Hello, I'm having trouble getting an update to install on a client PC. The update is KB2393802 and it fails with code 0x800B0100. This is on a Windows 7 Pro 32-bit machine. As recommended in the help for this error code, I downloaded and ran the System Update Readiness Tool. The CheckSUR log showed corruption of some MUM and catalog files and reported a list of 'unavailable repair files'. I then followed the instructions in the article below to extract the missing files from the downloaded update to the required folders within %windor%\Temp\CheckSUR. http://technet.microsoft.com/en-us/library/ee619779(WS.10).aspx I then re-ran CheckSUR and got the following log: ================================= Checking System Update Readiness. Binary Version 6.1.7601.21645 Package Version 11.0 2011-04-13 21:14 Checking Windows Servicing Packages Checking Package Manifests and Catalogs (f) CBS MUM Corrupt 0x800F0900 servicing\Packages\Package_2_for_KB2393802~31bf3856ad364e35~x86~~6.1.1.1.mum Line 1: (fix) CBS MUM Corrupt CBS File Replaced Package_2_for_KB2393802~31bf3856ad364e35~x86~~6.1.1.1.mum from Cabinet: C:\Windows\CheckSur\v1.0\windows6.1-7601-x86-cab4.cab. (fix) CBS Paired File CBS File also Replaced Package_2_for_KB2393802~31bf3856ad364e35~x86~~6.1.1.1.cat from Cabinet: C:\Windows\CheckSur\v1.0\windows6.1-7601-x86-cab4.cab. (f) CBS MUM Corrupt 0x800F0900 servicing\Packages\Package_4_for_KB2393802~31bf3856ad364e35~x86~~6.1.1.1.mum Line 1: (fix) CBS MUM Corrupt CBS File Replaced Package_4_for_KB2393802~31bf3856ad364e35~x86~~6.1.1.1.mum from Cabinet: C:\Windows\CheckSur\v1.0\windows6.1-7601-x86-cab4.cab. (fix) CBS Paired File CBS File also Replaced Package_4_for_KB2393802~31bf3856ad364e35~x86~~6.1.1.1.cat from Cabinet: C:\Windows\CheckSur\v1.0\windows6.1-7601-x86-cab4.cab. (f) CBS MUM Corrupt 0x800F0900 servicing\Packages\Package_for_KB2393802_RTM~31bf3856ad364e35~x86~~6.1.1.1.mum Line 1: (fix) CBS MUM Corrupt CBS File Replaced Package_for_KB2393802_RTM~31bf3856ad364e35~x86~~6.1.1.1.mum from Cabinet: C:\Windows\CheckSur\v1.0\windows6.1-7601-x86-cab4.cab. (fix) CBS Paired File CBS File also Replaced Package_for_KB2393802_RTM~31bf3856ad364e35~x86~~6.1.1.1.cat from Cabinet: C:\Windows\CheckSur\v1.0\windows6.1-7601-x86-cab4.cab. (f) CBS MUM Corrupt 0x800F0900 servicing\Packages\Package_for_KB2393802~31bf3856ad364e35~x86~~6.1.1.1.mum Line 1: (fix) CBS MUM Corrupt CBS File Replaced Package_for_KB2393802~31bf3856ad364e35~x86~~6.1.1.1.mum from Cabinet: C:\Windows\CheckSur\v1.0\windows6.1-7601-x86-cab4.cab. (fix) CBS Paired File CBS File also Replaced Package_for_KB2393802~31bf3856ad364e35~x86~~6.1.1.1.cat from Cabinet: C:\Windows\CheckSur\v1.0\windows6.1-7601-x86-cab4.cab. Checking Package Watchlist Checking Component Watchlist Checking Packages Checking Component Store (f) CSI Manifest All Zeros 0x00000000 winsxs\Manifests\x86_microsoft-windows-ntdll_31bf3856ad364e35_6.1.7600.20826_none_5978b89a766d479e.manifest x86_microsoft-windows-ntdll_31bf3856ad364e35_6.1.7600.20826_none_5978b89a766d479e (fix) CSI Manifest All Zeros CSI File Replaced File: x86_microsoft-windows-ntdll_31bf3856ad364e35_6.1.7600.20826_none_5978b89a766d479e.manifest From: C:\Windows\CheckSur\v1.0\windows6.1-7601-x86-cab4.cab (f) CSI Manifest All Zeros 0x00000000 winsxs\Manifests\x86_microsoft-windows-os-kernel_31bf3856ad364e35_6.1.7600.16695_none_6bfbed8a157ebb3f.manifest x86_microsoft-windows-os-kernel_31bf3856ad364e35_6.1.7600.16695_none_6bfbed8a157ebb3f (fix) CSI Manifest All Zeros CSI File Replaced File: x86_microsoft-windows-os-kernel_31bf3856ad364e35_6.1.7600.16695_none_6bfbed8a157ebb3f.manifest From: C:\Windows\CheckSur\v1.0\windows6.1-7601-x86-cab4.cab (f) CSI Manifest All Zeros 0x00000000 winsxs\Manifests\x86_microsoft-windows-ntdll_31bf3856ad364e35_6.1.7600.16695_none_58a26a2b5d8954ed.manifest x86_microsoft-windows-ntdll_31bf3856ad364e35_6.1.7600.16695_none_58a26a2b5d8954ed (fix) CSI Manifest All Zeros CSI File Replaced File: x86_microsoft-windows-ntdll_31bf3856ad364e35_6.1.7600.16695_none_58a26a2b5d8954ed.manifest From: C:\Windows\CheckSur\v1.0\windows6.1-7601-x86-cab4.cab (f) CSI Manifest All Zeros 0x00000000 winsxs\Manifests\x86_microsoft-windows-os-kernel_31bf3856ad364e35_6.1.7600.20826_none_6cd23bf92e62adf0.manifest x86_microsoft-windows-os-kernel_31bf3856ad364e35_6.1.7600.20826_none_6cd23bf92e62adf0 (fix) CSI Manifest All Zeros CSI File Replaced File: x86_microsoft-windows-os-kernel_31bf3856ad364e35_6.1.7600.20826_none_6cd23bf92e62adf0.manifest From: C:\Windows\CheckSur\v1.0\windows6.1-7601-x86-cab4.cab (f) CSI Manifest All Zeros 0x00000000 winsxs\Manifests\x86_microsoft-windows-r..gistry-trustedtypes_31bf3856ad364e35_6.1.7600.20826_none_849fd3eba8a7b88a.manifest x86_microsoft-windows-r..gistry-trustedtypes_31bf3856ad364e35_6.1.7600.20826_none_849fd3eba8a7b88a (fix) CSI Manifest All Zeros CSI File Replaced File: x86_microsoft-windows-r..gistry-trustedtypes_31bf3856ad364e35_6.1.7600.20826_none_849fd3eba8a7b88a.manifest From: C:\Windows\CheckSur\v1.0\windows6.1-7601-x86-cab4.cab (f) CSI Manifest All Zeros 0x00000000 winsxs\Manifests\x86_microsoft-windows-r..gistry-trustedtypes_31bf3856ad364e35_6.1.7600.16695_none_83c9857c8fc3c5d9.manifest x86_microsoft-windows-r..gistry-trustedtypes_31bf3856ad364e35_6.1.7600.16695_none_83c9857c8fc3c5d9 (fix) CSI Manifest All Zeros CSI File Replaced File: x86_microsoft-windows-r..gistry-trustedtypes_31bf3856ad364e35_6.1.7600.16695_none_83c9857c8fc3c5d9.manifest From: C:\Windows\CheckSur\v1.0\windows6.1-7601-x86-cab4.cab (f) CSI F Mark Missing 0x00000002 f!ntdll.dll x86_microsoft-windows-ntdll_31bf3856ad364e35_6.1.7600.20826_none_5978b89a766d479e (fix) CSI F Mark Missing CSI Registry Item Repaired Wrote x86_microsoft-windows-ntdll_31bf3856ad364e35_6.1.7600.20826_none_5978b89a766d479e\f!ntdll.dll: ntdll.dll (f) CSI F Mark Missing 0x00000002 f!ntoskrnl.exe x86_microsoft-windows-os-kernel_31bf3856ad364e35_6.1.7600.20826_none_6cd23bf92e62adf0 (fix) CSI F Mark Missing CSI Registry Item Repaired Wrote x86_microsoft-windows-os-kernel_31bf3856ad364e35_6.1.7600.20826_none_6cd23bf92e62adf0\f!ntoskrnl.exe: ntoskrnl.exe (f) CSI F Mark Missing 0x00000002 f!ntkrnlpa.exe x86_microsoft-windows-os-kernel_31bf3856ad364e35_6.1.7600.20826_none_6cd23bf92e62adf0 (fix) CSI F Mark Missing CSI Registry Item Repaired Wrote x86_microsoft-windows-os-kernel_31bf3856ad364e35_6.1.7600.20826_none_6cd23bf92e62adf0\f!ntkrnlpa.exe: ntkrnlpa.exe (f) CSI F Mark Missing 0x00000002 f!ntoskrnl.exe x86_microsoft-windows-os-kernel_31bf3856ad364e35_6.1.7600.16695_none_6bfbed8a157ebb3f (fix) CSI F Mark Missing CSI Registry Item Repaired Wrote x86_microsoft-windows-os-kernel_31bf3856ad364e35_6.1.7600.16695_none_6bfbed8a157ebb3f\f!ntoskrnl.exe: ntoskrnl.exe (f) CSI F Mark Missing 0x00000002 f!ntkrnlpa.exe x86_microsoft-windows-os-kernel_31bf3856ad364e35_6.1.7600.16695_none_6bfbed8a157ebb3f (fix) CSI F Mark Missing CSI Registry Item Repaired Wrote x86_microsoft-windows-os-kernel_31bf3856ad364e35_6.1.7600.16695_none_6bfbed8a157ebb3f\f!ntkrnlpa.exe: ntkrnlpa.exe (f) CSI F Mark Missing 0x00000002 f!ntdll.dll x86_microsoft-windows-ntdll_31bf3856ad364e35_6.1.7600.16695_none_58a26a2b5d8954ed (fix) CSI F Mark Missing CSI Registry Item Repaired Wrote x86_microsoft-windows-ntdll_31bf3856ad364e35_6.1.7600.16695_none_58a26a2b5d8954ed\f!ntdll.dll: ntdll.dll Summary: Seconds executed: 300 Found 16 errors Fixed 16 errors CSI Manifest All Zeros Total count: 6 Fixed: CSI Manifest All Zeros. Total count: 6 CSI F Mark Missing Total count: 6 Fixed: CSI F Mark Missing. Total count: 6 CBS MUM Corrupt Total count: 4 Fixed: CBS MUM Corrupt. Total count: 4 Fixed: CBS Paired File. Total count: 4 ================================= All looked good. I then ran Windows Update to install the update in question and it seemed to install ok but prompted me to reboot. After reboot, Windows Update says the update still needs to be installed. Attempting to install the update at this point results in the same failure as I began with. Running CheckSUR again produces the same, seemingly good, log but the install/reboot/failure cycle just repeats. I have also tried renaming the Catroot2 folder and renaming all oem*.* files as recommended in other MS support articles. I don't know what else to try. Any assistance to resolve this will be greatly appreciated. Thanks, David

