This isn't the update causing my problem.
The problem for many people is when Windows reports that the updates have been installed correctly they may not be aware that they have system file errors. Eventually when problems occur they will have difficulty knowing what the cause was.
Last edited by mjf; 15 Jan 2016 at 00:48. Reason: Update
I had a bunch of Office 2007 security updates that produced no problems so the issue is with at least one of these:
Last edited by mjf; 15 Jan 2016 at 00:52.
SFC Scan is working fine after installing the Malicious Software removal tool update, and while I didn't get the IE 9 update since I use IE 11, I got a very similar update for IE 11 and SFC scan is working after I installed that update as well.
As for the other security updates, installing them one by one and running SFC after each one is installed, I just can't get myself to do it because it doesn't seem to be worth the effort. If it was something big like a new service pack or something it would be worth it, but its just a bunch of vulnerability fixes for windows services I disabled eons ago.
FWIW I installed all 10 of this week's WUs (security only, not the W10 one), which included the MSRT scan, plus one for Silverlight and one for IE11 (twelve total) and my SFC is not happy. It LOOKED to be happy but then a third scan said "corrupt" again:
I suppose I should look at the logs and/or keep running sfc /scannow ad nauseum but given all the trouble we've had using sfc this year I'm not sure it's worth the effort.Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Users\Max>sfc /scannow
Beginning system scan. This process will take some time.
Beginning verification phase of system scan.
Verification 100% complete.
Windows Resource Protection found corrupt files but was unable to fix some of them.
Details are included in the CBS.Log windir\Logs\CBS\CBS.log. For example
C:\Windows\Logs\CBS\CBS.log
C:\Users\Max>sfc /scannow
Beginning system scan. This process will take some time.
Beginning verification phase of system scan.
Verification 100% complete.
Windows Resource Protection found corrupt files and successfully repaired
them. Details are included in the CBS.Log windir\Logs\CBS\CBS.log. For
example C:\Windows\Logs\CBS\CBS.log
C:\Users\Max>sfc /scannow
Beginning system scan. This process will take some time.
Beginning verification phase of system scan.
Verification 100% complete.
Windows Resource Protection found corrupt files but was unable to fix some of them.
Details are included in the CBS.Log windir\Logs\CBS\CBS.log. For example
C:\Windows\Logs\CBS\CBS.log
EDIT: I checked these updates w/another PC, doing a sfc before and then after, and no problems were found so the above is an issue with this particular PC and not with the updates--SORRY! The command BTW to check the log is:
findstr /c:"[SR]" %windir%\Logs\CBS\CBS.log >"%userprofile%\Desktop\sfcdetails.txt"
Last edited by maxseven; 16 Jan 2016 at 08:55.
If SFC is buggy then throw your hands up! If not then I'm not happy accepting corrupt system files. Generally I have no problems with security updates but now and again I do when I run sfc.
This forum has technically aware users but many people wouldn't know what a system file scan was and why should they need to know.
fyi on "important updates" always read the caveats. Some have the "unable to uninstall", those you wait on and then you usually avoid crashing your build...
Hell, I was a computer tech for over a decade and I don't think any of my co-workers were even aware it existed, and if a bunch of techs weren't familiar with it, I imagine a lot of mainstream PC owners aren't aware of it. In short, Microsoft can pretty much get away with breaking it since chances are when they do, they're not going to be lynched by the majority.
Now if they released an update that made it impossible to update Twitter or Facebook, they'd have people with pitchforks and guns outside of whatever offices they still have in the US.
Or most people would be like "eh." and just hop on their phone. I heard smartphone sales have put a huge dent in PC sales.. and that most use their smartphones to access social media sites and not pc's.
Kind of sad...
Well I just updated another W7HP x64 computer with the 12 most recent and I did not get the sfc /scannow errors as I reported a few posts ago. I checked the PC both before the updates, and then again after, no problems.
So I apologize for the misdirection. BTW anyone having the problem of "integrity violations" can find the source of them by using this command, which parses the CBS.log for you:
findstr /c:"[SR]" %windir%\Logs\CBS\CBS.log >"%userprofile%\Desktop\sfcdetails.txt"
You didn't misdirect anyone since I re-installed the updates again and SFC got bored again.
It seems to be this file.. but the thing is, even though SFC says it couldn't fix it, SFCdetails says it did..
aeinv.mof
It repairs it a total of 5 times during one SFC scan, so maybe that's why the scan says it couldn't fix some files since after repairing it 5 times, its still broken. I searched around to find out what aeinv.mof was and this is what I found..
What is Aeinv.mof and How to Fix It? Virus or Safe?
Its a Windows 10 file.. big surprise.
Quote
