Windows 7 Forums

Welcome to Windows 7 Forums. Our forum is dedicated to helping you find support and solutions for any problems regarding your Windows 7 PC be it Dell, HP, Acer, Asus or a custom build. We also provide an extensive Windows 7 tutorial section that covers a wide range of tips and tricks.


Windows 7: 4 Updates Failed, 800B0100, 80073712, 8024200D (Win 7 Pro x64)

28 Sep 2014   #1
Overand

Windows 7 Professional x64
 
 
Updates Failed, strange 8.3 files in servicing\packages (7 Pro x64)

(Original title: 4 Updates Failed, 800B0100, 80073712, 8024200D (Win 7 Pro x64))

Edit: SEE the SECOND post (reply) now - most of the issues in this first one are resolved

Hey folks - this is a pretty-darned-close to factory Windows 7 X64 SP1 Pro system. (Acer TravelMate P645-MG-7653). (The good news is I imaged the drive when I first got the system, so if I *have* to I can restore to factory).

A number of Windows Updates have installed correctly, but I've gotten stuck on several (KB2871997, KB2892074, KB2982378).

Prior steps:

sfc /scannow - no errors
Ran the system update readiness check tool - found errors, fixed some, not others. (Windows Update error 0x8007000D(and a timestamp), Cryptographic service components are not registered)
Deleted the software distribution folder
(A few other things, MS fixits for update issues, etc).

Normally, this is the point where I'd reinstall, but given it's a laptop with some technologies i'm not very familiar with (Switchable radeon/intel graphics) and some installed tools I can't get an installer for, so I'm trying to fix it.


Here's the output from a tool called SFCFix that was recommended to me for diagnostic purposes:

Code:
Code:
SFCFix version 2.4.1.0 by niemiro.
Start time: 2014-09-28 19:05:57.959
Not using a script file.

-- snip whitespace--

AutoAnalysis::
WARNING: Manifest damage on component "x86_microsoft-windows-ncrypt-dll_31bf3856ad364e35_6.1.7601.22736_none_605ba822690a48d0". See CBS logfile for more details.

--snip whitespace--

SUMMARY: Some corruptions could not be fixed automatically. Seek advice from helper or sysnative.com.
   CBS & SFC total detected corruption count:     1
   CBS & SFC total unimportant corruption count:  0
   CBS & SFC total fixed corruption count:        0
   SURT total detected corruption count:          75
   SURT total unimportant corruption count:       0
   SURT total fixed corruption count:             0
AutoAnalysis:: directive completed successfully.

-- snip whitespace --

Successfully processed all directives.
SFCFix version 2.4.1.0 by niemiro has completed.
Currently storing 0 datablocks.
Finish time: 2014-09-28 19:10:35.686
----------------------EOF-----------------------
OLD. IGNORECBS File (14 MB) Dropbox Link: https://www.dropbox.com/s/rufij6mp8r...and-1.zip?dl=0

Snippet from the CheckSUR.log

