KB3022345 causes error in sfc.exe

Anonymous
2015-05-01T08:04:57+00:00

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.

Windows for home | Previous Windows versions | Windows update

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.

0 comments No comments
Answer accepted by question author
Anonymous
2015-05-01T11:49:47+00:00

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.

Was this answer helpful?

0 comments No comments

64 additional answers

Sort by: Most helpful
  1. Anonymous
    2015-05-23T14:36:49+00:00

    I lurk and search around in many forums.  Just because I don't post in a venue doesn't mean I'm not there poking around to see impact.  I also am on the patchmanagement.org list where the WGA problem is not reported, I'm not seeing it widely in twitter , nor in the TechNet forums, nor in searching around the non Microsoft properties, nor have had any reports in my SMB listserves. 

    I received assurances that this KB won't kick WGA problems.  I truly think that it's a case of coincidence and the root cause is something else and not this patch for this specific issue.

    I have I installed in several locations on various systems, I have had no WGA issues.

    I stand by my comment - I am not seeing the WGA issue widely reported.  The SFC/scannow issues WILL be widely reported because it (unfortunately) an expected side effect of the patch.  But there is no actual corruption.

    If someone with an active WGA issue and has installed this patch would like to work with me to open a support case to get to the root cause, I would love to help out in the investigation.

    Was this answer helpful?

    0 comments No comments
  2. Anonymous
    2015-05-23T08:38:23+00:00

    Susan

    I'm not seeing this side effect widely reported at all.

    Perhaps you do not visit the right places or read the full threads.

    From my observations not all systems are affected in the same way or to the same extent. There are also a number of other problems currently being included in sfcdetail reports, which have nothing to do with the offending update. The problems caused by KB 3022345 surface not only in the Windows Update forums. Where there are to be found depends on which symptom the user notices.  How often do you visit Repair and Recovery or Install, Upgrade and Activate?

    Was this answer helpful?

    0 comments No comments
  3. Anonymous
    2015-05-23T08:07:06+00:00

    I uninstalled the update yesterday... This long-term aggravating problem with healthy files being reported as corrupted disappearedafter the reboot. The KB3022345 update is not hidden by them. It re-proposed itself for installation today. But if you right-click it, you can choose to hide it for yourself, so that it doesn't turn up in the list anymore. And of course you always have the option of viewing your hidden updates. If your system is otherwise healthy and you're having this problem, this is an easy and reversible fix. If you have uninstalled it in control panel, you can always reinstall it the next day. I prefer to hide it forever and good riddance. Thought maybe feedback from someone who's tried it would be helpful to someone else. All my best!

    Was this answer helpful?

    0 comments No comments
  4. Anonymous
    2015-05-23T07:46:13+00:00

    As I've commented in a related thread:

    Like to say that I have been struggling with this issue in WIN 8.1 for a couple weeks after cloning my hdd. The DISM /Online /CleanupImage /RestoreHealth command restored the files beautifully. But /scannow kept bringing up "hash mismatch" and "Could not reproject corrupted file [...] source file in store is also corrupted" errors, even though DISM /Online /CleanupImage /ScanHealth kept saying they were fine. These operations take masses of time. I am so grateful to the "uninstall KB3022345 update" suggestion. I uninstalled it in Control Panel - Programs and Features - Installed Updates, and after the obligatory reboot SFC /scannow gave the component store a clean bill of health. So GRATEFUL to have come across this fix. In my case, well worth the try. Thanks Herman P!

    Was this answer helpful?

    0 comments No comments