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-06-03T17:37:37+00:00

    wanted to post that today 6/1/15, an optional update was provided that fixed the erroneous errors reported by SFC.  All is well on my end now.

    Art, what is the KB # that fixed this ? ....I'm on W7.

    I assume the old KB3022345 is gone ? ......I "hid" it.

    Was this answer helpful?

    0 comments No comments
  2. Anonymous
    2015-06-03T14:31:59+00:00

    I was saddened to learn that Microsoft is taking the ability to control Windows Updates, that Windows Home users currently have the ability to do, and instead are going to push these updates in Windows 10 to the Home user whether they want it or not.

    I have always been used to trying to fix my problems myself before asking for help.

    Was this answer helpful?

    0 comments No comments
  3. Anonymous
    2015-06-03T12:49:09+00:00

    what's broken is Microsoft's process.

    Amen to that.........seems every MS update for past six+ months has some update that causes minor to major issues.  Seems Microsoft is not truly testing these things out extensively. Because of this "my" process is when the updates come out to scan the Forum's for other folks feedback on installs........I find myself waiting 3+ months to install.  Thus, Microsoft's attempts to be quick are now having people wait.

    Any news on a fix from Microsoft ?

    Was this answer helpful?

    0 comments No comments
  4. Anonymous
    2015-06-03T03:30:23+00:00

    Hi Gerry-

    I got to this thread from another forum and wanted to post that today 6/1/15, an optional update was provided that fixed the erroneous errors reported by SFC.  All is well on my end now.  BTW I got a real kick watching the 'sparring' between you and Susan. Two bright minds CAN civilly disagree.  A similar situation occurred for me on the Windows 7 Forum with a so-called "Guru" that was dishing out one-liner off-topic hokum ... then he got snotty with me.  I returned said sentiment right back to him and BAM I was booted for life for being "rude".  What a joke.

    • Art

    Was this answer helpful?

    0 comments No comments