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-13T22:45:21+00:00

    I had that problem the fix for me was to run from Command Prompt (admin);

    DISM /Online /Cleanup-image /ScanhealthDISM /Online /Cleanup-Image /RestoreHealth

     

     

    Yep, this got rid of the SFC errors on my W8 x64 Pro VM.  However, is this the way to go after applying the update?  Is the patch fully functional after doing this?  I would hate for this procedure to have unintended consequences down the line.

    Think I'll wait for an official comment.

    Was this answer helpful?

    0 comments
  2. Anonymous
    2013-06-13T19:03:41+00:00

    I had that problem the fix for me was to run from Command Prompt (admin);

    DISM /Online /Cleanup-image /ScanhealthDISM /Online /Cleanup-Image /RestoreHealth

    Was this answer helpful?

    0 comments
  3. Anonymous
    2013-06-13T18:14:12+00:00

    Thanks for uploading your log. We're taking a look at it and we will reply back when we have more information to share.

    Was this answer helpful?

    0 comments
  4. Anonymous
    2013-06-13T11:09:17+00:00

    Hi there,

     

    We would like to look at CBS logs if your machine has run into this problem.

     

    Thank you,

    Damit

    You can find my CBS log here:  http://sdrv.ms/PUzDbC

    Was this answer helpful?

    0 comments