Win7E Update Failure 8024200D (+800B0100 and 800F0900)

F

freesbee

Member
Joined
May 7, 2014
Posts
6
...starting from 98 errors, following any possible guide on this and other websites, I could strip errors down to 3! These 3 errors are preventing 18 updates to install, all of them failing with 8024200D (in Windows Update), while in the CheckSUR turn out the well known 800B0100 and 800F0900
:banghead:
The machine is freshly installed, all possible guides and tutorials have been followed.
Win7E x64 SP1

Right now my CBS.log is 115 MBytes, so I'm skipping it. Here are the CheckSUR.
I'm not able to to locate the missing packages asked here anyhow!!!

Code: 
=================================
Checking System Update Readiness.
Binary Version 6.1.7601.22471
Package Version 23.0
2014-05-08 00:53

Checking Windows Servicing Packages

Checking Package Manifests and Catalogs
(f)    CBS MUM Corrupt    0x800F0900    servicing\Packages\Package_for_KB2862330~31bf3856ad364e35~amd64~~6.1.2.0.mum        Line 1: 
(f)    CBS Catalog Corrupt    0x800B0100    servicing\Packages\Package_for_KB2862330~31bf3856ad364e35~amd64~~6.1.2.0.cat        
(f)    CBS MUM Corrupt    0x800F0900    servicing\Packages\Package_for_KB2909210~31bf3856ad364e35~amd64~~6.1.1.0.mum        Line 1: 
(f)    CBS Catalog Corrupt    0x800B0100    servicing\Packages\Package_for_KB2909210~31bf3856ad364e35~amd64~~6.1.1.0.cat        
(f)    CBS MUM Corrupt    0x800F0900    servicing\Packages\Package_for_KB2930275~31bf3856ad364e35~amd64~~6.1.1.1.mum        Line 1: 
(f)    CBS Catalog Corrupt    0x800B0100    servicing\Packages\Package_for_KB2930275~31bf3856ad364e35~amd64~~6.1.1.1.cat        

Checking Package Watchlist

Checking Component Watchlist

Checking Packages

Checking Component Store

Summary:
Seconds executed: 89
 Found 6 errors
  CBS MUM Corrupt Total count: 3
  CBS Catalog Corrupt Total count: 3

Unavailable repair files:
    servicing\packages\Package_for_KB2862330~31bf3856ad364e35~amd64~~6.1.2.0.mum
    servicing\packages\Package_for_KB2862330~31bf3856ad364e35~amd64~~6.1.2.0.mum
    servicing\packages\Package_for_KB2909210~31bf3856ad364e35~amd64~~6.1.1.0.mum
    servicing\packages\Package_for_KB2909210~31bf3856ad364e35~amd64~~6.1.1.0.mum
    servicing\packages\Package_for_KB2930275~31bf3856ad364e35~amd64~~6.1.1.1.mum
    servicing\packages\Package_for_KB2930275~31bf3856ad364e35~amd64~~6.1.1.1.mum
    servicing\packages\Package_for_KB2862330~31bf3856ad364e35~amd64~~6.1.2.0.cat
    servicing\packages\Package_for_KB2862330~31bf3856ad364e35~amd64~~6.1.2.0.cat
    servicing\packages\Package_for_KB2909210~31bf3856ad364e35~amd64~~6.1.1.0.cat
    servicing\packages\Package_for_KB2909210~31bf3856ad364e35~amd64~~6.1.1.0.cat
    servicing\packages\Package_for_KB2930275~31bf3856ad364e35~amd64~~6.1.1.1.cat
    servicing\packages\Package_for_KB2930275~31bf3856ad364e35~amd64~~6.1.1.1.cat
(why do they get written twice is absolute mistery)

Any idea?
 

Attachments

Hello freesbee, welcome to Sysnative!

It's just gone 2am here and I was about to pack up for the night, but I thought I'd squeeze you in before I hit the sack. This will fix everything:

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

https://dl.dropboxusercontent.com/u/16537616/Fixes/SURT/freesbee/Packs.zip

For any updates failing with 0x8024200D, download them from the Microsoft website and they'll install with no problems :)

Tom
 
...nice try, but it didn't work ;)
The 18 updates are still failing as they were before (0x8024200D). By the way installing the .msu directly from Microsoft does NOT install the fix (that was of course my first attempt).

Here is the CheckSUR.persistent after rerunning the readiness tool:

Code: 
=================================
Checking System Update Readiness.
Binary Version 6.1.7601.22471
Package Version 23.0
2014-05-08 17:50

Checking Windows Servicing Packages

