Endless Windows Update Errors, now 800B0100 and 8024200D

[jsg68]

I've been struggling with Windows Update. Any help would be greatly appreciated.

I've had a series of different error codes, and after trying seemingly endless interventions, the current codes I'm receiving are:

800B0100
8024200D

The first has been there since the beginning. I've had a number of other different codes along the way, prior to the current state.

After searching, I've tried like a zillion MS FixIt tools, CheckSUR (a few times now), WindowsUpdateDiagnostic.diagcab, which initially found several problems it couldn't fix, but after various interventions, now reports everything good. sfc /scannow finds no issues.

I don't believe it's directly the source of the problem, but the origin of this system is unusual. This is a VM running under Parallels on an iMac. I migrated a Dell XPS 8300 to a VM, and then uninstalled a bunch of software I didn't need.

That system was running Win7 Ultimate x64, but I only have an extra license/key for Win7 Pro, so I cloned the VM, in order to downgrade it to Pro. Downgrading required a couple of minor registry edits (from Ultimate to Professional) to get past install checks, and I had to uninstall SP1 to get past the installer claiming the current install was newer than my install disc.

Did an in-place upgrade install. Worked fine. Cleaned out some more software I didn't need. Started running Windows Update -- naturally, I ended up with a few hundred updates required, and had to go through multiple restart/update cycles to see and install them.

Everything was going fine. The system was performing well -- and booting much, much faster than it had been. Then with maybe a dozen updates left to go, including IE updates for 8, and new updates to install IE, 9, 10 and 11, started getting Windows update errors.

Tried everything I could find via google. Did get a few updates installed along the way, but still have the same basic issue. Having tried so many things, I now no longer have any restore points going back to before the problem. Hoping I can find a way to fix this, rather than having to revert to cloning the original VM again, and having to repeat the laborious downgrade and windows update process.

Any suggestions? Happy to run diagnostics that may help.

Jonathan

 

[NoelDP]

Please follow the Windows Update Posting Instructions and post the requested data