Code:
Checking Package Manifests and Catalogs
(f)    CBS MUM Corrupt    0x00000000    servicing\Packages\PA1A4B~1.MUM        Expected file name Package_53_for_KB2791765~31bf3856ad364e35~amd64~~6.1.1.2.mum does not match the actual file name
(f)    CBS Catalog Missing    0x00000002    servicing\Packages\PA1A4B~1.cat        
(f)    CBS MUM Corrupt    0x00000000    servicing\Packages\PA2771~1.MUM        Expected file name Package_56_for_KB2868725~31bf3856ad364e35~amd64~~6.1.1.1.mum does not match the actual file name
(f)    CBS Catalog Missing    0x00000002    servicing\Packages\PA2771~1.cat        
(f)    CBS MUM Corrupt    0x00000000    servicing\Packages\PA543D~1.MUM        Expected file name Package_54_for_KB2492386~31bf3856ad364e35~amd64~~6.1.1.0.mum does not match the actual file name
(f)    CBS Catalog Missing    0x00000002    servicing\Packages\PA543D~1.cat        
(f)    CBS MUM Corrupt    0x00000000    servicing\Packages\PA6730~1.MUM        Expected file name Package_110_for_KB2570791~31bf3856ad364e35~amd64~~6.1.1.1.mum does not match the actual file name
(f)    CBS Catalog Missing    0x00000002    servicing\Packages\PA6730~1.cat        
(f)    CBS MUM Corrupt    0x00000000    servicing\Packages\PA89EF~1.MUM        Expected file name Package_53_for_KB2762895~31bf3856ad364e35~amd64~~6.1.1.0.mum does not match the actual file name
(f)    CBS Catalog Missing    0x00000002    servicing\Packages\PA89EF~1.cat        
(f)    CBS MUM Corrupt    0x800F0900    servicing\Packages\Package_102_for_KB2982378~31bf3856ad364e35~amd64~~6.1.1.0.mum        Line 1: 
(f)    CBS Catalog Corrupt    0x800B0100    servicing\Packages\Package_102_for_KB2982378~31bf3856ad364e35~amd64~~6.1.1.0.cat        
(f)    CBS MUM Corrupt    0x800F0900    servicing\Packages\Package_103_for_KB2982378~31bf3856ad364e35~amd64~~6.1.1.0.mum        Line 1: 
(f)    CBS Catalog Corrupt    0x800B0100    servicing\Packages\Package_103_for_KB2982378~31bf3856ad364e35~amd64~~6.1.1.0.cat        
(f)    CBS MUM Corrupt    0x800F0900    servicing\Packages\Package_104_for_KB2982378~31bf3856ad364e35~amd64~~6.1.1.0.mum        Line 1: 
(f)    CBS Catalog Corrupt    0x800B0100    servicing\Packages\Package_104_for_KB2982378~31bf3856ad364e35~amd64~~6.1.1.0.cat        
(f)    CBS MUM Corrupt    0x800F0900    servicing\Packages\Package_105_for_KB2982378~31bf3856ad364e35~amd64~~6.1.1.0.mum        Line 1: 
(f)    CBS Catalog Corrupt    0x800B0100    servicing\Packages\Package_105_for_KB2982378~31bf3856ad364e35~amd64~~6.1.1.0.cat        
(f)    CBS MUM Corrupt    0x800F0900    servicing\Packages\Package_108_for_KB2982378~31bf3856ad364e35~amd64~~6.1.1.0.mum        Line 1: 
(f)    CBS Catalog Corrupt    0x800B0100    servicing\Packages\Package_108_for_KB2982378~31bf3856ad364e35~amd64~~6.1.1.0.cat        
(f)    CBS MUM Corrupt    0x800F0900    servicing\Packages\Package_109_for_KB2982378~31bf3856ad364e35~amd64~~6.1.1.0.mum        Line 1: 
(f)    CBS Catalog Corrupt    0x800B0100    servicing\Packages\Package_109_for_KB2982378~31bf3856ad364e35~amd64~~6.1.1.0.cat        
(f)    CBS MUM Corrupt    0x800F0900    servicing\Packages\Package_110_for_KB2982378~31bf3856ad364e35~amd64~~6.1.1.0.mum        Line 1: 
(f)    CBS Catalog Corrupt    0x800B0100    servicing\Packages\Package_110_for_KB2982378~31bf3856ad364e35~amd64~~6.1.1.0.cat        
(f)    CBS MUM Corrupt    0x800F0900    servicing\Packages\Package_111_for_KB2982378~31bf3856ad364e35~amd64~~6.1.1.0.mum        Line 1: 
(f)    CBS Catalog Corrupt    0x800B0100    servicing\Packages\Package_111_for_KB2982378~31bf3856ad364e35~amd64~~6.1.1.0.cat        
(f)    CBS MUM Corrupt    0x800F0900    servicing\Packages\Package_129_for_KB2973351~31bf3856ad364e35~amd64~~6.1.1.1.mum        Line 1: 
(f)    CBS Catalog Corrupt    0x800B0100    servicing\Packages\Package_129_for_KB2973351~31bf3856ad364e35~amd64~~6.1.1.1.cat



My System SpecsSystem Spec
.
28 Sep 2014   #2
Overand

Windows 7 Professional x64
 
 

OK - I made some progress! I used the update readyness tool again, with the .MSU files from the Microsoft Updates Catalog in the c:\Windows\CheckSUR\packages folder, and got through *some* updates.

Now, however, what I have seems *weird.*

It seems that there are a number of 8.3 (short files names rather than the modern Long File Names) .MUM and .CAT files in c:\Windows\servicing\packages. They're all, in fact, referenced below.

I have NO idea why those are there - but I'm certainly wary of removing them without anyone telling me that's what I should do.

Current CBS log: https://www.dropbox.com/s/enoxlwgbz6...and-2.zip?dl=0

Quote:
=================================
Checking System Update Readiness.
Binary Version 6.1.7601.22471
Package Version 25.0
2014-09-28 23:38

Checking Windows Servicing Packages

