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
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

64 additional answers

Sort by: Newest
Most helpful Newest Oldest
  1. Anonymous
    2015-06-15T01:59:03+00:00

    To be clear if any OTHER file is flagged as corrupted, the poster probably does have corruption.  But if these two specific files are flagged as corrupted, please take no other action other than to uninstall these updates.  Taking actions to 'fix' corruption when these two files are not corrupted but just have a bug in them that makes the tool report corruption, may cause more problems for the operating system.

    Was this answer helpful?

    0 comments
  2. Anonymous
    2015-06-15T01:56:22+00:00

    Again we're going to disagree over the concept of corruption.  Both updates make the sfc /scannow to report that the pieces that were installed are corrupted.  They really aren't.  but obviously it makes it really hard to now rely on this process.  Clearly they docemented this in both KB articles and one replaces the other, so it's pretty clear that if you ran sfc /scannow those two files are going to flag themselves as corrupted when they really are not.

    Bottom line both clearly state:

    https://support.microsoft.com/en-us/kb/3068708?wa=wsignin1.0

    This update contains the following files that are occasionally updated by the Diagnostic Tracking Service:

    • telemetry.ASM-WindowsDefault.json
    • utc.app.json

    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 that is running this update, and this issue will be fixed in a later service update.

    https://support.microsoft.com/en-us/kb/3022345 This update contains the following files that are occasionally updated by the Diagnostic Tracking Service:

    • telemetry.ASM-WindowsDefault.json
    • utc.app.json

    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
  3. Anonymous
    2015-06-14T18:54:04+00:00

    Herman

    Thanks for the feedback. The situation varies from one computer to another. You no doubt will see different results between Windows 7 and Windows 8. Most of the result I see are Windows 7 computers.

    Was this answer helpful?

    0 comments
  4. Anonymous
    2015-06-14T18:31:16+00:00

    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