Can't update Windows Code 800B0100 and Code 8024200D

Page 1 of 2 12 LastLast

  1. MattTG12
    Posts : 21
    Windows 7 Ultimate x64
       New #1

    Can't update Windows Code 800B0100 and Code 8024200D


    I haven't been able to update Windows for a while now. There are 13 updates that cannot download.

    I have Error code 800B0100 and Error code 8024200D

    Please help ASAP.
    My CBS file is too large to post, what should I do?
      My Computer
    Quote Quote

  3. NoelDP
    Posts : 21,482
    Win 7 x64 Home Premium (and x86 VirtualBox VM)/Win10
       New #2

    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 the C:\Windows\windowsudpate.log file
      My Computer
    Quote Quote

  4. MattTG12
    Posts : 21
    Windows 7 Ultimate x64
    Thread Starter
       New #3

    Thank you for responding NoelDP,

    The info is posted below
    Can't update Windows Code 800B0100 and Code 8024200D Attached Files
      My Computer
    Quote Quote

  6. NoelDP
    Posts : 21,482
    Win 7 x64 Home Premium (and x86 VirtualBox VM)/Win10
       New #4

    That's only some of the requested data - you haven't posted the CheckSUR.log file at all, and there's no SFC data in the CBS.log that you did post.

    Please follow the instructions.
      My Computer
    Quote Quote

  7. MattTG12
    Posts : 21
    Windows 7 Ultimate x64
    Thread Starter
       New #5

    Sorry about that.

    This should be the rest of the files
    Can't update Windows Code 800B0100 and Code 8024200D Attached Files
      My Computer
    Quote Quote

  8. NoelDP
    Posts : 21,482
    Win 7 x64 Home Premium (and x86 VirtualBox VM)/Win10
       New #6

    Here's the problem list from the CheckSUR log...
    Code:
    Summary:
Seconds executed: 579
 Found 74 errors
  CSI Manifest All Zeros Total count: 22
  CBS MUM Corrupt Total count: 26
  CBS Catalog Corrupt Total count: 26

