I have seen many discussions on 64-bit Hash crawling in Windows. We all know that Lm Hash is no longer saved in Windows Vista. All well-known Hash capture tools, such as PwDump, Gsecdump, WCE, and Gethash, are invalid. This is not a tool problem, but is nothing you can grasp, I also studied this issue in depth in the first half of the year. If the system does not store anything, we can just save it. Open the Local Security Policy-security option, which is tested in the local environment. The same is true for domain Hash, but the security policies of the domain controller are different. After the changes are made, the gpupdate/force instant refresh policy Start (Start)-Programs (Program) is executed) -Administrative Tools (Administrative Tools)-Group Policy Management (Policy Manager) Expand Group Policy Manager select-Forest (Forest)-Domains (domain)-Group Policy Objects (Group Policy object) -Default Domain Policy (Default Domain Policy), right-click Edit, and choose Computer Configuration> Policies> Windows Settings) -Security Settings (Security Settings) passed the test, but it was not. The change of password takes effect only after the prerequisites. However, generally large enterprises have security policies and will prompt you to change the password within three months, this is only a common phenomenon ). Now we can capture the global Hash.