SFC detects corrupted files again after KB4041686

In my previous thread, I reported SFC /SCANNOW corrupted files after installing KB4042076 and KB4041686. I resolved the issue by effectively removing these optional Windows Updates. However, after reinstalling them one at a time, and performing a sfc /scannow after each, the problem started again after KB4041686 was installed. Google search for KB4041686 reveals that this is a problem update that apparently causes sfc /scannow to find resource violations.

Is anyone else having System File Checker problems after installing optional Windows Update KB4041686?

Big problems with Win7 Preview of Monthly Rollup
KB4041686

Posted on October 18th, 2017 at 07:41

I just saw a heads-up from @abbodi86 about the Monthly Rollup
Preview for Win7 that was released yesterday. It’s KB 4041686, the 2017-10 Preview of Monthly
Rollup.
As you know, I strongly recommend against installing Previews — they’re
“previews” precisely because they aren’t ready for prime time.

Here’s the problem.

After installing KB 4041686, a SFC (System File Check) scan will report and
fix an error in \system32\drivers\en-US\usbhub.sys.mui — even though there is no
error.

This is precisely the problem @abbodi86 reported to Microsoft after
installing the old KB 3125574, which is the “convenience
rollup” I call “Win7 SP 2.”

The bug was fixed in KB 3181988, but it’s back again.

If you install KB 4041686, you’ll trigger a bogus SFC error even if you have
KB 3125574 installed.

Is anybody at Microsoft listening?

After all the spywares and problems with updates, I now have WU on services to manual and on WU to never check. I now only install Security ONLY updates.

Same issue here. I have been sitting on the fence regarding a possible uninstall or a system restore. Im glad Im not the only one facing this issue so thanks for posting. I have never had a sfc failure of any kind.I have had all sorts of issues regarding PC corruption or hard drive failures which is why I periodically run sfc amd other utillities but thats another story.

Anyways I was confused because when in the comand box interface and you run it (sfc/scannow), it says it cant fix but if you run again it fixes it. Run it again and your right back to square 1 again. Whats even weirder is the log always says it fixes it.

I went ahead and installed the windows update readiness tool thinking it would do something but it didn't work. I also saw like you did that this was an issue with a previous update as well.

I just dont know at this point what to do. Are you going to uninstall perminately or are you goung to keep and hope for an update to fix? I dont want this file to damage so I guess Im looking for recomenations at this point.

The only fix is a System Restore to before the problem optional update, KB4041686, was installed. Then, don't install this problem update. To increase the odds of a successful System Restore, use the most current restore point prior to the KB4041686 install.

This update was the 2017-10 Preview of Monthly Quality Rollup for Windows 7 for x64-based Systems. So, it appears that this was Microsoft's live test. Hopefully, they will have the bugs worked out by the time of the November monthly updates. It remains to be seen if the November monthly updates will resolve all the issues with this problem update. Regards