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: Oldest
  1. Anonymous
    2015-06-15T02:01:10+00:00

    I ran DISM /Online /Cleanup-Image /RestoreHealth with both updates and I had no joy.  The only thing that cleared up the SFC false positives for me was uninstalling KB3022345 and  KB3068708.  The CBS log file was a big help, because it names the actual update that causes the problem (in Windows 8.1 Pro)

    Susan

    Are you aware that KB3068708 corrupts in the same way as KB3022345?

    Hi Gerry,

    I am not Susan, but let me share my experience here.

    I have KB3068708 installed on three machines, while KB3022345 is not installed anymore (it was probably withdrawn by MS?).

    I ran sfc /scannow on all three machines, just to see what happens.

    On my laptop (Win 8.1 x64) sfc /scannow did not report errors.

    On both my tablet (Win 8.1 x32) and desktop PC (Win 8.1 x64) sfc /scannow reported the same error as it did when KB3022345 was installed (see my opening post of this topic).

    I ran DISM /Online /Cleanup-Image /RestoreHealth which reported a successful repair on both machines.

    Following that sfc /scannow executes without reporting an error on both machines.

    I must admit I did not try the DISM route when I stumbled over the KB3022345 issue, at that time I just uninstalled the update.

    Hope this helps,

    Was this answer helpful?

    0 comments No comments
  2. Anonymous
    2015-06-17T02:01:50+00:00

    Hi,

    KB 3022345 has been updated with the information about SFC unintentionally flagged specific files as corrupted.

    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.

    Was this answer helpful?

    0 comments No comments
  3. Anonymous
    2015-06-17T08:53:45+00:00

    Rohit

    When an advanced user runs the System File Checker Tool (sfc.exe), the files are unintentionally flagged as corrupted.

    If this is true why doesn't Microsoft stop the unintentional flagging of files as corrupted. It would be a much simpler solution that all their efforts to date to explain and justify this disastrous update.

    Was this answer helpful?

    0 comments No comments
  4. Anonymous
    2015-07-05T05:46:37+00:00

    Yep, (like Kenmdavisjr), on my Win 8.1, KB3068708 had to be uninstalled to get...

    PS C:\Windows\system32> sfc /scannow

    Beginning system scan. This process will take some time.

    Beginning verification phase of system scan.

    Verification 100% complete.

    Windows Resource Protection did not find any integrity violations.

    PS C:\Windows\system32>

    Uninstalling KB3022345 alone didn't cure me. Afterwards, this one is no longer offered, but KB3068708 is - & it's "important" now - no longer "optional". I'll wait till it gets to "critical" before I take again. I don't like the sound of "telemetry" & it was big enough to put up progress windows during the uninstall & required a reboot.

    Was this answer helpful?

    0 comments No comments