Home > Products > Windows Passwords > Windows Password Recovery > Screenshots > Loading hashes > Registry and Active Directory
Loading password hashes from registry and Active Directory
30.07.2021
Reset Windows Password v10.4.1
Support for Windows 10 21H1 and some extra enhancements
06.07.2021
MS Office password recovery tools
Support for MS Office 97-2003 formats, a major update in the password analysis module and mask attack syntax, etc.
06.07.2021
Office recovery tools
Some major changes in the password extraction module, mask attack syntax, etc.
17.06.2021
Reset Windows Password v10.3
Disk image creation tool, Windows PIN history decryption, new HTML/email parsing engine

Articles and video

You may find it helpful to read our articles on Windows security and password recovery examples. Video section contains a number of movies about our programs in action

Windows Password Recovery - loading hashes from registry and Active Directory

 

Loading password hashes from registry and Active Directory

Import hashes from binary files. Windows Password Recovery can extract password hashes directly from binary files. Even those of them that are currently used by the system (i.e. locked).

Normally, password hashes are stored in the registry file SAM, which resides in the '%WINDOWS%\System32\Config' folder. The same folder contains both the SECURITY and SYSTEM registry files, which is necessary for the recovery. If you have specified the current system's path to the registry, parsing it will take a bit longer (normally by a couple of extra seconds).

Password hashes for domain accounts are stored in the Active Directory database; or, to be more specific, in the very heart of it, in the ntds.dit file, which resides in the folder: '%Windows%\ntds'. To recover domain accounts you will also need the SYSTEM registry file.

Be careful! Dumping from the current system's Active Directory database may take some time, especially for huge databases.

Extracting domain cached credentials is pretty much the same as extracting regular SAM accounts. All you need is to specify paths to both SECURITY and SYSTEM files.

If you are copying the files from another system, besides the SAM (ntds.dit) and SYSTEM files, it is also highly recommended to copy the SECURITY and SOFTWARE registries (they should be located in the same folder with the SYSTEM file); that would allow you to recover the passwords to some user accounts quicker.

Using additional options you can:

  • Turn on/off password history parsing. Turning off history load will increase database processing. On the other hand, when attacking hashes, guessing history passwords may give a clue to figure out the password for the primary account the hashes belong to.
  • Discard loading machine accounts (ones end up with $ character).
  • Switch on/off the instant check for plaintext passwords, BitLocker backup keys, and other sensitive information
 
The program works properly and supports all the SYSKEY encryption options: Registry SYSKEY, SYSKEY startup diskette, SYSKEY startup password.