Checking Package Manifests and Catalogs
(f) CBS MUM Corrupt 0x00000000 servicing\Packages\PA1A4B~1.MUM Expected file name Package_53_for_KB2791765~31bf3856ad364e35~amd64~~6.1.1.2.mum does not match the actual file name
(f) CBS Catalog Missing 0x00000002 servicing\Packages\PA1A4B~1.cat
(f) CBS MUM Corrupt 0x00000000 servicing\Packages\PA2771~1.MUM Expected file name Package_56_for_KB2868725~31bf3856ad364e35~amd64~~6.1.1.1.mum does not match the actual file name
(f) CBS Catalog Missing 0x00000002 servicing\Packages\PA2771~1.cat
(f) CBS MUM Corrupt 0x00000000 servicing\Packages\PA543D~1.MUM Expected file name Package_54_for_KB2492386~31bf3856ad364e35~amd64~~6.1.1.0.mum does not match the actual file name
(f) CBS Catalog Missing 0x00000002 servicing\Packages\PA543D~1.cat
(f) CBS MUM Corrupt 0x00000000 servicing\Packages\PA6730~1.MUM Expected file name Package_110_for_KB2570791~31bf3856ad364e35~amd64~~6.1.1.1.mum does not match the actual file name
(f) CBS Catalog Missing 0x00000002 servicing\Packages\PA6730~1.cat
(f) CBS MUM Corrupt 0x00000000 servicing\Packages\PA89EF~1.MUM Expected file name Package_53_for_KB2762895~31bf3856ad364e35~amd64~~6.1.1.0.mum does not match the actual file name
(f) CBS Catalog Missing 0x00000002 servicing\Packages\PA89EF~1.cat

Checking Package Watchlist

Checking Component Watchlist

Checking Packages

Checking Component Store

Summary:
Seconds executed: 267
Found 10 errors
CBS MUM Corrupt Total count: 5
CBS Catalog Missing Total count: 5

Unavailable repair files:
servicing\packages\PA1A4B~1.mum
servicing\packages\PA1A4B~1.mum
servicing\packages\PA2771~1.mum
servicing\packages\PA2771~1.mum
servicing\packages\PA543D~1.mum
servicing\packages\PA543D~1.mum
servicing\packages\PA6730~1.mum
servicing\packages\PA6730~1.mum
servicing\packages\PA89EF~1.mum
servicing\packages\PA89EF~1.mum
servicing\packages\PA1A4B~1.cat
servicing\packages\PA1A4B~1.cat
servicing\packages\PA2771~1.cat
servicing\packages\PA2771~1.cat
servicing\packages\PA543D~1.cat
servicing\packages\PA543D~1.cat
servicing\packages\PA6730~1.cat
servicing\packages\PA6730~1.cat
servicing\packages\PA89EF~1.cat
servicing\packages\PA89EF~1.cat
My System SpecsSystem Spec
29 Sep 2014   #3
NoelDP

Microsoft Community Contributor Award Recipient

Win 7 x64 Home Premium (and x86 VirtualBox VM)/Win10
 
 

The latest batch of 'missing' files never actually existed - it seems that you have a problem with a pending installation.

It's an error type that I've only seen once before, and IIRC, we had to do a repair install to fix it.
I'm going to call for a second opinion on this as I don't have the time currently to do the research necessary.
Don't run away!
My System SpecsSystem Spec
.

29 Sep 2014   #4
Overand

Windows 7 Professional x64
 
 

I'm not sure I concur! Those .cab and .mum files with the MSDOS style filenames do actually exist (in c:\windows\servicing\packages), see the (ugly, via RDP) screenshot below!

More possibly relevant info - this had some sort of McAfee trial on it, before any of these updates, but I uninstalled it *and* used the McAfee uninstaller tool. (Some sort of norton cloud backup tool too, and same deal, removed & used the norton tool).


My System SpecsSystem Spec
29 Sep 2014   #5
NoelDP

Microsoft Community Contributor Award Recipient

Win 7 x64 Home Premium (and x86 VirtualBox VM)/Win10
 
 

They may exist on your machine - but they certainly shouldn't!

Please upload a couple of the .MUM files, and I'll take a look and see what they are supposed to be called.
My System SpecsSystem Spec
29 Sep 2014   #6
Overand

Windows 7 Professional x64
 
 

The CheckSUR.log quoted above offered some indications as to what *it* thought they should be called, but here you go!

https://www.dropbox.com/s/gigcp0ltol...m-cat.zip?dl=0

The whole thing is very strange, to me.
My System SpecsSystem Spec
29 Sep 2014   #7
NoelDP

Microsoft Community Contributor Award Recipient

Win 7 x64 Home Premium (and x86 VirtualBox VM)/Win10
 
 

...and to me!
Let's take an example...
The file "PA89EF~1.MUM"
Should be called "Package_53_for_KB2762895~31bf3856ad364e35~amd64~~6.1.1.0.mum"
It may be that Windows has recognised the file from its hash, rather than the filename - and this error is the result.
The question then becomes - does the final file exist at all in the folder?
If it does, what effect does removing the temporary file have?
If it doesn't - what would be the effect of adding the correct files via CheckSUR?

Also - is there a corresponding error in the registry which is linking to the 8.3 filename rather than the long one? If so, how do we deal with it?
Which of the CAT file is directly related to this file?

... and so on for each MUM file.

