[SOLVED] [Win7SP1 x64] monthy rollup update always failed (Error code is 8024200D)

DaddaRule

Contributor
Joined
Oct 16, 2017
Posts
22
Hello.
Like many other the update security files always fail. (been like this for probably half a year or more). Few days ago I got fed up with looking at that stupid flag and decided to try and fix it myself, as I don`t feel comfortable with asking strangers for a handout. But after 3 solid days and not getting any closer I am at a loss. I would really, really appreciate it if someone could take the time to help me, or point me in the right direction.

I will try to give points to my system and problem:
OS: Win7 64
problem: windows security update fail
I think the problem to are remnant of old Avast files looked in the winsxs folder.
Things I tried to do to remedy the problem:
chkdsk: clean
KB947821 - System Update Readiness Tool for Windows 7 : error message
Fix WU program
FixWin program
windowsupdateagent-7.6-x64.exe
replacing several different KBXXXX.msu files
taking ownership of winsxs folder and replacing avast files with error: could not take ownership over the broken files I wanted replaced.
turning off/on/restarting windows update
net stop wuauserv, etc.
deleting and re-installing avast (though I did not use any purge programs to clean avast. Only regular uninstall)

=================================
Checking System Update Readiness.
Binary Version 6.1.7601.22471
Package Version 26.0
2017-10-15 21:23

Checking Windows Servicing Packages

Checking Package Manifests and Catalogs

Checking Package Watchlist

Checking Component Watchlist

Checking Packages

Checking Component Store
(f) CSI C Mark Deployment Missing 0x00000000 c!avast.vc140.mfc_fcc99ee6193ebbca_14.0.24210.0_49391d6d8244622b x86_avast.vc140.mfc_fcc99ee6193ebbca_14.0.24210.0_none_a338d8ea2df29efb
(f) CSI C Mark Deployment Missing 0x00000000 c!policy.14.0.avast.vc140.crt_fcc99ee6193ebbca_14.0.24210.0_ef17e13d91c55d96 amd64_policy.14.0.avast.vc140.crt_fcc99ee6193ebbca_14.0.24210.0_none_499a1b14d5902dfc
(f) CSI C Mark Deployment Missing 0x00000000 c!policy.14.0.avast.vc140.crt_fcc99ee6193ebbca_14.0.24210.0_36c51814a641869c x86_policy.14.0.avast.vc140.crt_fcc99ee6193ebbca_14.0.24210.0_none_914751ebea0c5702
(f) CSI C Mark Deployment Missing 0x00000000 c!avast.vc140.crt_fcc99ee6193ebbca_14.0.24210.0_020285fe6d6e0580 amd64_avast.vc140.crt_fcc99ee6193ebbca_14.0.24210.0_none_56aba0211ca246c2
(f) CSI C Mark Deployment Missing 0x00000000 c!policy.14.0.avast.vc140.mfc_fcc99ee6193ebbca_14.0.24210.0_364e78aca69bba41 x86_policy.14.0.avast.vc140.mfc_fcc99ee6193ebbca_14.0.24210.0_none_962753dde6e08635
(f) CSI C Mark Deployment Missing 0x00000000 c!avast.vc140.crt_fcc99ee6193ebbca_14.0.24210.0_49afbcd581ea2e86 x86_avast.vc140.crt_fcc99ee6193ebbca_14.0.24210.0_none_9e58d6f8311e6fc8

Summary:
Seconds executed: 589
Found 6 errors
CSI C Mark Deployment Missing Total count: 6
 
Please do the following. Check for Windows Updates and attempt to install only one of the updates that you know will fail. When it fails, please let me know what the KB number of the update is and also please zip/attach your c:\windows\logs\cbs\cbs.log
 
Please do the following. Check for Windows Updates and attempt to install only one of the updates that you know will fail. When it fails, please let me know what the KB number of the update is and also please zip/attach your c:\windows\logs\cbs\cbs.log

sure :)

2017-10 Security Monthly Quality Rollup for Windows 7 for x64-based Systems (KB4041681)
Installation status: Failed
Error details: Code 8024200D

think this fileshare site should work: Uploadfiles.io - CBS.zip
 
you sir, are a gem. It looks like it works :D I really appreciate it. 30 hours of troubleshooting and the fix was just a simple uninstall of a KB package. Would you make a short text of what the problem was. I thought it was because of old avast files, but it was just a messy windows update file?
 
That is exactly correct! I've seen this a lot lately when Microsoft went to cumulative updates. If only one install scenario isn't accounted for the update may not be able to install. So getting rid of the cumulative update that is causing the issue will allow the newer one to install.

You are very welcome. Take care.
 
I just installed 2017-10 preview of montly quality KB4041686 and it went through flawlessly. Though, two smaller updates: microsoft game device xbox 360 reciever and Realtek - Network PCIe GBE Family Controller failed. I presume those are of unimportant and maybe failed because of old driver updates.
 
Though, two smaller updates: microsoft game device xbox 360 reciever and Realtek - Network PCIe GBE Family Controller failed. I presume those are of unimportant and maybe failed because of old driver updates.

We can look at these if you wish but I agree they are likely unimportant. Just let me know.
 
No thank you :) I think it is probably caused by old drivers. I will send you good karma and hope you have a prefect week :D Your help definitely deserve a donation to this site :) Thank you again. And I hope someone who have the same problem will stumble on this topic/post and get a quick fix.
 

Has Sysnative Forums helped you? Please consider donating to help us support the site!

Back
Top