Unavailable repair files:
	winsxs\manifests\amd64_microsoft-windows-g..validatefntcache-02_31bf3856ad364e35_6.1.7601.17621_none_a6f11fcb312ed12d.manifest
	winsxs\manifests\amd64_microsoft-windows-webdavredir-davclient_31bf3856ad364e35_6.1.7601.22913_none_f27bfa1981fd5c4e.manifest
	winsxs\manifests\amd64_microsoft-windows-webdavredir-webclient_31bf3856ad364e35_6.1.7601.22913_none_b3d45a96e36fc54b.manifest
	winsxs\manifests\amd64_microsoft-windows-webdavredir-mrxdav_31bf3856ad364e35_6.1.7601.22913_none_73597611f579c664.manifest
	winsxs\manifests\amd64_microsoft-windows-audio-audiocore_31bf3856ad364e35_6.1.7601.22826_none_d546840d14634c73.manifest
	winsxs\manifests\wow64_microsoft-windows-audio-audiocore_31bf3856ad364e35_6.1.7601.22826_none_df9b2e5f48c40e6e.manifest
	winsxs\manifests\x86_microsoft-windows-webdavredir-webclient_31bf3856ad364e35_6.1.7601.22913_none_57b5bf132b125415.manifest
	winsxs\manifests\x86_microsoft-windows-webdavredir-davclient_31bf3856ad364e35_6.1.7601.22913_none_965d5e95c99feb18.manifest
	winsxs\manifests\amd64_microsoft-windows-webdavredir-mrxdav_31bf3856ad364e35_6.1.7601.18706_none_72dda82adc515987.manifest
	winsxs\manifests\amd64_microsoft-windows-webdavredir-clientonly_31bf3856ad364e35_6.1.7601.22913_none_35f3367c25772c2d.manifest
	winsxs\manifests\wow64_microsoft-windows-webdavredir-clientonly_31bf3856ad364e35_6.1.7601.22913_none_4047e0ce59d7ee28.manifest
	winsxs\manifests\wow64_microsoft-windows-audio-audiocore_31bf3856ad364e35_6.1.7601.18619_none_df1f60782f9ba191.manifest
	winsxs\manifests\amd64_microsoft-windows-audio-audiocore_31bf3856ad364e35_6.1.7601.18619_none_d4cab625fb3adf96.manifest
	winsxs\manifests\amd64_microsoft-windows-g..validatefntcache-02_31bf3856ad364e35_6.1.7600.16820_none_a509c27b34094bea.manifest
	winsxs\manifests\amd64_microsoft-windows-u..roundprocessmanager_31bf3856ad364e35_6.1.7601.18741_none_c45292cc0822d17a.manifest
	winsxs\manifests\x86_microsoft-windows-u..roundprocessmanager_31bf3856ad364e35_6.1.7601.18741_none_6833f7484fc56044.manifest
	winsxs\manifests\x86_microsoft-windows-d..frastructure-client_31bf3856ad364e35_6.1.7601.18713_none_4e10e2ae012ca4ab.manifest
	winsxs\manifests\amd64_microsoft-windows-u..roundprocessmanager_31bf3856ad364e35_6.1.7601.22948_none_c4e33383213a1fcc.manifest
	winsxs\manifests\x86_microsoft-windows-u..roundprocessmanager_31bf3856ad364e35_6.1.7601.22948_none_68c497ff68dcae96.manifest
	winsxs\manifests\amd64_microsoft-windows-c..rmance-powertracker_31bf3856ad364e35_6.1.7601.18713_none_838b9f400b1ebc7f.manifest
	winsxs\manifests\amd64_microsoft-windows-c..rformance-perftrack_31bf3856ad364e35_6.1.7601.18713_none_b9f8289f61811978.manifest
	winsxs\manifests\amd64_microsoft-windows-d..frastructure-client_31bf3856ad364e35_6.1.7601.18713_none_aa2f7e31b98a15e1.manifest
	servicing\packages\Package_11_for_KB2545698~31bf3856ad364e35~amd64~~6.1.1.3.mum
	servicing\packages\Package_11_for_KB2545698~31bf3856ad364e35~amd64~~6.1.1.3.mum
	servicing\packages\Package_12_for_KB2545698~31bf3856ad364e35~amd64~~6.1.1.3.mum
	servicing\packages\Package_12_for_KB2545698~31bf3856ad364e35~amd64~~6.1.1.3.mum
	servicing\packages\Package_17_for_KB2545698~31bf3856ad364e35~amd64~~6.1.1.3.mum
	servicing\packages\Package_17_for_KB2545698~31bf3856ad364e35~amd64~~6.1.1.3.mum
	servicing\packages\Package_1_for_KB3005607~31bf3856ad364e35~amd64~~6.1.1.0.mum
	servicing\packages\Package_1_for_KB3005607~31bf3856ad364e35~amd64~~6.1.1.0.mum
	servicing\packages\Package_1_for_KB3019215~31bf3856ad364e35~amd64~~6.1.1.1.mum
	servicing\packages\Package_1_for_KB3019215~31bf3856ad364e35~amd64~~6.1.1.1.mum
	servicing\packages\Package_1_for_KB3021917~31bf3856ad364e35~amd64~~6.1.1.3.mum
	servicing\packages\Package_1_for_KB3021917~31bf3856ad364e35~amd64~~6.1.1.3.mum
	servicing\packages\Package_2_for_KB2545698~31bf3856ad364e35~amd64~~6.1.1.3.mum
	servicing\packages\Package_2_for_KB2545698~31bf3856ad364e35~amd64~~6.1.1.3.mum
	servicing\packages\Package_2_for_KB3019215~31bf3856ad364e35~amd64~~6.1.1.1.mum
	servicing\packages\Package_2_for_KB3019215~31bf3856ad364e35~amd64~~6.1.1.1.mum
	servicing\packages\Package_2_for_KB3021917~31bf3856ad364e35~amd64~~6.1.1.3.mum
	servicing\packages\Package_2_for_KB3021917~31bf3856ad364e35~amd64~~6.1.1.3.mum
	servicing\packages\Package_2_for_KB3030377~31bf3856ad364e35~amd64~~6.1.1.2.mum
	servicing\packages\Package_2_for_KB3030377~31bf3856ad364e35~amd64~~6.1.1.2.mum
	servicing\packages\Package_3_for_KB2545698~31bf3856ad364e35~amd64~~6.1.1.3.mum
	servicing\packages\Package_3_for_KB2545698~31bf3856ad364e35~amd64~~6.1.1.3.mum
	servicing\packages\Package_3_for_KB3019215~31bf3856ad364e35~amd64~~6.1.1.1.mum
	servicing\packages\Package_3_for_KB3019215~31bf3856ad364e35~amd64~~6.1.1.1.mum
	servicing\packages\Package_3_for_KB3021917~31bf3856ad364e35~amd64~~6.1.1.3.mum
	servicing\packages\Package_3_for_KB3021917~31bf3856ad364e35~amd64~~6.1.1.3.mum
	servicing\packages\Package_5_for_KB3021917~31bf3856ad364e35~amd64~~6.1.1.3.mum
	servicing\packages\Package_5_for_KB3021917~31bf3856ad364e35~amd64~~6.1.1.3.mum
	servicing\packages\Package_8_for_KB2545698~31bf3856ad364e35~amd64~~6.1.1.3.mum
	servicing\packages\Package_8_for_KB2545698~31bf3856ad364e35~amd64~~6.1.1.3.mum
	servicing\packages\Package_for_KB2545698_RTM~31bf3856ad364e35~amd64~~6.1.1.3.mum
	servicing\packages\Package_for_KB2545698_RTM~31bf3856ad364e35~amd64~~6.1.1.3.mum
	servicing\packages\Package_for_KB2545698_SP1~31bf3856ad364e35~amd64~~6.1.1.3.mum
	servicing\packages\Package_for_KB2545698_SP1~31bf3856ad364e35~amd64~~6.1.1.3.mum
	servicing\packages\Package_for_KB2545698~31bf3856ad364e35~amd64~~6.1.1.3.mum
	servicing\packages\Package_for_KB2545698~31bf3856ad364e35~amd64~~6.1.1.3.mum
	servicing\packages\Package_for_KB3005607_SP1~31bf3856ad364e35~amd64~~6.1.1.0.mum
	servicing\packages\Package_for_KB3005607_SP1~31bf3856ad364e35~amd64~~6.1.1.0.mum
	servicing\packages\Package_for_KB3005607~31bf3856ad364e35~amd64~~6.1.1.0.mum
	servicing\packages\Package_for_KB3005607~31bf3856ad364e35~amd64~~6.1.1.0.mum
	servicing\packages\Package_for_KB3019215_SP1~31bf3856ad364e35~amd64~~6.1.1.1.mum
	servicing\packages\Package_for_KB3019215_SP1~31bf3856ad364e35~amd64~~6.1.1.1.mum
	servicing\packages\Package_for_KB3019215~31bf3856ad364e35~amd64~~6.1.1.1.mum
	servicing\packages\Package_for_KB3019215~31bf3856ad364e35~amd64~~6.1.1.1.mum
	servicing\packages\Package_for_KB3021917_SP1~31bf3856ad364e35~amd64~~6.1.1.3.mum
	servicing\packages\Package_for_KB3021917_SP1~31bf3856ad364e35~amd64~~6.1.1.3.mum
	servicing\packages\Package_for_KB3021917~31bf3856ad364e35~amd64~~6.1.1.3.mum
	servicing\packages\Package_for_KB3021917~31bf3856ad364e35~amd64~~6.1.1.3.mum
	servicing\packages\Package_for_KB3030377_SP1~31bf3856ad364e35~amd64~~6.1.1.2.mum
	servicing\packages\Package_for_KB3030377_SP1~31bf3856ad364e35~amd64~~6.1.1.2.mum
	servicing\packages\Package_for_KB3030377~31bf3856ad364e35~amd64~~6.1.1.2.mum
	servicing\packages\Package_for_KB3030377~31bf3856ad364e35~amd64~~6.1.1.2.mum
    I'll post a fix protocol when I can get to it - probably over the weekend
      My Computer
    Quote Quote

  10. NoelDP
    Posts : 21,482
    Win 7 x64 Home Premium (and x86 VirtualBox VM)/Win10
       New #7

    I've uploaded a file - mtgaa.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 mtgaa 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.
      My Computer
    Quote Quote

  11. MattTG12
    Posts : 21
    Windows 7 Ultimate x64
    Thread Starter
       New #8

    Here are the files
    Can't update Windows Code 800B0100 and Code 8024200D Attached Files
      My Computer
    Quote Quote

  12. NoelDP
    Posts : 21,482
    Win 7 x64 Home Premium (and x86 VirtualBox VM)/Win10
       New #9

    Great - all the CheckSUR errors are now fixed, and it's happy.
    Code:
    Summary:
