Windows Updates failing with 800B0100, 8024200D and 80070490

Page 1 of 2 12 LastLast

  1. TerryinOz
    Posts : 6
    Windows 7 Home Premium Service Pack 1 (build 7601)
       New #1

    Windows Updates failing with 800B0100, 8024200D and 80070490


    Hi,

    I have six updates from February that I cannot get to install and I would like some help please as I haven't been able to resolve the problems after a few days of trying.

    I have run the SURT and SFC /scannow as per the instructions and attached them as files to this post along with the list of 6 fixes that are failing and the screenprint of the errors message from the Windows Update screen after it attempts to install them.

    A fix that came through the other day was applied successfully, however for these six I still haven't been able to get them to apply either individually or manually. There was also un optional update for IE 11 that was failing however I removed IE as I don't use it much.

    A message from the SFC in the CMD window was
    Beginning verification phase of system scan.
    Verification 100% complete.
    Windows Resource Protection found corrupt files but was unable to fix some of them.
    I hope someone is able to help me out or point me in the right direction.

    Regards,
    Terry
    Attached Thumbnails Attached Thumbnails Windows Updates failing with 800B0100, 8024200D and 80070490-updateerrors.png   Windows Updates failing with 800B0100, 8024200D and 80070490-updatesfailing.png  
      My Computer
    Quote Quote

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

    I need the CheckSUR scan results, please.


    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. TerryinOz
    Posts : 6
    Windows 7 Home Premium Service Pack 1 (build 7601)
    Thread Starter
       New #3

    Hi,

    I have attached the correct output this time and included the update log also.

    Thanks,
    Terry
    Windows Updates failing with 800B0100, 8024200D and 80070490 Attached Files
      My Computer
    Quote Quote

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

    Here's the CheckSUR summary (in part)
    Code:
    Summary:
Seconds executed: 2110
 Found 57 errors
  CSI Manifest Missing Total count: 14
  CSI Manifest All Zeros Total count: 20
  CBS MUM Missing Total count: 5
  CBS MUM Corrupt Total count: 9
  CBS Catalog Corrupt Total count: 9