Hi, Thanks for posting in Microsoft TechNet Forum. If you receive Windows Update error 800B0100, it means that a file needed by Windows Update is corrupted or missing. Generally speaking, installing System Update Readiness Tool can help fix problems. Currently, I suggest you try the following steps to check this issue: 1. Use SFC to scan whole system files: How to use the System File Checker tool to troubleshoot missing or corrupted system files on Windows Vista or on Windows 7 2. Reset the windows update components: How do I reset Windows Update components? Note: this article works for Windows 7, too. 3. If this issue persists, you could try the following methods to troubleshoot: You cannot install some updates or programs Hope it helps. Alex Zhao TechNet Subscriber Support in forum. If you have any feedback on our support, please contact tngfb@microsoft.comPlease remember to click Mark as Answer on the post that helps you, and to click Unmark as Answer if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

Hi, I am just writing to see how everything is going. I would appreciate if you could get back to me at your earliest convenience. If you have any questions or concerns related to this issue, please drop me a note. I appreciate your time and I look forward to hearing from you. Alex Zhao TechNet Subscriber Support in forum. If you have any feedback on our support, please contact tngfb@microsoft.comPlease remember to click Mark as Answer on the post that helps you, and to click Unmark as Answer if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

Hi Alex, Thanks for your suggestions. I've been unable to get access to the machine in question but hope to get access in the next couple of days. I'll post back as soon as possible. Regards, David

