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.
Microsoft considers anyone that uses sfc /scannow to be an "advanced user". <sigh>
I'm not sure if your sigh is a sign of frustration with Microsoft or not. ;o)
I'm not sure what the terms is for the likes of me - I can get around a PC but only by following instructions from an expert. But I'm sure I'm in the biggest segment of PC users and if I have a problem, I go to a forum to get advice. "Run sfc /scannow" is commonly given as the next step.
"All my point is here, for this particular fact pattern uninstall the update, don't run a fix to fix corruption when it's Microsoft that needs fixing, not your operating system."
But being a novice, rabbit or whatever I can't possible tell if it's Microsoft that needs fixing, not my operating system! But you make an excellent point. Thank you.
Microsoft considers anyone that uses sfc /scannow to be an "advanced user". <sigh>
The problem is that there's a lot attributed to this update because it's mainly a consumer based update (it's not on WSUS) no one is really getting to any good cause and effect in many of these reported issues. There's nothing in the code of this update to cause many of the reported issues (other than the misreporting of the corruption of course). I've seen networking problems attributed to this update when this patch doesn't touch the network stack.
When cases are not opened, no one gets to the root cause of the problem.
All my point is here, for this particular fact pattern uninstall the update, don't run a fix to fix corruption when it's Microsoft that needs fixing, not your operating system.
Hi Susan. You might be right in saying that KB3022345 doesn't actually corrupt any files, only that it produced an erroneous report of corruption, if I've got it right - I'm a layman but as a user. this is what happened to me:
My Compaq Presario CQ71 had been hanging up at shutdown and there had been occasions when I've had to start in Safe Mode and use System Restore to get back on track.
My first source for help was the HP Update Help Centre and I installed an updated BIOS but it happened again. I lost internet connection, Windows Security and System Restore. I sorted it using system restore via system recovery at the Esc phase of powering up. Running Got The Power's fix resolved my problem.
Using any search engine, input "KB3022345 problems" and there are hundreds (at least) of Joe Public, Microsoft customers logging the problems that they've had.
I do not want to interfere in an interesting debate between two experts but may I ask you one question - when these problems happened, I had a message saying that details of the problem would automatically be sent to Microsoft, (That's the usual procedure, isn't it?)
So will Microsoft tell us how many of these 'problem reports' from users have Microsoft received and what have they done about it?
I still remember the Microsoft up date that (temporarily, thank goodness) killed my XP tower. It was caused by some programmer forgetting that some PCs had amd processors and so the "for Pentium machines" update was disastrous.
You are totally correct in saying a major problem now is that ordinary users such as me have lost all faith in Microsoft. My XP is useless, my Win7 has a limited shelf life and WIn10 is being slowly forced on me - including removing the choice of control over updates. Sorry for the rant, and for going off-topic but just search the web for "KB3022345 problems" and you'll see what the 'man in the street' is going through.
For this particular fact pattern:
There is absolutely no corruption. What is "corrupted" here is Microsoft's handling of the issue and considering that only advanced users care about this and they will deal with the misreporting of corruption later because getting Windows 10 on a bunch of devices is more important.
Again, everyone reading this thread be aware I am not saying that for every instance the sfc /scannow tool reports bogus corruption, I am saying that in THIS instance the tool is misreporting.
