Q. How can I restore the HKLM\Software and HKLM\System hives if they become corrupted during a failed Windows Server 2003 SP1 install?

If your SP1 (Service Pack 1) installation on Windows Server 2003 fails, resulting in corruption of the HKLM\Software and HKLM\System registry hives, AND the rollback process fails, you may be able to restore these hives from the Software.sp and System.sp files that the service pack install backed up at %SystemRoot%\System32\Config.

To replace the corrupted registry hives:

1. If necessary, configure your BIOS to allow starting from a CD-ROM drive.

2. Insert the Windows Server 2003 CD into the CD-ROM drive and restart the server.

3. Press the space bar when you receive Press any key to boot from CD.

4. Press R in response to:

<b>This portion of the Setup program prepares Windows Server 2003 to run on your computer:
To setup Windows Server 2003 now, press ENTER
To repair a Windows Server 2003 installation using Recovery Console, press R
To quit Setup without installing Windows Server 2003, press F3</b>
5. If you have a multiple-boot system, select the operating system that you want to access from the Recovery Console.

6. When prompted for a password, type the Administrator password.

7. In the Recovery Console, type the following commands, pressing Enter after each line:

<b>cd %windir%\system32\config\
ren System System.bad
ren Software Software.bad
ren System.sp System
ren Software.sp Software</b>
8. Restart your server.

NOTE: If your registry hives were corrupted before you attempted to install SP1, the .sp files will be corrupted.


Please or Register to post comments.

IT/Dev Connections

Las Vegas
September 30th - October 4th

Paul ThurottYou'll have the opportunity to experience:
• The Microsoft
Technology Roadmap
• Office 365 Implementation
• Hyper-V Optimizing
• Windows 8 Deployment
and much more!

Come See Paul Thurrott & Rod Trent in Person!

Early Registration Now Open

Upcoming Training

Mastering SharePoint 2013: Succeeding, Not Just Surviving

Building on the success of the “Mastering SharePoint 2010” seminars, the presenters have updated the content to cover the latest and greatest SharePoint product: SharePoint 2013. While SharePoint 2013 is relatively new on the marketplace, the presenters have been working with SharePoint 2013 for well over a year, and have implemented it with a number of clients in production environments.

Register Now

Current Issue

May 2013 - The NameTranslate object is useful when you need to translate Active Directory object names between different formats, but it's awkward to use from PowerShell. Here's a PowerShell script that eliminates the awkwardness.

CURRENT ISSUE / ARCHIVE / SUBSCRIBE

Windows Forums

Get answers to questions, share tips, and engage with the Windows Community in our Forums.