Seconds executed: 166
 Found 48 errors
 Fixed 48 errors
  CSI Manifest All Zeros Total count: 22
  Fixed: CSI Manifest All Zeros.  Total count: 22
  CBS MUM Corrupt Total count: 26
  Fixed: CBS MUM Corrupt.  Total count: 26
  Fixed: CBS Paired File.  Total count: 26
    Please run SFC /SCANNOW again, and if that comes back clear, try Windows Update again. (if not, post back with the CBS.log file)
      My Computer
    Quote Quote

  13. MattTG12
    Posts : 21
    Windows 7 Ultimate x64
    Thread Starter
       New #10

    SFC /SCANNOW found some corrupt files

    Had to use winrar to compress CBS file.
      My Computer
    Quote Quote

 
Page 1 of 2 12 LastLast

  Related Discussions
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...
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...
Error Code 800B0100 and 8024200D
in Windows Updates & Activation

Hi can please get some help my laptop doesn't seem to want to install the following updates: Security Update for Windows 7 for x64-based Systems and windows 7 SP 1 try almost everything from downloading fix it and System Update Readiness Tool. Checking System Update Readiness. Binary...
Hello, I am receiving the titled errors during windows update, I checked at windows support and tried every answer given there with no success. in addition, i think that this might be the cause that BattleField 3 crashes all the time.
Our Sites
Site Links
About 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:51.
Find Us