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: Oldest
Most helpful Newest Oldest
  1. Anonymous
    2013-07-24T19:06:02+00:00

    are you experiencing problems?

    Was this answer helpful?

    0 comments
  2. Anonymous
    2013-07-24T19:06:09+00:00

    You can't uninstall it.

    Because it's a servicing stack it's uninstallable.

    Was this answer helpful?

    0 comments
  3. Anonymous
    2013-07-25T02:48:35+00:00

    Referring to my original discussion, ..... yes!

    I was receiving many Event Logs regarding logging problems.  These cleared after the sfc/dism repairs.  They're back today..

    I had issues running sfc.  Had to run dism to clear them.

    As of today, sfc is showing no errors but the logging problems are back which are what originally referred me to this thread.

    Was this answer helpful?

    0 comments
  4. Anonymous
    2013-07-25T02:51:39+00:00

    That's a partial answer at best.

    I always have options whether it's an uninstall, a restore or a reinstall.

    The only question is when the hole gets too deep and I have to put down the shovel and quit digging.

    So, to be very clear, is this "update" going to continue to cause me problems?  Do I need to find some method to get rid of it, eg put down the shovel and quit digging a deeper hole???

    Thanks...

    Was this answer helpful?

    0 comments