You appear to have one MUM/CAT pair from each of 5 updates - and a spare CAT file from another.
These problem updates date back as far as March 2011, and "Package_54_for_KB2492386~31bf3856ad364e35~amd64~~6.1.1.0.mum"

Do either of these files already exist in the Servicing\Packages folder?
My System SpecsSystem Spec
29 Sep 2014   #8
Overand

Windows 7 Professional x64
 
 

Intreresting! I checked, and all of the files those things are supposed to be (as in the CheckSUR.log) do exist, both as .cat and .mum.

Given the file dates on this, either they were extracted from somewhere with their datestamps intact, this is an issue dating to the original installation of the OS, there was some sort of filesystem corruption, or some sort of not-actually-filesystem-corruption but an erroneous copy made for some reason.

I went ahead and searched the entire registry for "PA89EF~1" - nothing. (That's one of the .MUM ones) - I also searched for PA4DDC~1 (which is one of the cat files), still nothing.

Even though I can't really tell which CAT files are what, I'm quite tempted to just move these files off, maybe re-run the Update Readiness tool (maybe) - and try to install updates again.

Thoughts?
My System SpecsSystem Spec
30 Sep 2014   #9
NoelDP

Microsoft Community Contributor Award Recipient

Win 7 x64 Home Premium (and x86 VirtualBox VM)/Win10
 
 

That's my thought as well - I've just never tried it before.
My System SpecsSystem Spec
30 Sep 2014   #10
Overand

Windows 7 Professional x64
 
 

Well, I deleted the files, then ran SURT. When I try to run updates, I get "Installation Failure: Windows failed to install the following update with error 0x8024200d: Security Update for Windows 7 for x64-based Systems (KB2892074)." in the event log.

The CBS directory is attached here, but you can see the basic log is clean.

https://www.dropbox.com/s/1su90gjy1l...elete.zip?dl=0

Code:
=================================
Checking System Update Readiness.
Binary Version 6.1.7601.22471
Package Version 25.0
2014-09-30 23:31

Checking Windows Servicing Packages

Checking Package Manifests and Catalogs

Checking Package Watchlist

Checking Component Watchlist

Checking Packages

Checking Component Store

Summary:
Seconds executed: 200
 No errors detected
My System SpecsSystem Spec
Reply

 4 Updates Failed, 800B0100, 80073712, 8024200D (Win 7 Pro x64)




Thread Tools Search this Thread
Search this Thread:

Advanced Search




Similar help and support threads
Thread Forum
Windows update error codes, 800B0100, 80073712, 8024200D
Hi there, When I run windows update I receive a few errors, along with numerous failed updates. I have attached my zipped CBS folder and a screenshot in the below link, as the CBS folder was too large to attach. https://onedrive.live.com/?cid=B85F8D81CC1FE97A&id=B85F8D81CC1FE97A!160 ...
Windows Updates & Activation
Failed Windows Update Errors 800B0100 and 8024200D
Hi Folks, Stumbled across this forum hoping to find an answer to my problem, Fresh install of Win 7 Home Premium 64 Bit, Windows Update downloaded and installed approx 120 updates but is constantly failing on two, these being KB2912390 and KB2978092, both fail with the errors 800B0100 and 8024200D....
Windows Updates & Activation
Continued Failing of 3 Updates: Code 800B0100 and 8024200D
I'm trying to play certain Steam games, but there's an issue, and it says one way to fix it is to get the .NET Framework up to date. I just recently formatted my hard drive, and I had many updates to take care of. I've been able to fix the errors for all but 3 of the updates. Updates KB2862335 and...
Windows Updates & Activation
Win7 home 64bits, Update crash error code 800B0100, 80073712, 8024200D
Hello, For few week, i can't update my windows 7, each try : crash error code 800B0100, 80073712, 8024200D. At each shut down i have 2 very fast update. It's weird :huh: I did try : - install System Update Readiness Tool - Sfcscann: 100% verification Windows Resource Protection did not...
Windows Updates & Activation
windows 7 x64 updates failing, errors 800B0100 and 8024200D
I keep getting error that these updates keep failing. i have already tried the windows troubleshooting and it didnt help. i also have tried the windows update reset. i should also note that yesterday 36 failed but for some reason today when i ran the update again it accepted some of them. i have...
Windows Updates & Activation
Updates fail to install, errors: 800B0100 and 8024200D
Dear experts and pros, since a couple of months I am having trouble with windows update. After not using my desktop for quite a while (probably in the period of June till September or October 2013). I switched on again and wanted to do all the updates that had accumulated. After a series of...
Windows Updates & Activation


Our Sites

Site Links

About Us

Find Us

Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

Designer Media Ltd

All times are GMT -5. The time now is 15:36.

Twitter Facebook Google+



Windows 7 Forums

Seven Forums Android App Seven Forums IOS App