Hi, Please feel free to let me know the status of this issue, I am glad to be of assistance. Alex Zhao TechNet Subscriber Support in forum. If you have any feedback on our support, please contact tngfb@microsoft.comPlease remember to click Mark as Answer on the post that helps you, and to click Unmark as Answer if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

Hi Alex, I tried your suggestions in turn. SFC found to issues. I reset the update components as per KB971058 - problem persists. I tried everything in KB822798 except an in-place upgrade (this refers to Windows XP). Unfortunately, the problem persists just the same as before. Do you have any further suggestions? Thanks, David

PROBLEM: Windows Update failed to install KB2393802 and generated an error code 0x800B0100. The error code 0x800B0100 equates to TRUST_E_NOSIGNATURE which means "No signature was present in the subject." The following steps would need to be taken in order to try resolving this issue: 1. Download the appropriate System Update Readiness Tool package (x86 or x64) for Windows 7 as outlined in KB947821. 947821 Description of the System Update Readiness Tool for Windows Vista, for Windows Server 2008, for Windows 7, and for Windows Server 2008 R2 http://support.microsoft.com/default.aspx?scid=kb;EN-US;947821 2. Execute the System Update Readiness Tool package for Windows 7. 3. Once completed, review the CheckSUR.log from the bottom of the log scrolling up and locate the value 0x800B0100. This will provide you with the name of the file(s) that may be missing or corrupted, which most of the times may be either a *.MUM or *.CAT file. 4. Then go to a Windows 7 machine that was able to successfully install that *.MUM or *.CAT file and copy both *.MUM and *.CAT to the affected Windows 7 machine that is unable to install KB2393802. 5. After both *.MUM and *.CAT to the affected Windows 7 machine, proceed in trying to re-install KB2393802 on the affected Windows 7 machine. 6. If the above steps 1-5 fail, then as a last resort try one of the following Methods 1, 3, 4, 5, 6, 7, 8, 9, 10, 11 and/or 12 outlined in KB2509997. 2509997 Unable to install updates in Windows Vista, Windows 7, Windows Server 2008 and Windows Server 2008 R2 http://support.microsoft.com/default.aspx?scid=kb;en-US;2509997 7. If neither KB947821 and KB2509997 resolved your issue and KB2393802 fails to install again, please call Microsoft Technical Support and create a case to further troubleshoot this issue and provide them the following 3 files: • %SYSTEMROOT%\Logs\CBS\CBS.log • %SYSTEMROOT%\Logs\CBS\CheckSUR.log • %SYSTEMROOT%\Logs\CBS\CheckSUR.persist.logKetan Thakkar | Microsoft Online Community Support

In the end I opted for an in-place upgrade as I expected it to be a quicker solution than going through the motions with MS Tech Support. The in-place upgrade went smoothly and fixed the problem. If anyone else wants to carry out the same procedure, the steps can be found at: http://www.sevenforums.com/tutorials/3413-repair-install.html David