Error 0x800b0100 installing KB2778344 - Win 7 SP1 x86

[brianeger]

I have wandered through many forums, trying to get this one fixed. This update is in our February patches from SCCM. Every time it tries to install it fails. I have tried to install the update manually, getting the same failure. I have tried renaming the SoftwareDistribution folder and manually installing the update. I have tried all of the steps in KB956702. The client with this problem has over 30 applications installed and doesn't really want to re-image his PC.
Over 5,000 other PCs in our network have this patch installed successfully.

 

[tom982]

Hello brianeger, welcome to Sysnative!

Your CheckSUR log is showing a bit of corruption which will need to be dealt with to clear this error.

=================================
Checking System Update Readiness.
Binary Version 6.1.7601.21645
Package Version 18.0
2013-03-26 19:26

Checking Windows Servicing Packages

Checking Package Manifests and Catalogs
(f)    CBS MUM Corrupt    0x800F0900    servicing\Packages\Package_2_for_KB2778344~31bf3856ad364e35~x86~~6.1.1.0.mum        Line 1: 
(f)    CBS Catalog Corrupt    0x800B0100    servicing\Packages\Package_2_for_KB2778344~31bf3856ad364e35~x86~~6.1.1.0.cat        
(f)    CBS MUM Corrupt    0x800F0900    servicing\Packages\Package_for_KB2778344_SP1~31bf3856ad364e35~x86~~6.1.1.0.mum        Line 1: 
(f)    CBS Catalog Corrupt    0x800B0100    servicing\Packages\Package_for_KB2778344_SP1~31bf3856ad364e35~x86~~6.1.1.0.cat        
(f)    CBS MUM Corrupt    0x800F0900    servicing\Packages\Package_for_KB2778344~31bf3856ad364e35~x86~~6.1.1.0.mum        Line 1: 
(f)    CBS Catalog Corrupt    0x800B0100    servicing\Packages\Package_for_KB2778344~31bf3856ad364e35~x86~~6.1.1.0.cat        

Checking Package Watchlist

Checking Component Watchlist

Checking Packages

Checking Component Store
(f)    CSI Manifest All Zeros    0x00000000    winsxs\Manifests\x86_microsoft-windows-win32k_31bf3856ad364e35_6.1.7601.18043_none_bad95351f8e24525.manifest    x86_microsoft-windows-win32k_31bf3856ad364e35_6.1.7601.18043_none_bad95351f8e24525    
(f)    CSI Manifest All Zeros    0x00000000    winsxs\Manifests\x86_microsoft-windows-win32k_31bf3856ad364e35_6.1.7601.22209_none_bb94336f11da0a5c.manifest    x86_microsoft-windows-win32k_31bf3856ad364e35_6.1.7601.22209_none_bb94336f11da0a5c    

Summary:
Seconds executed: 154
 Found 8 errors
  CSI Manifest All Zeros Total count: 2
  CBS MUM Corrupt Total count: 3
  CBS Catalog Corrupt Total count: 3

Unavailable repair files:
    winsxs\manifests\x86_microsoft-windows-win32k_31bf3856ad364e35_6.1.7601.18043_none_bad95351f8e24525.manifest
    winsxs\manifests\x86_microsoft-windows-win32k_31bf3856ad364e35_6.1.7601.22209_none_bb94336f11da0a5c.manifest
    servicing\packages\Package_2_for_KB2778344~31bf3856ad364e35~x86~~6.1.1.0.mum
    servicing\packages\Package_2_for_KB2778344~31bf3856ad364e35~x86~~6.1.1.0.mum
    servicing\packages\Package_for_KB2778344_SP1~31bf3856ad364e35~x86~~6.1.1.0.mum
    servicing\packages\Package_for_KB2778344_SP1~31bf3856ad364e35~x86~~6.1.1.0.mum
    servicing\packages\Package_for_KB2778344~31bf3856ad364e35~x86~~6.1.1.0.mum
    servicing\packages\Package_for_KB2778344~31bf3856ad364e35~x86~~6.1.1.0.mum
    servicing\packages\Package_2_for_KB2778344~31bf3856ad364e35~x86~~6.1.1.0.cat
    servicing\packages\Package_2_for_KB2778344~31bf3856ad364e35~x86~~6.1.1.0.cat
    servicing\packages\Package_for_KB2778344_SP1~31bf3856ad364e35~x86~~6.1.1.0.cat
    servicing\packages\Package_for_KB2778344_SP1~31bf3856ad364e35~x86~~6.1.1.0.cat
    servicing\packages\Package_for_KB2778344~31bf3856ad364e35~x86~~6.1.1.0.cat
    servicing\packages\Package_for_KB2778344~31bf3856ad364e35~x86~~6.1.1.0.cat

