Dear Shanthi,

Good day!!

I apologize ahead if the information provided didn’t help to meet your requirement because moderator in this category mainly focus on the users with Office 365 Concerns and have limited knowledge on your concern.

I understand your requirement and done some search at my end, where I noticed it’s not possible directly to open a SAM file created in the Windows 7 on Windows 10/11, where we have to use some third-party tools.

However, I would like to guide you in the right direction to get some more information on this and you can try cross posting your concern in the following communities where the experts can share their ideas and experience:

Windows Category in Answers Forum: https://answers.microsoft.com/en-us/windows/forum?sort=LastReplyDate&dir=Desc&tab=All&status=all&mod=&modAge=&advFil=&postedAfter=&postedBefore=&threadType=All&isFilterExpanded=true&page=1 

Microsoft Q&A Community: https://learn.microsoft.com/en-us/answers/questions/  (Windows Category)

Windows Community: https://techcommunity.microsoft.com/t5/windows/ct-p/Windows10 

Please don’t mind on redirection as we mainly focus on Office 365 Services and to get the correct guidance, we redirected you to following communities.

Thanks for understanding and if you feel my reply helped to explain your situation, please click on the helpful button (Yes or No) in the reply. In the future, if you have any further concerns related to Office 365, please feel free to post a new thread in this community and we will try our best to assist you.

Have a good day!!

Best Regards,

Sophia

The SAM hive still exists in Windows 10, and it's in the same place. For local non-Microsoft accounts, the format does not appear to have changed; the NTLM hash is still the 16 bytes before the last 8 bytes of the V value.

For accounts that sign in with a Microsoft account password, the CachedLogonInfo value contains the cached password (source). Unfortunately, it's not just an NTLM hash, so normal Windows hash cracking tools won't work on it. If that page is correct and the algorithm is indeed much stronger - which would make sense, since it would be very bad if an MS account password could be retrieved from a workstation - then cracking it would take an extremely long time considering the complexity requirements Microsoft puts in place.