How to Repair Windows 2003 SBS R2 with Registry File Failure Error – STOP:C0000218
I recently had to repair our Windows 2003 SBS R2 server after it crashed into Blue Screen oblivion.
The system couldn’t load Windows and kept restarting after showing blue screen of death (BSOD) with the following error message indicating a registry file failure.
Stop: c0000218 {Registry File Failure} The registry cannot load the hive (file): SystemRootSystem32ConfigSOFTWARE or its log or alternate
Only one registry hive was corrupted so I didn’t want to follow Microsoft’s solution which a bit long so here is what I did.
- Use an alternative boot device to start the system. I used UBDC4Win but if you have the Windows installation CD then booting from it would be preferable. UBCD4Win can also installed on a pen drive.
- If you booted using the installation CD then select R to go into the recovery console otherwise start the command screen for your alternative boot device.
- This is an optional procedure but I always do this when something like this happens. I usually run the commands chkdsk /r /f to locate bad sectors on the hard disk and recover readable information. It’s just a procedure I do.
- Once the chkdsk is complete, delete the corrupted hive by using the following commands del c:windowssystem32configsoftware.
- Then restore the hive from the repair folder. Windows usually creates this folder as a backup. Use this command copy c:windowsrepairsoftware c:windowssystem32config.
- Remove the CD and reboot your system.
You should be able to load Windows and you can now repair other problems on the system.
If the error message appears with a different hive then simply replacing the hive named into the command line.
For further reference I suggest reading this http://support.microsoft.com/kb/307545
- How to Get Stock Photography Pictures That Sell - April 10, 2024
- How to Use Etcher AppImage on Ubuntu - September 13, 2023
- How to Install LogicalDOC CE on Ubuntu 22.04 LTS - June 22, 2023
nice infromation provide for ipad repair.I like this blog.iPad Repair
Thanks so much, this was the solution for my problem!
You are welcome Jaime.