Windows Update Package Replacement

Warning: this fix is specific to the user in this thread. No one else should follow these instructions as it may cause more harm than good. If you are after assistance, please start a thread of your own.

1. Please download the attached file, Packs.zip and save this to your Desktop.
2. Right-click on the file and select Extract All...
3. Tick the box labelled Show extracted files when complete then click Extract
4. A window will open showing two folders, Manifests and Packages
5. Open the Manifests folder and copy the files into the following folder (if there are any files)
   
   C:\Windows\Temp\CheckSur\Winsxs\Manifests
   
   
6. Open the Packages folder and copy the files into the following folder (if there are any files)
   
   C:\Windows\Temp\CheckSur\Servicing\Packages
   
   
7. Run the System Update Readiness Tool (SURT) again
8. When the SURT finishes installing, copy (Ctrl + C) and paste (Ctrl + V) the contents of the SURT log into your next post please:
   
   C:\Windows\Logs\CBS\CheckSUR.persist.log

You will probably be shown the error code 0x8024200D after performing this fix, if so, please download and install the update from this link. It must be downloaded using Internet Explorer.

Download Security Update for Windows 7 (KB2778344) from Official Microsoft Download Center

Tom

 

[brianeger]

Hi Tom, Thanks for the help.
I downloaded the Packs. Copied the files to the C:\Windows\Temp\CheckSur folders
I ran SURT again.
I then downloaded the Update and tried to install it - same error
I have attached the CheckSUR.persist.log file inline - did that work?

View attachment CheckSUR.persist.log

 

[tom982]

Hi brianeger,

Are you sure you did step 6? Your log is showing that you haven't :)

Tom

 

[brianeger]

Sorry, misread the folder name. My mistake. Thanks.

The manual install worked!!!

Awesome!

Hope SCCM notices.

 

[tom982]

Hi brianeger,

No worries, glad to hear everything is working now!

Tom

 

[brianeger]

Sorry to say, after I installed the patch manually, and I did the restart, the machine went into a startup repair loop.
The PC is about 800 kilometers away, so I had to get a technician available to have a look at it.
What do I do now?

 

[niemiro]

Sorry to say, after I installed the patch manually, and I did the restart, the machine went into a startup repair loop.
The PC is about 800 kilometers away, so I had to get a technician available to have a look at it.
What do I do now?

Do you yet have any details about what failed?

The fix provided only altered .cat, .mum, and .manifest files. These will not affect startup, even if completely deleted, corrupted, whatever. Not possible.

But I will admit that a Windows Kernel Update could potentially cause a problem if failed: MS13-016: Vulnerabilities in Windows kernel-mode driver could allow elevation of privilege: February 12, 2013

To me, this suggests a deeper issue. Neither a 0x800B0100 error code nor your particular CheckSUR.log carry much risk of a startup failure or hint at a deep underlying corruption, both are relatively shallow and not boot critical.

Let us know if the normal stuff like Safe Mode, System Restore, etc., work out.

Additionally, if you can, extract a copy of C:\Windows\Winsxs\Pending.xml and upload it.

We need to narrow down whether a file didn't get updated properly (a part of the kernel is missing), in which case we will copy it back), or whether this is a Configuring Windows/Reverting Changes loop, in which case we will try to revert the actions manually and take a deeper look at what went wrong. Here, you are lucky to be running Windows 7. It is much more fixable than Vista with the same problem.

Richard

 

[brianeger]

So far all I have is this attached picture.
The technician has done a system restore to 4:30 this morning, and it worked. I can now get to the PC and have a look at things.
The System restore said it had an indeterminant error 0x8000FFFFF. But we could log into the PC.

 

[niemiro]

Thank you.

Please re-run the System Update Readiness Tool, and post a new CBS folder, with, if it still exists, any C:\Windows\Winsxs\pending.xml files (including with an extra, randomly generated file extension on the end too)

Richard.

 

[brianeger]

No pending.xml files in c:\Windows\winsxs folder.
We restored the OS to the 4:30 AM backup.
I have attached the cbs folder zipped.
Our monthly patches came out th eother day for voluntary install. I think I will apply them and see, Monday, when the technician is back at work...

 

[brianeger]

I thought I attached this one last time

 

[niemiro]

The logs are a bit out of date at the moment. Can you please put through Tom's fix again and re-run the System Update Readiness Tool.

Then can you post C:\Windows\Logs\CBS before trying to restart the computer.

Finally, I would suggest putting through the updates one at a time or in small groups, and install only through Windows Update. Don't put it through manually for the time being, especially if it is not offered via Windows Update for some reason, although I would be very surprised if that is the cause. The conditionals are built into large XML files contained within the updates themselves.

Richard