[SOLVED] [Win7SP1 x86] Unable to apply KB3185278 September 2016 update rollup

[protivakid]

Hello,

None of the recent monthly update rollups want to install but I have traced it back to the September 2016 update rollup for Windows 7 SP1 as being the first to not work. The August 2016 one went in without an issue. When I try to install them they do so and then ask to reboot. It's after that I see a failure to install updates, rolling back screen.

I found another thread and already completed some steps to save time. I ran SFCFix which reported the following: SURT total detected corruption count: 2

I then ran the SURT which generated the CheckSUR.log. It reported an issue with a particular file in the winsxs/Manifests directory. I was able to copy a replacement of that file from a working windows 7 install. After this I ran SURT again which said "No errors detected".

I then ran sfc /scannow which said "Windows Resource Protection found corrupt files but was unable to fix some of them." I copied the CBS log to my desktop and linked it below (was above the forum's attachment size limit). It's pretty large so I am not sure what all needs fixing from here. Any help is appreciated. Thanks!

CBS.txt

Hopefully you guys are not looking for "Cannot repair member file" entries because there seems to be about 40 of them...

 

[protivakid]

I was able to solve my own problem by again using the steps in this post here as a guide: https://www.sysnative.com/forums/wi...able-apply-kb3185278-after-hd-corruption.html

I looked over the attached CBS log in Notepad++ searching for the phrase "Hashes for file member". It showed up 68 times but saw most were duplicates and that only 9 files were actually bad. I copied those files from my Win 7 32-bit install on another laptop to an external drive. I then booted into Ubuntu and copied over the files so there would be no access issues. After that I ran sfc /scannow which said it was able to repair the files this time. I ran the command a second time and it said no corruption detected.

I then gave KB3185278 another try and it went in without an issue. Hope this helps someone else.