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.
Gerry I can't fix Microsoft.
This particular patch clearly causes systems to report that they have corruption when they clearly do not.
I am deeply concerned that people are running additional tools to fix something that isn't corrupted in the first place.
The ONLY way someone should "fix" their system if they don't want to ignore the bogus reporting of corrupted files is to uninstall the patch, not run some utility.
Susan
Gerry I can't fix Microsoft.
True but you are the principal person in these forums providing users with explanations like that isn't corrupted in the first place. I do not understand why you continue to offer this as an explanation. No one else is taking the same position. You undermine the importance of system file checker to correct file corruption.
Because it's not corruption.
These systems are not corrupted after the install of KB3022345.
Microsoft has clearly stated that the diagnostic patch has two files that throw off bogus errors. I have seen this before when a spelling update was installed and did the same thing. The files installed by the patch are causing a misreporting of the corruption there is no actual corruption.
Anyone who states that after the install of the KB in the subject line that they are now suddenly getting reports of corruption, the operating system is NOT corrupted. It's THE PATCH or specifically two files in THE PATCH that cause the misreporting.
Read in the KB again what it says:
The two files are marked as static files in the update. When an advanced user runs the System File Checker Tool (sfc.exe), the files are unintentionally flagged as corrupted. There is no impact or actual corruption on a device running this update, and a later service update will resolve this issue.
I am the principal person in the forums trying to tell people who have installed this patch that if they want to have reporting of no corruption merely uninstall the patch, don't take any other action such as using another tool to "fix the corruption" when there isn't any corruption in the first place.
See what I'm saying here? The patch has two files that are misreporting. The actual operating system has no corruption. If you don't want to ignore the report (and I totally understand that) then take the right action of uninstalling the offending update, don't hack up the operating system and "fix" corruption when there isn't any real corruption in the first place.
Susan
We must agree to disagree. There is no impact or actual corruption on a device running this update, and a later service update will resolve this issue is misleading advice, which in a number of cases not true. Remove the update and problems stop. It is as simple as that.