If the file is too large (8MB compressed), remove the older CBSPersist cab files until the final file is below the limit - you can always post them separately after zipping them. (the forum doesn't allow the upload of bare CAB files, for a number of reasons)

Please also post your c:\windows\windowsupdate.log file

 

[jsg68]

Sorry for missing the posting instructions. I had performed each of the specified interventions, but re-executed them just now, and re-confirmed the Windows Update error codes, still 800B0100 and 8024200D.

sfc /scannow finds no integrity violations. I can't attach the CBS.zip file, as it is over 8MB (9.28 MB) even with all cabs removed. The uncompressed log is very large, perhaps because of all the interventions I've tried. So I've posted it here:

http://xfields.net/files/CBS.zip

Thanks for your help.

 

[jsg68]

Here's the Windowsupdate.log.

 

[NoelDP]

CheckSUR shows the following problems...

Summary:
Seconds executed: 944
 Found 48 errors
  CSI Manifest All Zeros Total count: 20
  CBS MUM Corrupt Total count: 14
  CBS Catalog Corrupt Total count: 14
Unavailable repair files:
 winsxs\manifests\x86_microsoft-windows-ie-iecompat_31bf3856ad364e35_8.0.7600.21028_none_bc4d84a2222a1af5.manifest
 winsxs\manifests\amd64_microsoft-windows-ie-iecompat_31bf3856ad364e35_8.0.7600.21028_none_186c2025da878c2b.manifest
 winsxs\manifests\x86_microsoft-windows-charmap_31bf3856ad364e35_6.1.7601.18648_none_f444a3cc02b20fea.manifest
 winsxs\manifests\amd64_microsoft-windows-charmap_31bf3856ad364e35_6.1.7601.18648_none_50633f4fbb0f8120.manifest
 winsxs\manifests\x86_microsoft-windows-charmap_31bf3856ad364e35_6.1.7601.22856_none_f4c171fd1bd9961e.manifest
 winsxs\manifests\amd64_microsoft-windows-charmap_31bf3856ad364e35_6.1.7601.22856_none_50e00d80d4370754.manifest
 winsxs\manifests\amd64_microsoft-windows-w..for-management-core_31bf3856ad364e35_6.1.7601.18619_none_2890675ec3a2ec11.manifest
 winsxs\manifests\wow64_microsoft-windows-w..for-management-core_31bf3856ad364e35_6.1.7601.18619_none_32e511b0f803ae0c.manifest
 winsxs\manifests\x86_microsoft-windows-ie-iecompat_31bf3856ad364e35_8.0.7601.17667_none_bd7e2cc106540a42.manifest
 winsxs\manifests\amd64_microsoft-windows-ie-iecompat_31bf3856ad364e35_8.0.7601.17667_none_199cc844beb17b78.manifest
 winsxs\manifests\amd64_microsoft-windows-rastls_31bf3856ad364e35_6.1.7601.22792_none_cabc39528023cdfa.manifest
 winsxs\manifests\x86_microsoft-windows-rastls_31bf3856ad364e35_6.1.7601.22792_none_6e9d9dcec7c65cc4.manifest
 winsxs\manifests\x86_microsoft-windows-ie-iecompat_31bf3856ad364e35_8.0.7601.21789_none_bdf42a481f80149c.manifest
 winsxs\manifests\amd64_microsoft-windows-ie-iecompat_31bf3856ad364e35_8.0.7601.21789_none_1a12c5cbd7dd85d2.manifest
 winsxs\manifests\amd64_microsoft-windows-rastls_31bf3856ad364e35_6.1.7601.18584_none_ca3f6b2166fc47c6.manifest
 winsxs\manifests\x86_microsoft-windows-rastls_31bf3856ad364e35_6.1.7601.18584_none_6e20cf9dae9ed690.manifest
 winsxs\manifests\x86_microsoft-windows-ie-iecompat_31bf3856ad364e35_8.0.7600.16865_none_bb95cf27092f6ba8.manifest
 winsxs\manifests\amd64_microsoft-windows-ie-iecompat_31bf3856ad364e35_8.0.7600.16865_none_17b46aaac18cdcde.manifest
 winsxs\manifests\wow64_microsoft-windows-w..for-management-core_31bf3856ad364e35_6.1.7601.22826_none_3360df98112c1ae9.manifest
 winsxs\manifests\amd64_microsoft-windows-w..for-management-core_31bf3856ad364e35_6.1.7601.22826_none_290c3545dccb58ee.manifest
 servicing\packages\Package_1_for_KB2598845~31bf3856ad364e35~amd64~~6.1.1.0.mum
 servicing\packages\Package_1_for_KB2598845~31bf3856ad364e35~amd64~~6.1.1.0.mum
 servicing\packages\Package_1_for_KB3006121~31bf3856ad364e35~amd64~~6.1.1.0.mum
 servicing\packages\Package_1_for_KB3006121~31bf3856ad364e35~amd64~~6.1.1.0.mum
 servicing\packages\Package_1_for_KB3006625~31bf3856ad364e35~amd64~~6.1.1.0.mum
 servicing\packages\Package_1_for_KB3006625~31bf3856ad364e35~amd64~~6.1.1.0.mum
 servicing\packages\Package_2_for_KB2977292~31bf3856ad364e35~amd64~~6.1.1.0.mum
 servicing\packages\Package_2_for_KB2977292~31bf3856ad364e35~amd64~~6.1.1.0.mum
 servicing\packages\Package_3_for_KB2598845~31bf3856ad364e35~amd64~~6.1.1.0.mum
 servicing\packages\Package_3_for_KB2598845~31bf3856ad364e35~amd64~~6.1.1.0.mum
 servicing\packages\Package_for_KB2598845_RTM~31bf3856ad364e35~amd64~~6.1.1.0.mum
 servicing\packages\Package_for_KB2598845_RTM~31bf3856ad364e35~amd64~~6.1.1.0.mum
 servicing\packages\Package_for_KB2598845_SP1~31bf3856ad364e35~amd64~~6.1.1.0.mum
 servicing\packages\Package_for_KB2598845_SP1~31bf3856ad364e35~amd64~~6.1.1.0.mum
 servicing\packages\Package_for_KB2598845~31bf3856ad364e35~amd64~~6.1.1.0.mum
 servicing\packages\Package_for_KB2598845~31bf3856ad364e35~amd64~~6.1.1.0.mum
 servicing\packages\Package_for_KB2977292_SP1~31bf3856ad364e35~amd64~~6.1.1.0.mum
 servicing\packages\Package_for_KB2977292_SP1~31bf3856ad364e35~amd64~~6.1.1.0.mum
 servicing\packages\Package_for_KB2977292~31bf3856ad364e35~amd64~~6.1.1.0.mum
 servicing\packages\Package_for_KB2977292~31bf3856ad364e35~amd64~~6.1.1.0.mum
 servicing\packages\Package_for_KB3006121_SP1~31bf3856ad364e35~amd64~~6.1.1.0.mum
 servicing\packages\Package_for_KB3006121_SP1~31bf3856ad364e35~amd64~~6.1.1.0.mum
 servicing\packages\Package_for_KB3006121~31bf3856ad364e35~amd64~~6.1.1.0.mum
 servicing\packages\Package_for_KB3006121~31bf3856ad364e35~amd64~~6.1.1.0.mum
 servicing\packages\Package_for_KB3006625_SP1~31bf3856ad364e35~amd64~~6.1.1.0.mum
 servicing\packages\Package_for_KB3006625_SP1~31bf3856ad364e35~amd64~~6.1.1.0.mum
 servicing\packages\Package_for_KB3006625~31bf3856ad364e35~amd64~~6.1.1.0.mum
 servicing\packages\Package_for_KB3006625~31bf3856ad364e35~amd64~~6.1.1.0.mum

I don't think these will be too hard to fix - but I'm worried about the cause and timing.

When did you reinstall Windows last?
Have you had a malware infection?
When did you first notice problems updating?


The WU log shows the following errors which may also be easily fixable...

2015-01-04 08:14:43:124 1004 177c Report REPORT EVENT: {55FF2639-87A8-4547-BFC1-729A5B21C3ED} 2015-01-04 08:14:38:124-0500 1 182 101 {E0840035-6B21-4554-A6E9-2FFEBC99D9AA} 201 8024200d AutomaticUpdates Failure Content Install Installation Failure: Windows failed to install the following update with error 0x8024200d: Security Update for Windows 7 for x64-based Systems (KB2839894).
2015-01-04 08:14:43:124 1004 177c Report REPORT EVENT: {176D1C88-7F2C-41B1-A9A6-3707DCBF7A0C} 2015-01-04 08:14:38:646-0500 1 182 101 {CED3293C-2613-41FF-BD6A-D8525504C035} 201 8024200d AutomaticUpdates Failure Content Install Installation Failure: Windows failed to install the following update with error 0x8024200d: Security Update for Windows 7 for x64-based Systems (KB2957503).
2015-01-04 08:14:43:124 1004 177c Report REPORT EVENT: {4002D7C4-7C3F-4DAB-AAC3-88826277C709} 2015-01-04 08:14:39:779-0500 1 182 101 {C499223D-2F22-4626-BBE5-F5A35E7A5854} 204 8024200d AutomaticUpdates Failure Content Install Installation Failure: Windows failed to install the following update with error 0x8024200d: Security Update for Microsoft .NET Framework 3.5.1 on Windows 7 and Windows Server 2008 R2 SP1 for x64-based Systems (KB2861698).

 

[jsg68]

Windows was reinstalled (downgrade install to Win7 Pro) late on January 2nd. After that, nothing substantial was done with this system other than windows updates. There were close to 200 updates that installed without issue, before windows update ran into problems. (So many, owing to the fact that my install CDs are from the original production release of Win7.)

The problem started occurring in the wee hours of January 3rd -- I was basically in a continuous process of readying this system, so I went straight from cloning it, to reinstalling windows, to undergoing repetitive windows updates, until the problem occurred. I started trying to find fixes in those wee hours of the morning, then went to bed, and returned to trying to resolve the issue after waking up in the morning. Spent most of the day trying different interventions, without substantive improvement, before posting here.

To me, it seems most likely that the problem got created as a product of the windows update process, itself, since there really wasn't anything else going on. I don't even think I opened a browser until the problem had occurred, at which point I was searching for fixes.

If there is some malware infection, I believe it would have to have carried over from the original system the VM was created from, and survived the windows reinstall. I'm not aware of an infection on that system, and I'm running both Norton 360 and malwarebytes there. Norton 360 is still running on the current system. (Malwarebytes had stopped working, so I uninstalled it, and haven't tried to reinstall it yet.)

If there's something you'd suggest I do to check the system for malware, let me know.

Thanks.

 

[NoelDP]

Assuming a full MBAM scan comes up clean, then it may be OK - although I've recently come across a couple of nasty infections that appear to be able to hide from pretty much anything
I'll see what I can do to fix the CheckSUR problems first, and we'll see how it goes.

 

[NoelDP]

I've uploaded a file - jsgaa.zip - to my OneDrive at Noel's OneDrive
Please download and save it.
Right-click on the downloaded file, and select Extract all…
Extract to the default location - which will create a new folder jsgaa in the same place.
Open this folder - there should be two folders inside it (Manifests, and Packages)

Copy the content of the Packages folder to the folder
C:\Windows\Temp\CheckSur\Servicing\Packages

And the content of the manifests folder (.manifest files) into this folder:

C:\Windows\Temp\CheckSur\Winsxs\Manifests

Now run the CheckSUR tool again (it may take a while)

Post the new CheckSUR.log file, and the CheckSUR.persist.log file.

 

[jsg68]

Thanks, will do. And I reinstalled MBAM. Full scan comes up clean.

 

[jsg68]

CheckSUR.log appears to indicate all errors were fixed. Running Windows Update shows progress, but not complete resolution -- 3 of 8 important updates installed.

Now have error codes 8024200D and 2.

New CBS.zip and windowsupdate.log attached.

 

[jsg68]

Tried a second time, this time also selecting two optional updates. All 7 failed, with one additional error code: 9C59.

 

[NoelDP]

KB2598845, KB2957503, KB2861698 should all install if you use the standalone installer.
https://www.microsoft.com/en-gb/download/details.aspx?id=27804
Download Security Update for Windows 7 for x64-based Systems (KB2957503) from Official Microsoft Download Center
Download Security Update for Microsoft .NET Framework 3.5.1 on Windows 7 Service Pack 1 and Windows Server 2008 R2 Service Pack 1 from Official Microsoft Download Center

 

[jsg68]

KB2598845, KB2957503, KB2861698 should all install if you use the standalone installer.

Thanks for so much help, Noel. I really appreciate it.

I was able to install these three using the standalone installers. That left 2 important updates (one of which was IE9) and two option updates (IE10 and IE11).

Tried automatically installing the two important updates. IE9 installed. The other, KB2839894, failed with 8024200D. Restarted to complete installation of IE9. Windows update was now showing only the two optional updates. Installed them successfully, and restarted.

Then KB2839894 reappeared as an important update. Retried installing, failed again. Found the standalone installer, and installed it successfully. Restarted.

Windows Update then reported two cumulative updates for IE11. Successfully installed those automatically. Restarted.

Windows Update reported one more update for IE11. Succeeded, no restart required. No further updates reported.


Any idea why those four updates failed to install automatically? Should I be resigned to having to install some updates manually, from standalone installers, on this system, going forward? (I've never run into a persistent issue like this on a system, before.)

 

[NoelDP]

It's due to minor corruption somewhere in the SoftwareDistribution folder, I believe - it's enough to foil AU, but doesn't get in the way using the msu installers.

 

[jsg68]

I see.

I re-ran CheckSUR which looks all good.

Re-running Windows update diagnostic indicates some errors again. Does this shed any light on what the corruption might be, or how to resolve it?

Windows Update error 0x800F081F(2015-01-05-T-09_34_24A) Not Fixed
Cryptographic service components are not registered Not fixed
Service registration is missing or corrupt Fixed
Problems installing recent updates Fixed
Problems installing recent updates Fixed

 

[NoelDP]

The only one that concerns me there is the second one.

I'll see if I can work out what it may mean.