Windows Updates failing with 800B0100, 8024200D and 80070490

[TerryinOz]

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

 

[NoelDP]

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

 

[TerryinOz]

Hi,

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

Thanks,
Terry

 

[NoelDP]

Here's the CheckSUR summary (in part)

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.

 

[NoelDP]

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.

 

[TerryinOz]

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

 

[TerryinOz]

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

 

[NoelDP]

You now have a completely different set of problems

Here's the errors from the body of the CheckSUR report...

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.

 

[Layback Bear]

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?

 

[NoelDP]

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

 

[TerryinOz]

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?

Avast is the paid for Internet Security which includes AV and Firewall and Commodo is the free AV and Firewall. Both are set to prompt me if they want to sandbox, quarantine or do something I haven't already said is okay and I haven't been receiving any messages that there were issues when doing the Windows Updates. I also have CCleaner for keeping things tidy along with Auslogic Defreag and Revo uninstaller all of which are manually run, not autostarts, otherwise there are no other tools for tuning or optimising things and I don't recall using any of those listed in the past few weeks.

I did get a Red Screen of Death(just like a BSOD but the background was Red) during last week and on the next start up the Windows error checking kicked in and said it was fixing files and recovering orphans etc. but I didn't take much notice and did something else while it ran and things appeared okay afterwards until the messages in the SUR log. Whether they are related I am not sure, but that was the only thing out of the norm I can think of from last week.

Terry

 

[NoelDP]

Running with two AV's installed and active is a recipe for disaster
Running with two Firewalls installed .... the thought just gives me nightmares!
UNINSTALL one or the other.

 

[TerryinOz]

Hi, I have cleared up the problem with the corrupted files and now get a clean CheckSUR.log so I am happy to close this thread as solved. There are still a couple of fixes failing with errors as I try to install them, but they are different KB numbers and messages to what this thread started out as so I will see how I go and if get stuck again will open a new thread. Thank you for the help in solving this one. Terry

 

[NoelDP]

You're welcome - good luck!