Unavailable repair files:
 winsxs\manifests\x86_microsoft-windows-ieinstal_31bf3856ad364e35_11.2.9600.17633_none_6ec024e8ee61ec2c.manifest
 winsxs\manifests\x86_497cf4fa8ae4d16b68484e54db17e8e7_31bf3856ad364e35_6.1.7601.22920_none_76f893f469f83f9f.manifest
 winsxs\manifests\x86_microsoft-windows-scripting-vbscript_31bf3856ad364e35_11.2.9600.17420_none_ce9332ff8a96f3d8.manifest
 winsxs\manifests\x86_microsoft-windows-ieinstal_31bf3856ad364e35_11.2.9600.17501_none_6ec82186ee5c50f4.manifest
 winsxs\manifests\x86_microsoft-windows-lsa_31bf3856ad364e35_6.1.7601.22920_none_a8ccaf4ed436b8b6.manifest
 winsxs\manifests\x86_microsoft-windows-msauditevtlog_31bf3856ad364e35_6.1.7601.22920_none_c9c49edaefd8f53c.manifest
 winsxs\manifests\x86_microsoft-windows-lsa.resources_31bf3856ad364e35_6.1.7601.22920_en-us_8929f8de0e06d7a7.manifest
 winsxs\manifests\x86_49702b4c4567900f95308fa1c2d0851d_31bf3856ad364e35_6.1.7601.18588_none_a6dc1b8f4c243448.manifest
 winsxs\manifests\x86_microsoft-windows-security-credssp_31bf3856ad364e35_6.1.7601.22920_none_c63a55fc18fb8551.manifest
 winsxs\manifests\x86_microsoft-windows-security-kerberos_31bf3856ad364e35_6.1.7601.22920_none_e95901b828391078.manifest
 winsxs\manifests\x86_microsoft-windows-ncrypt-dll_31bf3856ad364e35_6.1.7601.22920_none_60607a1e69078f23.manifest
 winsxs\manifests\x86_microsoft-windows-security-ntlm_31bf3856ad364e35_6.1.7601.22920_none_7f35115fd9f64398.manifest
 winsxs\manifests\x86_microsoft-windows-security-digest_31bf3856ad364e35_6.1.7601.22920_none_3d4f6fa3f4209449.manifest
 winsxs\manifests\x86_microsoft-windows-lsa.resources_31bf3856ad364e35_6.1.7601.18714_en-us_88af2b40f4dd8421.manifest
 winsxs\manifests\x86_microsoft-windows-security-schannel_31bf3856ad364e35_6.1.7601.22920_none_24986f9accae5741.manifest
 winsxs\manifests\x86_microsoft-windows-m..ditevtlog.resources_31bf3856ad364e35_6.1.7601.18714_en-us_5c0cfae2b81e93c7.manifest
 winsxs\manifests\x86_63a5e4d61967c75a46383316fa1a8969_31bf3856ad364e35_11.2.9600.17420_none_1067c4acc6e8d110.manifest
 winsxs\manifests\x86_4955e86b7ec6cba4c2aec5bf83882e5b_31bf3856ad364e35_11.2.9600.17239_none_531db386af1cdb7b.manifest
 winsxs\manifests\x86_microsoft-windows-scripting-vbscript_31bf3856ad364e35_11.2.9600.17633_none_ce7e4f198aa691f4.manifest
 winsxs\manifests\x86_microsoft-windows-lsa_31bf3856ad364e35_6.1.7601.18714_none_a851e1b1bb0d6530.manifest
 winsxs\manifests\x86_microsoft-windows-msauditevtlog_31bf3856ad364e35_6.1.7601.18714_none_c949d13dd6afa1b6.manifest
 winsxs\manifests\x86_1256eb77a73d7cae6d4547dd2adab76e_31bf3856ad364e35_11.2.9600.17633_none_8dd1da9846be14f6.manifest
 winsxs\manifests\x86_microsoft-windows-scripting-vbscript_31bf3856ad364e35_11.2.9600.17501_none_ce864bb78aa0f6bc.manifest
 winsxs\manifests\x86_63b74ba08993a14ff0760b202a66e124_31bf3856ad364e35_11.2.9600.17207_none_6f485e54c5a52501.manifest
 winsxs\manifests\x86_microsoft-windows-security-kerberos_31bf3856ad364e35_6.1.7601.18714_none_e8de341b0f0fbcf2.manifest
 winsxs\manifests\x86_microsoft-windows-ncrypt-dll_31bf3856ad364e35_6.1.7601.18714_none_5fe5ac814fde3b9d.manifest
 winsxs\manifests\x86_microsoft-windows-security-schannel_31bf3856ad364e35_6.1.7601.18714_none_241da1fdb38503bb.manifest
 winsxs\manifests\x86_microsoft-windows-security-ntlm_31bf3856ad364e35_6.1.7601.18714_none_7eba43c2c0ccf012.manifest
 winsxs\manifests\x86_microsoft-windows-security-digest_31bf3856ad364e35_6.1.7601.18714_none_3cd4a206daf740c3.manifest
 winsxs\manifests\x86_microsoft-windows-security-credssp_31bf3856ad364e35_6.1.7601.18714_none_c5bf885effd231cb.manifest
 winsxs\manifests\x86_63644923aa5d1d380721163cf03cf74d_31bf3856ad364e35_11.2.9600.17280_none_c57ee3c7ee101c24.manifest
 winsxs\manifests\x86_126e835b5e178e3a75b30548cb60cef8_31bf3856ad364e35_11.2.9600.17633_none_830f365448494a78.manifest
 winsxs\manifests\x86_49514fca0679c825976789b8f983b8e5_31bf3856ad364e35_11.2.9600.17501_none_76c79d815bc68add.manifest
 winsxs\manifests\x86_microsoft-windows-m..ditevtlog.resources_31bf3856ad364e35_6.1.7601.22920_en-us_5c87c87fd147e74d.manifest
 servicing\packages\Package_30_for_KB3023607~31bf3856ad364e35~x86~~6.1.1.0.mum
 servicing\packages\Package_30_for_KB3023607~31bf3856ad364e35~x86~~6.1.1.0.mum
 servicing\packages\Package_31_for_KB3023607~31bf3856ad364e35~x86~~6.1.1.0.mum
 servicing\packages\Package_31_for_KB3023607~31bf3856ad364e35~x86~~6.1.1.0.mum
 servicing\packages\Package_32_for_KB3023607~31bf3856ad364e35~x86~~6.1.1.0.mum
 servicing\packages\Package_32_for_KB3023607~31bf3856ad364e35~x86~~6.1.1.0.mum
 servicing\packages\Package_57_for_KB3023607~31bf3856ad364e35~x86~~6.1.1.0.mum
 servicing\packages\Package_57_for_KB3023607~31bf3856ad364e35~x86~~6.1.1.0.mum
 servicing\packages\Package_58_for_KB3023607~31bf3856ad364e35~x86~~6.1.1.0.mum
 servicing\packages\Package_58_for_KB3023607~31bf3856ad364e35~x86~~6.1.1.0.mum
 servicing\packages\Package_59_for_KB3023607~31bf3856ad364e35~x86~~6.1.1.0.mum
 servicing\packages\Package_59_for_KB3023607~31bf3856ad364e35~x86~~6.1.1.0.mum
 servicing\packages\Package_60_for_KB3023607~31bf3856ad364e35~x86~~6.1.1.0.mum
 servicing\packages\Package_60_for_KB3023607~31bf3856ad364e35~x86~~6.1.1.0.mum
 servicing\packages\Package_for_KB3023607_SP1~31bf3856ad364e35~x86~~6.1.1.0.mum
 servicing\packages\Package_for_KB3023607_SP1~31bf3856ad364e35~x86~~6.1.1.0.mum
 servicing\packages\Package_for_KB3023607~31bf3856ad364e35~x86~~6.1.1.0.mum
 servicing\packages\Package_for_KB3023607~31bf3856ad364e35~x86~~6.1.1.0.mum
 servicing\packages\Package_39_for_KB3004375~31bf3856ad364e35~x86~~6.1.3.1.mum
 servicing\packages\Package_39_for_KB3004394~31bf3856ad364e35~x86~~6.1.2.0.mum
 servicing\packages\Package_39_for_KB3008923~31bf3856ad364e35~x86~~11.2.1.0.mum
 servicing\packages\Package_39_for_KB3013410~31bf3856ad364e35~x86~~6.1.1.2.mum
 servicing\packages\Package_39_for_KB3021952~31bf3856ad364e35~x86~~11.2.1.0.mum
    I'll post a fix when I can get to it.
      My Computer
    Quote Quote

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

    I've uploaded a file - tizaa.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 tizaa 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

  8. TerryinOz
    Posts : 6
    Windows 7 Home Premium Service Pack 1 (build 7601)
    Thread Starter
       New #6

    Noel,

    I have run the CheckSUR tool and it fixed 43 out 53 problems so I tried the original fixes again and this time applied 5 out of the 6 that were not being applied, so just one outstanding at the moment.

    I reran the CheckSUR tool and have included the contents of C:\Windows\Logs\CBS in the attached file and would appreciate it if you could take a look and do your magic again for this remaining issue.

    Regards,
    Terry
      My Computer
    Quote Quote

  10. TerryinOz
    Posts : 6
    Windows 7 Home Premium Service Pack 1 (build 7601)
    Thread Starter
       New #7

    Noel,

    I have run the CheckSUR tool and it fixed 43 out 53 problems so I tried the original fixes again and applied 5 out of the 6 that were not being applied, so just one outstanding at the moment.

    I reran the CheckSUR tool and have included the contents of C:\Windows\Logs\CBS in the attached file and would appreciate it if you could take a look at the output.

    Regards,
    Terry
      My Computer
    Quote Quote

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

    You now have a completely different set of problems

    Here's the errors from the body of the CheckSUR report...
    Code:
    Checking Package Manifests and Catalogs
