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: Most helpful
Most helpful Newest Oldest
  1. Anonymous
    2015-05-22T17:54:02+00:00

    https://support2.microsoft.com/default.aspx?scid=kb;en-us;3022345

    KB3022345 does NOT cause file corruption.

    Summary

    This update enables the Diagnostics Tracking Service in Windows 8.1, Windows Server 2012 R2, Windows 7 Service Pack 1 (SP1), and Windows Server 2008 R2 SP1. This tracking service collects data about functional issues in Windows.

    This update contains the following two manifests 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 corruption on a device that is running this update, and this issue will be fixed in a later service update.

    Was this answer helpful?

    0 comments
  2. Anonymous
    2015-05-21T22:50:48+00:00

    http://answers.microsoft.com/en-us/windows/forum/windows8_1-windows_update/cant-uninstall-kb3022345-error-0x800f0922/7e285f60-72b7-4ba6-919a-e9ffa18d1aa5

    check my thread I have a solution to remove the update if you can't remove it and stop getting sfc errors related to it.

    also no critical windows files get corrupted, only the files related to the update cause sfc to fail.

    Was this answer helpful?

    0 comments
  3. Anonymous
    2015-05-17T14:12:13+00:00

    I two have had the same symptoms with this update and sfc, and tried lots of various ways to make it work, but the same telemetry errors appear in CBS.log.

    The only way out of it for now is to just uninstall it, and leave it alone, until MS issue a revised version.

    I also agree that it is an optional update, in lieu of upgrading to Windows 10. So for me, on a production system, I am going to hold out for now.

    Was this answer helpful?

    0 comments
  4. Anonymous
    2015-05-06T08:37:27+00:00

    Windows 7 (SP1)

    I decided to go ahead and install this update. The install went well.

    I came back to the computer after the computer was turned off for several hours and this is when I very briefly saw a STOP screen and finally a selection to either do a Startup Repair or Startup Normally. 

    I chose Startup Repair. During this process it ask me whether I wanted to restore the system (back to the latest Restore Point) and I said yes. 

    So far everything seems to be working back to normal again.

    Was this answer helpful?

    0 comments