Microsoft GTSC Romania - Enterprise Platforms Support

Microsoft GTSC Bucharest / Covering topics such as: Windows Server, Failover Clustering, Performance, Printing, Core OS, AD, Deployment, WSUS, SCOM/SCCM

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

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

  • Comments 57
  • Likes

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

Error: Unexpected error refreshing Server Manager: Exception from HRESULT:0x800F0818

Alternatively you can also get:
Server Manager: Unexpected error refreshing Server Manager: No signature was present in the subject. (Exception from HRESULT: 0x800B0100)

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.

clip_image001

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.

Tudor Dimboianu
- Support Engineer / Enterprise Platforms Support (Core)

Comments
  • Remember to restore Owner to NT SERVICE\TrustedInstaller on the Packages folder and contents, and remove your username from the Packages folder ACL when finished.

  • what should be renamed...the .cat file or the .cab file???

    "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:"

  • Thanks this is very helpful.

    I resolved the issue after following it.  Although, now error is not there but Server Manager Features only showing

    single feature "Windows Internal Database".  Same with the "Roles" it only shows a single option "Application Server".

    Would you please advise.

    Email address raman03@msn.com

    Thanks.

  • I had the same problem for

    Unavailable repair files:

    servicing\packages\Package_for_KB2360131_RTM~31bf3856ad364e35~amd64~~6.1.1.3.mum

    servicing\packages\Package_for_KB2360131_RTM~31bf3856ad364e35~amd64~~6.1.1.3.cat

    But once I followed the step to expand and copy/replace the file listed in the CheckSUR log the Windows 2008 R2 Service Managers worked.

  • Great! This worked.

    It's VERY important for everyone having this problem to look at the log file.

    I did it first without checking the log file by using the same KB listed here and it didn't work.

    It turned out that it was a different KB having issues - KB2388210

    I followed the steps above but used the KB shown in my error log, and it worked perfectly. No reboot required.

    Thanks!

  • Thanks! I finally got my server fixed because of your excellent guide.

  • Nowhere can I seem to find information about how to actually run the System Update Readiness tool.  You mention to re-run the tool... does that mean re-running the actual 152MB update every time?

  • This is absurd. Does Microsoft really expect people to go through this convoluted rigamorole just to get their machines fixed? Dump your Windows box! Switch to a Mac! I HATE MICROSOFT!

  • Saved me a lot of hassle here. Thanks very much Tudor!

  • Just the solution I was looking for. Thanks...

    Regards Peter

  • In My case the last step #3 did not work. rename update.mum and update.cab did not work.

    in the KB the actual files .Num and .Cab were there. so I just had to copy the exact 2 files from the downloaded and extracted KB2416400 to the /servicing/packages directory. That resolved the issue.

    here is the info from Checksur.log

    =================================

    Checking System Update Readiness.

    Binary Version 6.1.7600.20822

    Package Version 10.0

    2011-01-11 23:55

    Checking Windows Servicing Packages

    Checking Package Manifests and Catalogs

    (f) CBS MUM Corrupt 0x00000000 servicing\Packages\Package_for_KB2416400_RTM~31bf3856ad364e35~amd64~~6.1.1.2.mum Expected file name Package_for_KB2416400~31bf3856ad364e35~amd64~~6.1.1.2.mum does not match the actual file name

    Checking Package Watchlist

    Checking Component Watchlist

    Checking Packages

    Checking Component Store

    Summary:

    Seconds executed: 425

    Found 1 errors

     CBS MUM Corrupt Total count: 1

    Unavailable repair files:

    servicing\packages\Package_for_KB2416400_RTM~31bf3856ad364e35~amd64~~6.1.1.2.mum

    servicing\packages\Package_for_KB2416400_RTM~31bf3856ad364e35~amd64~~6.1.1.2.cat

  • I found that renaming the update.mum and update.cat files and copying to servicing\packages did not work. Then I noticed in the expanded cab file that there were already two files with the correct filename as referenced in checksur.log. Once I copied those 2 files it then worked!

  • Thx a lot it works on my server 2008r2

    I couldn't find the kb on windows update but I had the same server without errors so I took his kb and paste it on \packages of the other server.

  • I had fix that, making copy/paste with the files with the same name.

    Thanks

  • Not work ((( have server manager errors. ((

Your comment has been posted.   Close
Thank you, your comment requires moderation so it may take a while to appear.   Close
Leave a Comment