[SOLVED] Also troubles with KB4505903

Menno555

New member
Joined
Aug 6, 2019
Posts
2
Short intro: name is Menno, I am from the Netherlands.
I to have troubles with KB4505903. It's an exact copy of WU error 0x800f0982, but SFCFix found no corruptions ... but since I am a new user here, I can not react in that topic.
There are numerous mentions on KB4505903 on the net. From fails like this to much worse. For me it gives Error 0x800f0982
But like usual I am intrigued on why an update fails :)

I did all the steps mentioned in the Instructions on the start page of this forum. All is cleared, no errors what so ever, all steps done. My CBS is bigger then 7 Mb (just over 8 Mb), so it is stored here: CBS.zip

Also did run SFCFix and that also came out without errors:

SFCFix version 3.0.2.1 by niemiro.
Start time: 2019-08-06 15:08:16.195
Microsoft Windows 10 Build 18362 - amd64
Not using a script file.
AutoAnalysis::
SUMMARY: No corruptions were detected.
AutoAnalysis:: directive completed successfully.
Successfully processed all directives.
SFCFix version 3.0.2.1 by niemiro has completed.
Currently storing 0 datablocks.
Finish time: 2019-08-06 15:08:39.463
----------------------EOF-----------------------

Also did steps found elsewhere like clearing of C:\Windows\SoftwareDistribution, uninstalled virusscanner (Kaspersky Internet Security 2019), and so on.
Maybe worth mentioning: found multiple mentions that within a few hours after the release of KB4505903 it was removed. Only to be re-released a short while later. No reason for it was given though.
 
For those interested: since the OP of [SOLVED] - WU error 0x800f0982, but SFCFix found no corruptions had 100% identical problems and tried solutions as I have and did, I followed that thread.
I also did follow the steps that were given as solution. Did check all the results like SearchReg.txt that were given by the OP and my results (used a text comparison tool) and they were 100% identical. Checked the other files: 100% identical.
So, I decided to use the fixlist.txt (the warning on top was noted by me, used it at my own risk) and for me now also the update worked fine. One difference: creation of the restore point gave no error.
Having said that: I took the risk of using that solution. By no means I encourage others with the same problem to use it also. That it worked for me also is no guarantee that it works for others too.
 
Back
Top