Hello again!
Well, your logs are very unusual. You have a rare strain of the error, hence why the usual fix didn't fix it.
Code:
=================================
Checking System Update Readiness.
Binary Version 6.1.7601.21645
Package Version 13.0
2012-01-08 17:19
Checking Windows Servicing Packages
Checking Package Manifests and Catalogs
(f) CBS MUM Corrupt 0x800B0100 servicing\Packages\Package_2_for_KB2556532~31bf3856ad364e35~amd64~~6.1.1.1.mum servicing\Packages\Package_2_for_KB2556532~31bf3856ad364e35~amd64~~6.1.1.1.cat Package manifest cannot be validated by the corresponding catalog
(fix) CBS MUM Corrupt CBS File Replaced Package_2_for_KB2556532~31bf3856ad364e35~amd64~~6.1.1.1.mum from Cabinet: C:\Windows\CheckSur\v1.0\windows6.1-7601-x64-clientcab4.cab.
Checking Package Watchlist
Checking Component Watchlist
Checking Packages
Checking Component Store
Summary:
Seconds executed: 580
Found 1 errors
Fixed 1 errors
CBS MUM Corrupt Total count: 1
Fixed: CBS MUM Corrupt. Total count: 1
Notice that the (f) line (FATAL error) is followed by a (fix) line. The error should be fixed.
Also notice where the replacement file came from:
"from Cabinet: C:\Windows\CheckSur\v1.0\windows6.1-7601-x64-clientcab4.cab"
It came out of the cabinet files which I made, using the files I provided you with yesterday.
However, if you look at yesterday's log, there is an inconsistency. All (f) logs are followed by a (fix) line or two, and no (fix) lines are followed by a (fix) failed line.
However, at the bottom there is a
Code:
Unavailable repair files:
servicing\packages\Package_2_for_KB2556532~31bf3856ad364e35~amd64~~6.1.1.1.cat
servicing\packages\Package_for_KB2345886_RTM~31bf3856ad364e35~amd64~~6.1.1.2.cat
servicing\packages\Package_for_KB2345886_RTM~31bf3856ad364e35~amd64~~6.1.1.2.cat
section, which should only when there are failures in a log file.
The error in today's log was fixed in yesterdays log. It is being repeatedly fixed, but keeps being re-detected as a failure.
The only hint at a problem is "Package manifest cannot be validated by the corresponding catalog".
I just need to test this, one last time. When I get home this evening, I shall examine the fix I sent you yesterday for clues as to what may have caused this.
In the mean time, can you please the System Update Readiness Tool one last time, and then provide me with the C:\Windows\Logs\CBS\CheckSUR.persist.log
Whatever it may seem, your problem is far from common! But there is no reason to be concerned yet. A second fix this evening will probably sort the problem out.
Richard