Error Cannot Load Registry File 589 (0x24D): How to Fix it
A chkdsk scan can sometimes help with this error code
2 min. read
Published on
Read our disclosure page to find out how can you help Windows Report sustain the editorial team. Read more
Sometimes on your PC, you may encounter an ERROR_CANNOT_LOAD_REGISTRY_FILE error, and if this happens, you won’t be able to boot to Windows at all. This can be a major problem, but let’s see if we can fix it.
How can I fix ERROR_CANNOT_LOAD_REGISTRY_FILE?
1. Check the boot order in BIOS
- Restart your PC.
- While it boots, keep pressing F2 or Del to access BIOS.
- Once you enter BIOS, navigate to the Boot section.
- Adjust the boot order if needed.
- Save changes and restart.
2. Run chkdsk from the recovery environment
- Restart your PC a few times during the boot.
- Next, navigate to Troubleshoot.
- Select Advanced options and then Command Prompt.
- Next, run
chkdsk C: /f /r
- Wait for the scan to finish.
Once done, check if the ERROR_CANNOT_LOAD_REGISTRY_FILE error is gone.
3. Use System Restore
- Repeat the steps from above, but instead of selecting Command Prompt choose System Restore.
- Follow the instructions on the screen and select the desired restore point.
- Wait for the process to finish and check if the problem is gone.
4. Perform a Windows reset
- Back up files from your C drive.
- Once again, follow the steps from above.
- Navigate to Troubleshoot and then select Reset this PC.
- Choose the Keep my files option.
- Follow the steps on the screen to perform a reset.
- If the reset doesn’t work, repeat the same steps, but choose Remove everything and then Only the drive where Windows is installed.
Keep in mind that for this solution you might need an installation media. To create it, you need to find a working PC and follow the instructions from our guide on how to create a Windows 11 bootable USB.
This error usually comes with the following message 589 (0x24D) {Registry File Failure} The registry cannot load the hive (file): %hs or its log or alternate. It is corrupt, absent, or not writable, so even if you don’t get the error code, you can use these solutions to fix it.
We covered similar registry issues in the past, and you can read about them in our STATUS_CANNOT_LOAD_REGISTRY_FILE and ERROR_INCOMPATIBLE_WITH_GLOBAL_SHORT_NAME_REGISTRY_SETTING articles.
User forum
0 messages