KB2821895 Windows 8 x64 Update 06.11.2013 problem

Anonymous
2013-06-13T00:47:34+00:00

After this update “sfc /scannow” gets stuck at 100% for about 6-7 minutes, and afterwards reports that there are corrupted files that it cannot fix and asks for reboot.

The situation with “sfc/scannow” repeats after restart. I checked it with three different machines. There are a lot of errors in CBS.log file.

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
2013-06-20T22:03:17+00:00

We’re aware of an issue impacting some Windows 8 customers trying to run the sfc /scannow command after installing KB2821895, where customers using the System File Checker receive an error message that there are corrupt files and that the system requires a restart to repair the files. 

To work around this issue:

·         Open an elevated command window

·         Run the command dism /online /cleanup-image /restorehealth, and wait for this command to complete.

·         Run the sfc /scannow command again until the command completes and reports that there is no corruption. If you still get an error that there is corruption, you should contact technical support for further assistance as your system may have actual corruption.

Was this answer helpful?

5 people found this answer helpful.
0 comments

117 additional answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Anonymous
    2013-06-15T00:48:16+00:00

    If you look here http://support.microsoft.com/kb/2821895 you will see this:

    The installer in the Unified Extensible Firmware Interface (UEFI) firmware does not work correctly.

    I run under UEFI.  Can this be the problem?

    Was this answer helpful?

    0 comments
  2. Anonymous
    2013-06-15T00:20:37+00:00

    MS, any definitive solution for this problem yet?. 

    Yes, my name says MSFT, but I'm not on the team that owns this...

    I have noticed this behavior too, but only because of this post.  The sfc error is known but the file is actually OK and I'm pretty sure spurious error can be ignored.  Are you having symptoms other than sfc not quite behaving as expected?  Is there a reason you ran sfc?  I'm not experiencing any other problems myself, so my "plan" is to ignore this on my machines.

    The high disk usage is because it's trying to compress files, which takes some time and thought, and should better prepare your machine for future updates.  After that one-time hit, there shouldn't be any performance issues.

    Was this answer helpful?

    0 comments
  3. Anonymous
    2013-06-14T18:44:43+00:00

    MS, any definitive solution for this problem yet?.

    Was this answer helpful?

    0 comments
  4. Anonymous
    2013-06-14T15:40:22+00:00

    Hey, I had that two hour clean disk session..  dropped c drive from 40gb to 30, then back up to 33 when it made that side by side reserve.tmp 3.0gb file             Don't delete that , it will go away at the right time.

    Here on technet:

    social.technet.microsoft.com/Forums/en-US/w8itproperf/thread/e800e7d8-0a57-4071-a9ea-c97a26b3eb0f

    http://social.technet.microsoft.com/Forums/en-US/w8itproperf/thread/e800e7d8-0a57-4071-a9ea-c97a26b3eb0f

    they state, that a new LZX compression algorithm is used by TiWorker.exe for the WinSxs folder after this update, which is quite CPU-intensive.

    Both sfc and Disk Cleanup use TiWorker. 

    So far ok, MS has announced to give Windows a smaller system disk footprint and also my Windows folder has dropped in size.

    But there's still the problem of the giant CBS error logs, and the need to fix this via DISM. ( and the question whether it's really fixed by that ).

    Was this answer helpful?

    0 comments