Last round of updates stuff up again

I've just installed the latest (security) important updates. SFC fails unable to correct corrupt files. SFC before updates and was fine. This has happened before and it was a MS KB stuff up. This is why I always make a system image before installing updates!!


Update:
Restored system image made the day before I installed the updates which all installed with "no problems". No system file corruption reported by sfc /scannow.

Did you figure out which KB caused the problem?

Layback Bear said:

Did you figure out which KB caused the problem?

No. Last time it took me a long time with trial and error plus multiple image restores to identify the one problem KB. I'm not going to do this but there may be a more efficient approach and the rogue KB will be identified.

Those who have installed the latest important security updates may like to do an sfc /scannow. From memory the last time the problem affected many but not all people.

This could be a buggy update or cynics could suspect that this is a mechanism to move users to Windows 10. There appears to be a lot of pressure to move Windows 7 (and 8.1) users to Windows 10. Well there is an EULA MS expect users to adhere to and users should expect the same commitment by MS to the EULA.

I installed all the Important Updates on two computers and as always did a sfc /scannow.
No problems were found on either computer.
One Home Premium and one Professional.

I see you use Norton and MSE. Did you have problems on the Norton and MSE computers?

The MSE is on a PC which is very seldomly connected to the internet. I have 2 PCs that are very much internet connected and they use Norton and MBAM (free version).

The last time I had this problem I was also using Norton and the KB problem eventually noted by many.
I suppose it could be an incompatibility issue between MS update and Norton. Like Norton or not a large number of people use it.

Deviancy said:

I'm looking at the list of updates now.

The bugged one may be KB3108664 since it was released before and it was a Windows 10 update, and various people are having issues with it today.

Not the problem for me at least.

mjf said:

Deviancy said:

I'm looking at the list of updates now.

The bugged one may be KB3108664 since it was released before and it was a Windows 10 update, and various people are having issues with it today.

Not the problem for me at least.

That's because I was wrong, one of the other updates borked SFC scan and I just don't have the patience to test them one by one, so I removed them all and I'm running SFC scan right now to see what happens.

For the record, I do not use Norton for my AV, I use Eset.