This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(128, 8%, 22%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EA%3C/text%3E%3C/svg%3E)
After installation of optional update KB3022345, executing sfc.exe /scannow throws the following result message (see attached screenshot):
I can reproduce this on three different machines, all Win 8.1, all fully patched, they are a mix of 64 and 32 bit systems.
The error disappears on all my machines when I uninstall the KB3022345 update.
Moderators please feel free to move this message to an other board in case I posted this in the wrong one.
Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.
Thank you for responding.
I appreciate you are trying to help me, but as I said in my opening post I 'fixed' this by uninstalling an optional update.
As this occurred on three different machines and could be corrected on all machines by uninstalling this update my guess would be there is something wrong with the update.
wanted to post that today 6/1/15, an optional update was provided that fixed the erroneous errors reported by SFC. All is well on my end now.
Art, what is the KB # that fixed this ? ....I'm on W7.
I assume the old KB3022345 is gone ? ......I "hid" it.
I am on Win7 as well. The KB number is
KB3068708
For what it's worth, I've just come out of an incredibly bad few days thanks to KB3022345 and it was Go The Power via Bleeping Computer who fixed my Win7 laptop.
A few days ago I read that Microsoft would not accept that PCs had been corrupted by the KB but the article said that Microsoft were about to release the 5th or 6th version of it but under an entirely different name - KB3068708. The advice given was not to install it, to wait a few days then visit forums to see if there were any threads on the subject.
Unfortunately, it was installed*** last night along with another 8 so I'm just waiting to find out if the sfc /scannow CBS had shown any problems.
*** After a similar major update problem many months ago I changed my settings so that updates would not be automatically installed - well I thought that I had. But I hadn't - I should have chosen "check for updates but let me choose whether to download and install them".
Instead I'd selected "**download updates but let me choose whether to install them"**and the result when I shut down last night was the message "downloading 1 of 9 updates - do not switch off" - I couldn't do anything to stop the updates being installed and I'm horrified that the option I'd chosen gave me no choice at all - there was no shield icon "updates are available" - they just installed presumably as part of the powering down process.
To be clear this update doesn't cause corruption. It only erroneously reports corruption. So if anyone does any action post install to make it not report corruption, I am concerned about what this action is doing to your system. If you don't want this update please merely uninstall it, don't take actions to "fix" because the "fix" has to come from Microsoft.
When you selected download updates but let me choose, you end up in a situation where the patches download in the background. When you go to shut down there's a tiny little icon indicating that updates are ready to be installed. If you haven't adjusted the registry to disable installing updates on shut down you could "catch" these updates. There's an indicator, it's just so small that it's often overlooked.
Do that to ensure it won't catch you again.
Susan
Windows File Protection (WFP), a sub-system included in Microsoft Windows operating systems of the Windows 2000 and Windows XP era, aims to prevent programs from replacing critical Windows system files. Protecting core system files mitigates problems such as DLL hell with programs and the operating system. Windows 2000, Windows XP and Windows Server 2003 include WFP under the name of Windows File Protection; Windows Me includes it as System File Protection.
Source: http://en.wikipedia.org/wiki/Windows_File_Protection
What Microsoft say in the Knowledge Base Article you keep quoting, totally undermines the basis of this core element of Windows. Users rely on System File Checker to correct things that go wrong. Using the Article to say that the content of System File Checker reports does not matter simply undermines their credibility.
