Skip to content

Published: December 3, 2015 | Applies to:

Learn how to fix "The process cannot access the file because it is being used by another process" error when loading hive in Registry Editor for Windows 10.

Earlier, we’ve seen how to load hive in Registry Editor, in this following article:

How to load or unload hive in Registry Editor

We know that loading hive is quite important for administrators and it technically helps us to load registry about those user accounts which are facing some issues with their profile. Today, while loading hive using Command Prompt at boot, we came around following error due to which loading hive failed.

Cannot load X:\Windows\System32\config\SAM: The process cannot access the file because it being used by another process.

The Process Cannot Access The File Because It Is Being Used By Another Process While Loading Registry Hive

This is expected error which you will receive while loading user account via Security Account Manager (SAM) file. SAM file is basically a database file in Windows and it stores user account password and other relevant information.

FIX : “The Process Cannot Access The File Because It Is Being Used By Another Process” While Loading Registry Hive

The root cause behind you’re getting this error is mounting SAM file from incorrect folder. Actually, when you’re loading hive and look out for the SAM file in Load Hive window, Registry Editor by default opens config folder under X: drive. Here this X: comes due to Command Prompt at boot which defaults X: drive rather than using actual system root drive. Now since X: drive is nothing but its the memory in which Command Prompt is working, this error message comes into play.

Hence to solve this issue, you need to click the folder list under Look in section of window shown below. Then carefully locate your system root drive, note that it is always not C: drive.

The Process Cannot Access The File Because It Is Being Used By Another Process While Loading Registry Hive

Then navigate system root drive > Windows > System32 > config. In the config folder, choose SAM file. This should work up and the loaded hive can be find under local machine branch of registry database:

The Process Cannot Access The File Because It Is Being Used By Another Process While Loading Registry Hive

That’s it! See this fix if you can’t modify registry values.


SHARE: Facebook Google+ Twitter

2 Comments

  • Thank you Sir!!

    Question, I am here to enable Administrators account but the F key is 15 instead of 11 which is Disabled and suppose too change to 10, but I am not sure now since it is 15 and not 11 :( Any advice?

    Thank you in advance!

  • Kapil Arya

    ^^ Proceed as suggested here: http://www.kapilarya.com/fix-lost-administrative-rights-in-windows-10

  • Leave a Reply

    Your email address will not be published. Required fields are marked *

    What's New


    Recent Comments

    • Kapil Arya : ^^ Happy to help ☺️...

      1 hour ago

    • frozen nerd : i also tried uninstalling avast, disabling all startup progr...

      5 hours ago

    • frozen nerd : i have a win 10 home OEM from ASUS tried this and got the ...

      5 hours ago

    • Darren : Thank you, Kapil! The first two netsh commands and reboot ju...

      7 hours ago

    • Charles : I followed your steps but got stuck at step 9 since I couldn...

      12 hours ago

    • Barry : Fantastic! You solved my problem with very clear instruction...

      13 hours ago


    Windows Group Policy Troubleshooting