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.

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 (70)

  1. Anonymous says:

    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!

  2. Anonymous says:

    Works great on my 2008 R2 servers – No reboot required – Many Thanks!

  3. Anonymous says:

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

    servicingpackagesPackage_for_KB2416400_RTM~31bf3856ad364e35~amd64~~6.1.1.2.mum

    servicingpackagesPackage_for_KB2416400_RTM~31bf3856ad364e35~amd64~~6.1.1.2.cat

  4. jrv says:

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

  5. wondering says:

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

  6. raman says:

    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.

  7. Chris Skorlinski (Microsoft) says:

    I had the same problem for

    Unavailable repair files:

    servicingpackagesPackage_for_KB2360131_RTM~31bf3856ad364e35~amd64~~6.1.1.3.mum

    servicingpackagesPackage_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.

  8. Juan Ortuno says:

    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!

  9. gcballard says:

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

  10. Lowell says:

    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?

  11. Howard says:

    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!

  12. Dangerousfish says:

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

  13. plaw013 says:

    Just the solution I was looking for. Thanks…

    Regards Peter

  14. justin says:

    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!

  15. julien says:

    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.

  16. JUAMPI says:

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

    Thanks

  17. akatim says:

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

  18. jesse says:

    I was able to fix one server by merely running the Readiness Tool.

    Thank you for the information.

  19. SAMI says:

    CraziJaxs – thank you!! your added solution resolved my issue.

  20. Julian M. says:

    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 !

  21. FedUp says:

    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!

  22. Mazoo says:

    Thanks reinaldokibel

    Step #3I didn't work for me either, but when I made a manual copy of the files, it worked.

  23. Microsoft GTSC Bucharest says:

    Is this page from a kacker fan club??  Romania :-))

  24. MuthuKrishnan- CTS boy says:

    Good post!!.. This resolved my issue.. Thanks narrator.

  25. Andrew says:

    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.

  26. Tomas says:

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

  27. Torben says:

    Thanks Justin – your suggestion worked for me (and the Microsoft way didn't) – to be specific …my checksur.log looked like this:

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

    Checking System Update Readiness.

    Binary Version 6.1.7601.21645

    Package Version 13.0

    2011-09-07 13:43

    Checking Windows Servicing Packages

    Checking Package Manifests and Catalogs

    (f) CBS MUM Corrupt 0x00000000 servicingPackagesPackage_for_KB2478661_RTM~31bf3856ad364e35~amd64~~6.1.1.0.mum Expected file name Microsoft-Windows-Foundation-Package~31bf3856ad364e35~amd64~~6.1.7600.16385.mum does not match the actual file name

    Checking Package Watchlist

    Checking Component Watchlist

    Checking Packages

    Checking Component Store

    Summary:

    Seconds executed: 832

    Found 1 errors

     CBS MUM Corrupt Total count: 1

    Unavailable repair files:

    servicingpackagesPackage_for_KB2478661_RTM~31bf3856ad364e35~amd64~~6.1.1.0.mum

    servicingpackagesPackage_for_KB2478661_RTM~31bf3856ad364e35~amd64~~6.1.1.0.cat

    (w) Unable to get system disk properties 0x0000045D IOCTL_STORAGE_QUERY_PROPERTY Disk Cache

    I just open Windows6.1-KB2478661-x64 cab file in the DestinationDirectory and found the 2 mum and cat files and dropped them to  %systemrootWindowsServicingPackages and then Add roles and features worked again

    so I could haved stopped with the step 2:

    – Unpack them using the following command:

    Expand -F:* UpdateKBXXXX.msu x:DestinationDirectory

  28. HUEC says:

    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.

  29. Damian says:

    Ridiculous

    Simply Ridiculous

    Smooth move M$

  30. manas says:

    Many  many thanks to JUSTIN…your solution worked for me.

    Cheers

  31. Steven says:

    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

  32. coolArtur says:

    Super!!! Work!!!

    I have problem with KB2616676 and copy two files from archive .cab

    into directory servicingpackages

    Package_for_KB2616676_SP1~31bf3856ad364e35~amd64~~6.1.1.0.mum

    Package_for_KB2616676_SP1~31bf3856ad364e35~amd64~~6.1.1.0.cat

    Thanks!!!

    Artur

  33. J007 says:

    This can be a pain, if you're deploying to several servers. How can this be prevented?

  34. Me says:

    Absolute Joke of an operating system, these are files managed by the OS that it corrupts.

    I have 200+ servers with the same error.

  35. MBKITMGR says:

    I have the same issue but the readiness tool reports the same problem after a following the method here a number of times.  

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

    Checking System Update Readiness.

    Binary Version 6.1.7601.21645

    Package Version 13.0

    2011-12-10 11:46

    Checking Windows Servicing Packages

    Checking Package Manifests and Catalogs

    (f) CBS MUM Corrupt 0x00000000 servicingPackagesPackage_for_KB2454826_RTM~31bf3856ad364e35~amd64~~6.1.2.0.mum Expected file name Package_for_KB2454826~31bf3856ad364e35~amd64~~6.1.2.0.mum does not match the actual file name

    Checking Package Watchlist

    Checking Component Watchlist

    Checking Packages

    Checking Component Store

    Summary:

    Seconds executed: 111

    Found 1 errors

     CBS MUM Corrupt Total count: 1

    Unavailable repair files:

    servicingpackagesPackage_for_KB2454826_RTM~31bf3856ad364e35~amd64~~6.1.2.0.mum

    servicingpackagesPackage_for_KB2454826_RTM~31bf3856ad364e35~amd64~~6.1.2.0.cat

    Customer Experience report successfully uploaded.  Thank you for participating.  For more information, see the Microsoft Customer Experience Improvement Program on the Microsoft web site.

    What else can be done to fix?

  36. cnc says:

    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.

  37. sam says:

    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.

  38. manuel says:

    Download the file MSU from microsoft

  39. Lamb says:

    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.

  40. Catlett says:

    Copying files from a working machine fixed my issue with KB2620712.  Thanks for all the help!

  41. Japinator says:

    My problem was fixed by re-applying KB947821 using the steps above. Thanks!

  42. Paddy185 says:

    Hi,

    I have the same issue but the readiness tool reports the same problem after a following the method here a number of times.

    I really don't understand…

    Always "HRESULT:0x800F0818"

    Please, any idea ?

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

    Checking System Update Readiness.

    Binary Version 6.1.7601.21645

    Package Version 14.0

    2012-04-30 15:09

    Checking Windows Servicing Packages

    Checking Package Manifests and Catalogs

    (f) CBS MUM Corrupt 0x00000000 servicingPackagesPackage_for_KB2584146_SP1~31bf3856ad364e35~amd64~~6.1.1.3.mum Expected file name Package_for_KB2584146~31bf3856ad364e35~amd64~~6.0.1.3.mum does not match the actual file name

    (fix) CBS MUM Corrupt CBS File Replaced Package_for_KB2584146_SP1~31bf3856ad364e35~amd64~~6.1.1.3.mum from Cabinet: C:WindowsCheckSurv1.0windows6.1-7601-x64-neutralcab.cab.

    (fix) CBS Paired File CBS File also Replaced Package_for_KB2584146_SP1~31bf3856ad364e35~amd64~~6.1.1.3.cat from Cabinet: C:WindowsCheckSurv1.0windows6.1-7601-x64-neutralcab.cab.

    Checking Package Watchlist

    Checking Component Watchlist

    Checking Packages

    Checking Component Store

    Summary:

    Seconds executed: 198

    Found 1 errors

    Fixed 1 errors

     CBS MUM Corrupt Total count: 1

     Fixed: CBS MUM Corrupt.  Total count: 1

     Fixed: CBS Paired File.  Total count: 1

  43. Dave says:

    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.

  44. Matt says:

    Insane. Can't wait til my mum has to do this on her Surface…

  45. D says:

    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?

  46. Paddy185 says:

    Hi !

    I try every day and no evolution…

    CheckSUR.log does'nt change…

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

    Checking System Update Readiness.

    Binary Version 6.1.7601.21645

    Package Version 14.0

    2012-07-18 17:05

    Checking Windows Servicing Packages

    Checking Package Manifests and Catalogs

    (f) CBS MUM Corrupt 0x00000000 servicingPackagesPackage_for_KB2584146_SP1~31bf3856ad364e35~amd64~~6.1.1.3.mum Expected file name Package_for_KB2584146~31bf3856ad364e35~amd64~~6.1.1.3.mum does not match the actual file name

    (fix) CBS MUM Corrupt CBS File Replaced Package_for_KB2584146_SP1~31bf3856ad364e35~amd64~~6.1.1.3.mum from Cabinet: C:WindowsCheckSurv1.0windows6.1-7601-x64-neutralcab.cab.

    (fix) CBS Paired File CBS File also Replaced Package_for_KB2584146_SP1~31bf3856ad364e35~amd64~~6.1.1.3.cat from Cabinet: C:WindowsCheckSurv1.0windows6.1-7601-x64-neutralcab.cab.

    Checking Package Watchlist

    Checking Component Watchlist

    Checking Packages

    Checking Component Store

    Summary:

    Seconds executed: 280

    Found 1 errors

    Fixed 1 errors

     CBS MUM Corrupt Total count: 1

     Fixed: CBS MUM Corrupt.  Total count: 1

     Fixed: CBS Paired File.  Total count: 1

    Please, any idea ?

  47. Paddy185 says:

    Thanks to CraziJaxs !!!

    The same way and good issue !!!

    Very good posts !

  48. Hacked Off says:

    Using the world as your testbed should be a criminal offense.  Shame on you, Microsoft!

  49. Jesus Wept says:

    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.

  50. Nife56 says:

    This is what my log says and it does not mention a KB. What do I do here.

    Checking System Update Readiness.

    Binary Version 6.1.7601.21645

    Package Version 18.0

    2013-05-06 15:21

    Checking Windows Servicing Packages

    Checking Package Manifests and Catalogs

    (f) CBS MUM Corrupt 0x00000000 servicingPackagesWUClient-SelfUpdate-Aux-MiniLP~31bf3856ad364e35~amd64~fr-FR~7.6.7600.256.mum Expected file name Microsoft-Windows-Foundation-Package~31bf3856ad364e35~amd64~~6.1.7600.16385.mum does not match the actual file name

    Checking Package Watchlist

    Checking Component Watchlist

    Checking Packages

    Checking Component Store

    Summary:

    Seconds executed: 299

    Found 1 errors

     CBS MUM Corrupt Total count: 1

    Unavailable repair files:

    servicingpackagesWUClient-SelfUpdate-Aux-MiniLP~31bf3856ad364e35~amd64~fr-FR~7.6.7600.256.mum

    servicingpackagesWUClient-SelfUpdate-Aux-MiniLP~31bf3856ad364e35~amd64~fr-FR~7.6.7600.256.cat

  51. Morris Maynard says:

    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.

  52. Vincent DURAIN says:

    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.

  53. @Nife56 says:

    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.

  54. Ulrich S. says:

    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) ?!?

  55. Kamante says:

    I have Ulrich S.'s problem. There seems to be no download location for needed files that have no KB number.

  56. Vyona says:

    Thanks !! It help me solved the problem!

  57. viralarchitect says:

    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.

  58. JDMils says:

    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!

  59. kuldeep Saxena says:

    but after ran tool I did not get any error on CheckSur.log file, so now what I’ll do as a next step.

  60. Steve says:

    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. 🙂

  61. Mark Anthony says:

    Great Post! It worked for me,
    Note I used 7zip to extract the msi cab files as I was experiencing some issues with the command line But otherwise its a go.

  62. Dave says:

    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?

  63. Dave says:

    Correction: My bad! I downloaded the x86 not the x64 package, all working now 😀

  64. Cybot says:

    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.

  65. Praveen says:

    Took me a while but this actually worked! Thanks mate!

  66. giuseppe says:

    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.

  67. gurnam says:

    worked….

  68. Julius says:

    Awesome stuff. Thanks, it worked for me.

  69. David says:

    IDIOTIC – Micro$oft continues to suck

  70. Wasim Sheikh says:

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