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 am so sorry Gerry but I don't see the thread you are referring to? Can you point me in the right thread?
I absolutely agree with the distrust of patches.
Susan
I have I installed in several locations on various systems, I have had no WGA issues.
The situation is the same here. There have been no issues with the KB3022345 update on my three computers, two being Windows 7 and one Windows 8.
It is obvious that your experience differs from mine. I have not said that connected WGA issues are widespread, only that some have arisen.
What is widespread is user mistrust of Microsoft being able to get some updates right because there have been too many failures to get updates right when they are first released. KB3022345 is currently seen as one such update that is not really needed. You need to build a convincing case to explain why the update is important. The latest Knowledge Base Article is not convincing.
You have had an offer in another thread to unhide. You could reply to the offer.
To Gerry Cornell and Susan Bradley. Not selling anything madam, sir. I first saw the KB3022345 update uninstall proposition yesterday on this post and the post “After latest optional update KB3022345 sfc /scannow gives corrupted files.” ...this after days and days poking around on tech sites and trying many solutions. I would have liked to have found more user feedback before trying it, but went for it anyway. I’ve reported that the uninstall worked for me, and that it is an easy and, importantly, reversible procedure well worth the ten minutes if (qualifying clause follows) … if DISM has been telling you your files are without integrity problems but SCF /scannow is telling you there are hash mismatch corruptions. Reporting back is the responsible way of participating in a forum. It’s presented as just one gal’s experience. Be happy to send logs if it’s useful... Recovery or Install, Upgrade and Activate are overkill if uninstalling an update fixes the issue. Really happy to have run into it. Thanks for the forum.
