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.
Susan
You may find it hard selling your message to many users who have felt the impact of this update.
If KB 3022345 was uninstalled the corrupted files reported by system file checker were reversed and the reports that the copy of Windows 7 was not genuine ceased. Further the Windows Update service reverted to normal service. Your explanation makes no reference to the Not Genuine messages or the inability to update.
Can you show me those threads as I'm not seeing those with WGA/update problems as I'll take them back to the product group.
As far as uninstalling making the corrupted files go away well of course it will as this patch adds those two files that the sfc/scannow doesn't handle correctly.
Install the patch and you have files that ARE NOT corrupted but the sfc tool can't scan properly.
Uninstall the patch and you've removed the files in question.
EVERY DAMN TIME (yes I'm swearing) a stupid patch has introduced a reported unrepairable corruption it always comes down to the cart in front of the horse at Microsoft and they haven't updated the rest of the parts .
But make no mistake no system corruption has been introduced so please everyone don't use any tool to fix anything because the issue isn't your machine, what's broken is Microsoft's process.
Susan
Very hard to tell without reinstalling the update and given that they've hid it/probably are not willing to do so now. I'm not seeing this side effect widely reported at all.
