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.
I can confirm that uninstalling both updates fixes the SFC false positive problem and that reinstalling either of them causes the problem to manifest itself. Win 8.1 pro.
Susan
Are you aware that KB3068708 corrupts in the same way as KB3022345?
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.
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.
Hear...Here! It is patently absurd for MS to send an update that reports a false positive in one of their core services. What I want to know is WHY Microsoft takes the following position:
"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."
MS needs to fix the updates so that they do not (unintentionally) flag the files as corrupted. Even If Microsoft's position is that "only advanced users" use the SFC tool, then they need to explain to Technology professionals WHY these files are flagged as corrupted. Telling us that a core service is giving us a false positive does not answer WHY this is the case.
