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: Newest
Most helpful Newest Oldest
  1. Anonymous
    2013-06-13T01:21:54+00:00

    I can confirm this.  The instal of KB2821895 appeared to complete OK.  The problem as already stated is that running sfc /scannow produces an error message that some files could not be fixed.  A reboot is required to try and fix the files.

    Ran the reboot and sfc again and got the same error message.  The CBS log was filled to the brim with corrupted files that can't be fixed.  Running sfc /scannow will always produce the same error message and the same entries in CBS.log.

    When sfc reaches 100% there is a wait on my system about 10-15minutes.  During this time my CPU is around 30% with spikes up to 50%.  This is on a 3770k Quad Core.

    I came across a site in German where folks were having the same problem.  Windows 7 users didn't have this problem.  Seems it's a Windows 8 problem.

    It's possible the patch itself is working fine although I don't know how to test it.  Having sfc always giving errors is not a good thing even if they can be ignored.  All these messages will hide other problems.

    I have some CBS logs if you want to look at them.

    Was this answer helpful?

    0 comments