Checking Package Manifests and Catalogs
(f)    CBS MUM Corrupt    0x800F0900    servicing\Packages\Package_for_KB2862330~31bf3856ad364e35~amd64~~6.1.2.0.mum        Line 1: 
(fix)    CBS MUM Corrupt    CBS File Replaced    Package_for_KB2862330~31bf3856ad364e35~amd64~~6.1.2.0.mum from Cabinet: C:\Windows\CheckSur\v1.0\windows6.1-7601-x64-clientcab4.cab.
(fix)    CBS Paired File    CBS File also Replaced    Package_for_KB2862330~31bf3856ad364e35~amd64~~6.1.2.0.cat from Cabinet: C:\Windows\CheckSur\v1.0\windows6.1-7601-x64-clientcab4.cab.
(f)    CBS MUM Corrupt    0x800F0900    servicing\Packages\Package_for_KB2909210~31bf3856ad364e35~amd64~~6.1.1.0.mum        Line 1: 
(fix)    CBS MUM Corrupt    CBS File Replaced    Package_for_KB2909210~31bf3856ad364e35~amd64~~6.1.1.0.mum from Cabinet: C:\Windows\CheckSur\v1.0\windows6.1-7601-x64-clientcab4.cab.
(fix)    CBS Paired File    CBS File also Replaced    Package_for_KB2909210~31bf3856ad364e35~amd64~~6.1.1.0.cat from Cabinet: C:\Windows\CheckSur\v1.0\windows6.1-7601-x64-clientcab4.cab.
(f)    CBS MUM Corrupt    0x800F0900    servicing\Packages\Package_for_KB2930275~31bf3856ad364e35~amd64~~6.1.1.1.mum        Line 1: 
(fix)    CBS MUM Corrupt    CBS File Replaced    Package_for_KB2930275~31bf3856ad364e35~amd64~~6.1.1.1.mum from Cabinet: C:\Windows\CheckSur\v1.0\windows6.1-7601-x64-clientcab4.cab.
(fix)    CBS Paired File    CBS File also Replaced    Package_for_KB2930275~31bf3856ad364e35~amd64~~6.1.1.1.cat 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: 75
 Found 3 errors
 Fixed 3 errors
  CBS MUM Corrupt Total count: 3
  Fixed: CBS MUM Corrupt.  Total count: 3
  Fixed: CBS Paired File.  Total count: 3

...strangely it says "fixed" but still finding 3 errors.
Attached you have the full versions of the logfiles.
View attachment CBS_afterFix.zip

P.S.: I already tried this fix, even if I wasn't sure where to get the right *.cat and *.mum files, since they are not present in the .msu downloaded from MS
 
...it's even worse :D
We went from a system which failed to install 18 updates, to a system that BSODs during boot (also attempting to repair it fails miserably).
Code: 
STOP: c000021a
0x000000000 (0xC0000428 0x00010770)
Now I can access the system drive only from my other OS, because there is noway to boot the "freshly installed" Win7.
I'm very close to formatting the system, unless you don't have some other idea to try...
 
Last edited:
Sorry to hear things have taken a turn for the worse, but I can assure you it wasn't my fix, it's completely unrelated :)

That's just the way the CheckSUR log writes its output, we had three issues and my fix fixed them all:

Code: 
 Found 3 errors
 Fixed 3 errors

These packages were actually in that KB2930275 but you wouldn't have found them if you didn't know what to look for - they are known as the default packages and are named update.cat and update.mum.

I'm confident I can fix the 0x8024200D but due to the BSOD issue preventing you from booting, I think your best bet is to do a clean install. Sorry!

Tom
 
tom982 said:
Sorry to hear things have taken a turn for the worse, but I can assure you it wasn't my fix, it's completely unrelated :)
(...)
Click to expand...

...don't worry: I know the "microsoft quality" ;) (afterall I'm sysadmin of a quite interesting system!!)
tom982 said:
(...)
These packages were actually in that KB2930275 but you wouldn't have found them if you didn't know what to look for - they are known as the default packages and are named update.cat and update.mum.
Click to expand...
well: this is an interesting info!!

I already did the clean install a couple of hours after the BSOD: I'm organized to be able to reinstall a machine quite quickly (I've written a number of scripts for updating/maintaining all machines in the company, so installing new machines is not that tragic). I was curios to see if corrupted windows updates could be repaired...

Anyway I find your business model quite interesting, and I'll come back here in the future... I'm quite busy, but I think that if you establish a "scripting & deployment" section I could be quite helpful there. Did you know that almost 50% of the world browses with the ms crashware IE just because most of sysadmins are to lazy to be able to deploy and maintain other browsers as for example FireFox?

Till then, take care!!
 
You must log in or register to reply here.

Has Sysnative Forums helped you? Please consider donating to help us support the site!

Back
Top