(f) CBS MUM Corrupt 0x00000000 servicing\Packages\PA16AD~1.MUM  Expected file name Package_39_for_KB3004375~31bf3856ad364e35~x86~~6.1.3.1.mum does not match the actual file name
(f) CBS Catalog Missing 0x00000002 servicing\Packages\PA16AD~1.cat  
(f) CBS MUM Corrupt 0x00000000 servicing\Packages\PA76E9~1.MUM  Expected file name Package_39_for_KB3004394~31bf3856ad364e35~x86~~6.1.2.0.mum does not match the actual file name
(f) CBS Catalog Missing 0x00000002 servicing\Packages\PA76E9~1.cat  
(f) CBS MUM Corrupt 0x00000000 servicing\Packages\PA79CF~1.MUM  Expected file name Package_3_for_KB2547666~31bf3856ad364e35~x86~~6.1.1.0.mum does not match the actual file name
(f) CBS Catalog Missing 0x00000002 servicing\Packages\PA79CF~1.cat  
(f) CBS MUM Corrupt 0x00000000 servicing\Packages\PA8A58~1.MUM  Expected file name Package_39_for_KB3021952~31bf3856ad364e35~x86~~11.2.1.0.mum does not match the actual file name
(f) CBS Catalog Missing 0x00000002 servicing\Packages\PA8A58~1.cat  
(f) CBS MUM Corrupt 0x00000000 servicing\Packages\PAB33E~1.MUM  Expected file name Package_39_for_KB3013410~31bf3856ad364e35~x86~~6.1.1.2.mum does not match the actual file name
(f) CBS Catalog Missing 0x00000002 servicing\Packages\PAB33E~1.cat  
(f) CBS MUM Corrupt 0x00000000 servicing\Packages\PABADF~1.MUM  Expected file name Package_39_for_KB3008923~31bf3856ad364e35~x86~~11.2.1.0.mum does not match the actual file name
(f) CBS Catalog Missing 0x00000002 servicing\Packages\PABADF~1.cat
    I am pretty certain that the problem here arises from the use of some kind of registry 'optimiser' or 'cleaner'. If this is the case, please uninstall it.


    I think your best option is to use System Restore to go back to a week ago (if you can) then then start the process again with a new set of CheckSUR and SFC runs.
    Please do NOT attempt to install updates until we have fixed all the identified problems.
      My Computer
    Quote Quote

  12. Layback Bear
    Posts : 25,847
    Windows 10 Pro. 64/ version 1709 Windows 7 Pro/64
       New #9

    A thought.
    From TerryinOz specs.

    Antivirus AVAST and COMODO
    Two anti virus programs at the same time.

    TerryinOz could you list all security programs you have installed.

    Could you also list all Tuneup, Cleanup, Speedup or Registry Tools you use?
      My Computer
    Quote Quote

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

    Hmmm - good point! (Hopefully he means Avast AV and Comodo Firewall, but...?)
      My Computer
    Quote Quote

 
Page 1 of 2 12 LastLast

  Related Discussions
Hello! I'm having a pretty hard time with a computer. There are six updates which are failing - 3068708 3071756 3060716 3101746 3080149 2726535 2965788
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...
(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...
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...
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...
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 08:19.
Find Us