How to fix Server Manager Errors after installing updates (HRESULT:0x800F0818 / HRESULT:0x800B0100)

Symptoms
You install several Updates. After the successful installation, you notice you cannot add or remove features/roles in the Server Manager.

Resolution
First you run the Microsoft Update Readiness Tool located here: http://support.microsoft.com/kb/947821
After the scan has completed check: C:\Windows\logs\CBS\Checksur.log. You should see the following errors:

Checking Package Manifests and Catalogs
(f) CBS MUM Corrupt 0x00000000 servicing\Packages\Package_for_KB978601~31bf3856ad364e35~amd64~~6.0.1.0.mum  Expected file name Package_for_KB978601_server~31bf3856ad364e35~amd64~~6.0.1.0.mum does not match the actual file name
(f) CBS MUM Corrupt 0x00000000 servicing\Packages\Package_for_KB979309~31bf3856ad364e35~amd64~~6.0.1.0.mum  Expected file name Package_for_KB979309_server~31bf3856ad364e35~amd64~~6.0.1.0.mum does not match the actual file name

Or 

(f) CBS MUM Corrupt 0x800B0100 servicing\Packages\Package_for_KB978601~31bf3856ad364e35~amd64~~6.0.1.0.mum servicing\Packages\Package_for_KB978601~31bf3856ad364e35~amd64~~6.0.1.0.cat Package manifest cannot be validated by the corresponding catalog
(f) CBS MUM Corrupt 0x800B0100 servicing\Packages\Package_for_KB979309~31bf3856ad364e35~amd64~~6.0.1.0.mum servicing\Packages\Package_for_KB979309~31bf3856ad364e35~amd64~~6.0.1.0.cat Package manifest cannot be validated by the corresponding catalog
Or
(f) CBS MUM Missing 0x00000002 servicing\packages\Package_114_for_KB955839~31bf3856ad364e35~amd64~~6.0.1.0.mum
(f) CBS MUM Missing 0x00000002 servicing\packages\Package_83_for_KB955839~31bf3856ad364e35~amd64~~6.0.1.0.mum

Further down you will see:

Unavailable repair files:
servicing\packages\Package_for_KB978601~31bf3856ad364e35~amd64~~6.0.1.0.mum
servicing\packages\Package_for_KB979309~31bf3856ad364e35~amd64~~6.0.1.0.mum
servicing\packages\Package_for_KB978601~31bf3856ad364e35~amd64~~6.0.1.0.cat
servicing\packages\Package_for_KB979309~31bf3856ad364e35~amd64~~6.0.1.0.cat
These files need to be copied into: %systemroot\Windows\Servicing\Packages

1. You first need to gain control over that folder. In order to do this use the following commands:

This makes the current logged on user (needs to have Administrative privileges) owner of that folder:
takeown /F c:\Windows\Servicing\Packages /D y /R

Then assign full control using:
cacls c:\Windows\Servicing\Packages /E /T /C /G "UserName":F

This will grant you full control over the directory.
Optionally you can download this ZIP. Inside you have 2 REG Files. If you install TakeOwnership.reg you will have a handy Take Ownership entry in the right click menu every time you use it on a Folder.






2. Now you need to gather the missing or corrupted files from the checksur log:

- Download the KB Files for the missing files:
servicing\packages\Package_for_KB978601~31bf3856ad364e35~amd64~~6.0.1.0.mum

- Unpack them using the following command:
Expand -F:* UpdateKBXXXX.msu x:\DestinationDirectory

After you expand you will see a UpdateKBXXXX.cab File. Expand it as well:
Expand -F:* UpdateKBXXXX.CAB x:\DestinationDirectoryCAB

Inside of this cab you will need to grab 2 files: update.mum and update.cat

3. Rename the gathered update.mum and update.cab files exactly as they are specified in the checksur.log:
Ex.: update.mum for KB978601 will be:
Package_for_KB978601~31bf3856ad364e35~amd64~~6.0.1.0.mum
Do the same for all the other missing/corrupt files and place them into the directory specified in checksur.log (/servicing/packages)
After these steps the problem should be fixed. No reboot required.
If the Server Manager is not working even after doing these steps, run the Update Readiness Tool again and double-check the steps described above.

Booting Into the System Recovery Options Screen

First you will need to boot your computer into the System Recovery Options screen. This is usually done with the installation DVD, which should be inserted into the optical drive. When the computer boots, Press any key to boot from CD or DVD as requested, select your language preference and then click Repair your computer. A list of installed operating systems should be displayed – select Windows 7 and click Next.

The System Recovery Options screen will appear. Select the first option, Use recovery tools that can help fix problems with Windows, and then select Startup Repair.
(If your computer has a pre-installed recovery partition, the process is a little difference. In this case, boot to the Advanced Boot Options screen, select Repair your computer and tap Enter. Next, select the keyboard language type, then your username and password before selecting Startup Repair in the System Recovery Options screen.)
With Startup Repair selected, Windows will attempt to automate the repair; this might work – otherwise, further action will be required.

Preparing Windows 7 Recovery

If the Startup Repair option fails, you will receive a message reading Windows cannot repair this computer automatically. At the bottom of the message, click View advanced options for system recovery and support to return to System Recovery Options, and instead click Command Prompt.
The black command line interface will open with X:\ selected by default; this is the Windows internal RAM disk that is used by System Repair. You will need to navigate to your Windows system drive, which will by default be on the C: drive.
To open this, type C: and press Enter. Type DIR and press Enter to check that you are in the right drive – the contents listed should include the Program Files, Users and Windows folders.

You will then need to change directory. Enter CD \windows\system32\config and then DIR to check that the correct files and folders are listed:

• RegBack
• DEFAULT
• SAM
• SECURITY
• SOFTWARE
• SYSTEM

With access to the correct directory and the required folders present, enter MD mybackup to create a backup folder. Enter copy *.* mybackup to copy everything to this location, agreeing to the overwrite warnings when they appear.

The RegBack folder stores automatic Windows registry backups. To check if these can be used in restoring your system, enter CD RegBack and then DIR to view the contents. In the folder, you should have the following:

• DEFAULT, SAM and SECURITY files, each around 262,000 bytes
• SOFTWARE file, around 26,000,000 bytes
• SYSTEM file, around 9,900,000 bytes

Note that these figures are approximate, but recognise that if any of these files display a size of zero bytes then you will have to resort to another method of restoring Windows 7.

Running the Windows 7 Recovery

With your RegBack folder containing the data you need to restore Windows 7 and rescue it from the reboot loop, you will be able to copy the contents and use them to get the operating system back up and running again.

Begin by entering copy *.* .. – note the two trailing dots. These indicate that the contents should be pasted to the level above – the Config folder. Agree to all prompts concerning whether you want to overwrite files, and once the process has completed enter exit to close the command prompt.

On the System Recovery Options screen, click Restart to reboot your PC – if everything has gone as it should, Windows 7 should now start correctly!