Compartir a través de

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

  • Artículo

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: https://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

  • Anonymous
    January 01, 2003
    Everything worked great for me except renaming the update.mum and update.cat to the KBXXXXXX.  When i did this is still got errors in the checksur log.  Instead I copied all the package_for_kb2454826_rtm~31bf3856ad364e35~amd64~~6.1.2.0.mum & .cat files (usually around 2-4 files) to the C:WindowsServicingPackages and over wrote existing files.   This solved my issue.  Thanks for posting this blog. Cheers!

  • Anonymous
    January 01, 2003
    Works great on my 2008 R2 servers - No reboot required - Many Thanks!

  • Anonymous
    January 01, 2003
    The comment has been removed

  • Anonymous
    July 06, 2010
    Remember to restore Owner to NT SERVICETrustedInstaller on the Packages folder and contents, and remove your username from the Packages folder ACL when finished.

  • Anonymous
    July 14, 2010
    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

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

  • Anonymous
    August 13, 2010
    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.

  • Anonymous
    October 26, 2010
    I had the same problem for Unavailable repair files: servicingpackagesPackage_for_KB2360131_RTM~31bf3856ad364e35~amd646.1.1.3.mum servicingpackagesPackage_for_KB2360131_RTM~31bf3856ad364e35~amd646.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.

  • Anonymous
    November 04, 2010
    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!

  • Anonymous
    November 04, 2010
    Thanks! I finally got my server fixed because of your excellent guide.

  • Anonymous
    November 14, 2010
    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?

  • Anonymous
    December 18, 2010
    The comment has been removed

  • Anonymous
    January 18, 2011
    Saved me a lot of hassle here. Thanks very much Tudor!

  • Anonymous
    January 19, 2011
    Just the solution I was looking for. Thanks... Regards Peter

  • Anonymous
    February 01, 2011
    I found that renaming the update.mum and update.cat files and copying to servicingpackages 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!

  • Anonymous
    February 03, 2011
    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.

  • Anonymous
    March 19, 2011
    I had fix that, making copy/paste with the files with the same name. Thanks

  • Anonymous
    April 05, 2011
    Not work ((( have server manager errors. ((

  • Anonymous
    April 28, 2011
    I was able to fix one server by merely running the Readiness Tool. Thank you for the information.

  • Anonymous
    May 04, 2011
    CraziJaxs - thank you!! your added solution resolved my issue.

  • Anonymous
    May 16, 2011
    Again ... renaming 2 files and replacing them, did not work. Just copy/paste-ing (replacing) the corrupted files can fix my 0x800f0818 at Windows update (Windows7). I would suggest MS to modify this KB. thanks !

  • Anonymous
    May 20, 2011
    I've had this happen more times than it should and usually to critcial systems like DCs MS you should fix this issue; this is a MAJOR issue on W2K8 R2!

  • Anonymous
    May 31, 2011
    Thanks reinaldokibel Step #3I didn't work for me either, but when I made a manual copy of the files, it worked.

  • Anonymous
    June 04, 2011
    Is this page from a kacker fan club??  Romania :-))

  • Anonymous
    June 20, 2011
    Good post!!.. This resolved my issue.. Thanks narrator.

  • Anonymous
    July 12, 2011
    Thanks that worked.  It's certainly a couple of hoops to jump through to resolve the issue, but if you follow the steps carefully it works.

  • Anonymous
    July 21, 2011
    This solved my problem, but I needed to copy the files from the cab-file. The renaming of the update-files didn´t work.

  • Anonymous
    September 07, 2011
    The comment has been removed

  • Anonymous
    September 13, 2011
    This article is a bit in error. Copy the mentioned missing files to C:WindowsTempCheckSURservicingpackages* Rerun the assesment tool. It wil update the missing files for you.

  • Anonymous
    September 20, 2011
    Ridiculous Simply Ridiculous Smooth move M$

  • Anonymous
    October 01, 2011
    Many  many thanks to JUSTIN...your solution worked for me. Cheers

  • Anonymous
    October 13, 2011
    i still cannot find the update files for kb976933 plz help Unavailable repair files: servicingpackagesPackage_for_KB976933~31bf3856ad364e35~x86~bg-BG~6.1.7601.17514.mum servicingpackagesPackage_for_KB976933~31bf3856ad364e35~x86~bg-BG~6.1.7601.17514.mum servicingpackagesPackage_for_KB976933~31bf3856ad364e35~x86~fi-FI~6.1.7601.17514.mum servicingpackagesPackage_for_KB976933~31bf3856ad364e35~x86~fi-FI~6.1.7601.17514.mum servicingpackagesPackage_for_KB976933~31bf3856ad364e35~x86~fr-FR~6.1.7601.17514.mum servicingpackagesPackage_for_KB976933~31bf3856ad364e35~x86~fr-FR~6.1.7601.17514.mum servicingpackagesPackage_for_KB976933~31bf3856ad364e35~x86~nb-NO~6.1.7601.17514.mum servicingpackagesPackage_for_KB976933~31bf3856ad364e35~x86~nb-NO~6.1.7601.17514.mum servicingpackagesPackage_for_KB976933~31bf3856ad364e35~x86~pl-PL~6.1.7601.17514.mum servicingpackagesPackage_for_KB976933~31bf3856ad364e35~x86~pl-PL~6.1.7601.17514.mum servicingpackagesPackage_for_KB976933~31bf3856ad364e35~x86~pt-BR~6.1.7601.17514.mum servicingpackagesPackage_for_KB976933~31bf3856ad364e35~x86~pt-BR~6.1.7601.17514.mum servicingpackagesPackage_for_KB976933~31bf3856ad364e35~x86~ro-RO~6.1.7601.17514.mum servicingpackagesPackage_for_KB976933~31bf3856ad364e35~x86~ro-RO~6.1.7601.17514.mum servicingpackagesPackage_for_KB976933~31bf3856ad364e35~x86~sk-SK~6.1.7601.17514.mum servicingpackagesPackage_for_KB976933~31bf3856ad364e35~x86~sk-SK~6.1.7601.17514.mum servicingpackagesPackage_for_KB976933~31bf3856ad364e35~x86~th-TH~6.1.7601.17514.mum servicingpackagesPackage_for_KB976933~31bf3856ad364e35~x86~th-TH~6.1.7601.17514.mum servicingpackagesPackage_for_KB976933~31bf3856ad364e35~x86~bg-BG~6.1.7601.17514.cat servicingpackagesPackage_for_KB976933~31bf3856ad364e35~x86~bg-BG~6.1.7601.17514.cat servicingpackagesPackage_for_KB976933~31bf3856ad364e35~x86~fi-FI~6.1.7601.17514.cat servicingpackagesPackage_for_KB976933~31bf3856ad364e35~x86~fi-FI~6.1.7601.17514.cat servicingpackagesPackage_for_KB976933~31bf3856ad364e35~x86~fr-FR~6.1.7601.17514.cat servicingpackagesPackage_for_KB976933~31bf3856ad364e35~x86~fr-FR~6.1.7601.17514.cat servicingpackagesPackage_for_KB976933~31bf3856ad364e35~x86~nb-NO~6.1.7601.17514.cat servicingpackagesPackage_for_KB976933~31bf3856ad364e35~x86~nb-NO~6.1.7601.17514.cat servicingpackagesPackage_for_KB976933~31bf3856ad364e35~x86~pl-PL~6.1.7601.17514.cat servicingpackagesPackage_for_KB976933~31bf3856ad364e35~x86~pl-PL~6.1.7601.17514.cat servicingpackagesPackage_for_KB976933~31bf3856ad364e35~x86~pt-BR~6.1.7601.17514.cat servicingpackagesPackage_for_KB976933~31bf3856ad364e35~x86~pt-BR~6.1.7601.17514.cat servicingpackagesPackage_for_KB976933~31bf3856ad364e35~x86~ro-RO~6.1.7601.17514.cat servicingpackagesPackage_for_KB976933~31bf3856ad364e35~x86~ro-RO~6.1.7601.17514.cat servicingpackagesPackage_for_KB976933~31bf3856ad364e35~x86~sk-SK~6.1.7601.17514.cat servicingpackagesPackage_for_KB976933~31bf3856ad364e35~x86~sk-SK~6.1.7601.17514.cat servicingpackagesPackage_for_KB976933~31bf3856ad364e35~x86~th-TH~6.1.7601.17514.cat servicingpackagesPackage_for_KB976933~31bf3856ad364e35~x86~th-TH~6.1.7601.17514.cat

  • Anonymous
    October 16, 2011
    Super!!! Work!!! I have problem with KB2616676 and copy two files from archive .cab into directory servicingpackages Package_for_KB2616676_SP1~31bf3856ad364e35~amd646.1.1.0.mum Package_for_KB2616676_SP1~31bf3856ad364e35~amd646.1.1.0.cat Thanks!!! Artur

  • Anonymous
    October 18, 2011
    This can be a pain, if you're deploying to several servers. How can this be prevented?

  • Anonymous
    October 27, 2011
    Absolute Joke of an operating system, these are files managed by the OS that it corrupts. I have 200+ servers with the same error.

  • Anonymous
    December 09, 2011
    The comment has been removed

  • Anonymous
    December 17, 2011
    I agree, what a joke of a process. I have the 100% same exact error. Running the "2008" tool and see what happens. There is no official readiness tool for 2011 yet.

  • Anonymous
    January 01, 2012
    I don't understand the second step:

  • Unpack them using the following command: Expand -F:* UpdateKBXXXX.msu x:DestinationDirectory >> I have the .mum and the .cat file. But where is the UpdateKBXXXX.msu come from? Appreciate your help.

  • Anonymous
    January 10, 2012
    Download the file MSU from microsoft

  • Anonymous
    April 10, 2012
    Hi, as a summary/close for one of my partners: The blog is not quite correct. We still need to copy files from a working machine. Or, use the existing files in the extracted folder of the msu. Renaming is not a right step, concluded from ITPRO teams.

  • Anonymous
    April 24, 2012
    Copying files from a working machine fixed my issue with KB2620712.  Thanks for all the help!

  • Anonymous
    April 29, 2012
    My problem was fixed by re-applying KB947821 using the steps above. Thanks!

  • Anonymous
    May 04, 2012
    The comment has been removed

  • Anonymous
    May 30, 2012
    Trying tounderstand this further in general does renaming update.mum and update.cat for a particular package to the missing files in checksur.log work no matter the package? The text inside the various MUM files is quite different.

  • Anonymous
    June 26, 2012
    Insane. Can't wait til my mum has to do this on her Surface...

  • Anonymous
    July 16, 2012
    2 years later, this error is still occurring thanks to Windows Update...shouldn't it be time that Microsoft gets it fixed so that we don't have to deal with this?

  • Anonymous
    July 18, 2012
    The comment has been removed

  • Anonymous
    July 19, 2012
    Thanks to CraziJaxs !!! The same way and good issue !!! Very good posts !

  • Anonymous
    August 02, 2012
    Using the world as your testbed should be a criminal offense.  Shame on you, Microsoft!

  • Anonymous
    October 23, 2012
    October 2012 and still having the issue on a newly installed 2008 R2 machine. Perhaps I'll just reinstall and try my luck. Maybe Server 2012 will be more stable..... or not.

  • Anonymous
    May 07, 2013
    The comment has been removed

  • Anonymous
    June 19, 2013
    Evidently, the patch at support.microsoft.com/.../947821 now repairs the missing or corrupt files in packages. At least, after running it, the log indicated the files were "fixed" and in fact, the server manager and update functions that failed previously now work.

  • Anonymous
    July 12, 2013
    the patch 947821 doesn't always repair corrupted files. In my case, i had corrupt files for role server, i've solve this with the comment of "Justin 1 Feb 2011 1:56 AM", i had the same case with KB 2744842 and i've found the cat and mum file directly in the uncompressed cab. I'ts work now, Thanks Justin.

  • Anonymous
    July 23, 2013
    Download them here and replace the corrupted files. Worked for me docs.google.com/.../edit This solution pointed me in the right direction although it is not applicable for every packe.

  • Anonymous
    September 24, 2013
    And where can I find download links for files starting with Microsoft-Windows-IE-Hyphenation-Parent-Package-English~... Microsoft-Windows-IE-Spelling-Parent-Package-English~... (and 16 others similar filename starting too) ?!?

  • Anonymous
    October 16, 2013
    I have Ulrich S.'s problem. There seems to be no download location for needed files that have no KB number.

  • Anonymous
    June 11, 2014
    Thanks !! It help me solved the problem!

  • Anonymous
    July 31, 2014
    This worked for me. Different patches from what were mentioned in the post, but if you follow the directions exactly, you'll get it working. Also, indeed remember to change the owner of the C:WINDOWSServicingPackages folder back to "NT ServiceTrustedInstaller" and remove yourself from the security access list.

  • Anonymous
    October 22, 2014
    The standard procedure did not work for my Win 2K8 R2 (non-SP1), and I tried many times. I copied the same files from a working server (Thanks Julien!!) and it worked!

  • Anonymous
    November 21, 2014
    but after ran tool I did not get any error on CheckSur.log file, so now what I'll do as a next step.

  • Anonymous
    April 03, 2015
    Many thanks for this.. worked for me when I copied the files in from the cab rather than trying to rename. Solved a problem that has existed for a long time. :)

  • Anonymous
    April 20, 2015
    The comment has been removed

  • Anonymous
    May 15, 2015
    I've followed the guide but it's not working for me yet. I've read a few people saying that you need to reset the permissions & ownership back but how do I do this?

  • Anonymous
    May 15, 2015
    Correction: My bad! I downloaded the x86 not the x64 package, all working now :-D

  • Anonymous
    July 09, 2015
    Ulrich S. has a similar problem as me. my problem is the hyphenation and spelling packages for ie10 and ie11. I tried making a copy of the actual filename and giving the copy the name that was listed in the expected filename, but dism didn't even notice and still listed the 4 files. this has been an issue for me since at least 2013 uninstalling and reinstalling ie10/11 does not solve the issue.

  • Anonymous
    August 20, 2015
    Took me a while but this actually worked! Thanks mate!

  • Anonymous
    October 02, 2015
    Thanks! It worked. I wonder if the problem would arise without installing 121 patches, but installing Service Pack 2, and applying the remaining patches AFTER the SP2.

  • Anonymous
    October 14, 2015
    worked....

  • Anonymous
    February 12, 2016
    Awesome stuff. Thanks, it worked for me.

  • Anonymous
    March 08, 2016
    The comment has been removed

  • Anonymous
    April 02, 2016
    Thanks! I finally got my server fixed because of your excellent guide.