[SOLVED] Can't Install Windows Update KB3099862 -> Code 800736b3

[spitfireCH]

Hi,

I don't really know what I am doing wrong or why my system files keep going corrupt. My system fails to install update KB3099862.

Running SFCFix tool reveals 28 SURT corruptions:

SFCFix version 2.4.5.0 by niemiro.
Start time: 2015-12-10 21:29:02.991
Microsoft Windows 7 Service Pack 1 - amd64
Not using a script file.




AutoAnalysis::
SUMMARY: Some corruptions could not be fixed automatically. Seek advice from helper or sysnative.com.
CBS & SFC total detected corruption count: 0
CBS & SFC total unimportant corruption count: 0
CBS & SFC total fixed corruption count: 0
SURT total detected corruption count: 28
SURT total unimportant corruption count: 0
SURT total fixed corruption count: 0
AutoAnalysis:: directive completed successfully.




Successfully processed all directives.
SFCFix version 2.4.5.0 by niemiro has completed.
Currently storing 52 datablocks.
Finish time: 2015-12-10 21:34:44.427
----------------------EOF-----------------------

I already run the SURT scan. It produced the attached log-files. Please let me know if I should still upload the entire CBS folder.

I am truly sorry, but I fear I will have to ask for your help again


Thank you so much!

 

[spitfireCH]

P.S. After a restart, CHKDSK fixed some errors, and low the log files already looks better - or at least different (see attachment).

 

[spitfireCH]

All right, I kind of managed to fix this by checking CheckSUR.log for corrupt files and replacing them with dlls from a backup (following these instructions), followed by running checkdsk and a restart.

Now, CheckSUR.log is free of errors and I managed to install the security update.

However, CheckSUR.persist.log still shows many errors that could not be fixed. Are those going to be an issue?

 

[BrianDrab]

No those won't be an issue. The CheckSUR.persist.log contains information from older runs. The only one of concern is the CheckSUR.log. Good job!!

 

[spitfireCH]

No those won't be an issue. The CheckSUR.persist.log contains information from older runs. The only one of concern is the CheckSUR.log. Good job!!

Great, that's good to know, thank you very much!