bob16314
Try to reset Windows password..See how that rolls.
 
By the way, it rolls perfectly for me.

bob16314
Works like a charm for me (Win10 Home and Win7 Home).

I create a bootable USB with the ISO2USB tool from the HBCD_PE_x64.iso file..Then boot from the USB into Hiren's, not Windows..Then open Utilities..Then Security..Then Passwords..Then NT Password Edit. 

Then make sure the path is to the SAM file in the Windows\System32\Config folder..Then Change password for the user..Then make a new password or leave all fields blank to delete your current one..Then Save Changes..Then Exit..Then pull the USB and Restart..Then *poof* like magic, done deal.

If you dual-boot, make sure to point Hirens to the SAM file on the correct Windows drive

ty_ger07
Dave takes a computer from a dumpster which has been set up using a Microsoft online account.  He doesn't know the former owner nor the former owner's account password.  He creates a new administrator account and deletes the old owner's account.  All without dealing with Microsoft support or any 3rd party programs.  If he can do it, you should be able to as well.
 
I am going to give a link so that it will start at a specific time in the video, instead of embedding the video here.  If I embedded the video, it would start from the beginning with stuff you wouldn't find relevant.
https://youtu.be/-FszeHoK2Ck?t=420
 
(from 07:00 to 12:30)
 
If you have a SSD and the computer boots too fast, the 3 time "spinny icon" recovery mode boot method might not work for you.  In that case, you will need to use another method to boot into Windows 10 recovery mode.  There are multiple ways to get into Windows recovery mode.  From there, the rest of his methodology should work.
 
I think it is pretty easy to follow, but some stuff is missing.
 
Basically, what he did was whatever was necessary to get into the Windows Image Recovery process.  Then, when he chose to "Install a Driver", he instead renamed Utilman to something else and then renamed CMD to Utilman.  Then, he rebooted to a normal boot.  Then, when locked at that user's account screen, he clicked the Ease of Access icon in the bottom right which is supposed to help people with disabilities log in, but instead opened up command prompt due to his file name changes.  For some reason, command prompt opens up with full administrator privileges (seems like a Windows security bug to me), and then he used a command to open Netplwiz and create a new account.  Then, he used command prompt (because command prompt was currently running with administrative privileges) to change that new user's account to administrative privilege level.  Then, he rebooted, logged in as the new user, and deleted the other old user.  I would assume that he then renamed CMD and Utilman back in order to avoid further errors.  I also assume that at some point in the future Windows would make you sync the new account to a Microsoft online account; which you can presumably do to an old already-existing Microsoft account or to a new Microsoft account... I am not sure.  And, does Windows become deactivated at some point, or does it remain activated?  Very interesting questions to ask.