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 No 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 No comments

117 additional answers

Sort by: Oldest
  1. Anonymous
    2013-06-20T20:57:09+00:00

    anyone?

    Was this answer helpful?

    0 comments No comments
  2. Deleted

    This answer has been deleted due to a violation of our Code of Conduct. The answer was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.


    Comments have been turned off. Learn more

  3. Anonymous
    2013-06-21T01:23:37+00:00

    Are we suppose to restart the computer after running this command

    dism /online /cleanup-image /restorehealte

    Or can we run sfc /scannow right after without restarting?

    Was this answer helpful?

    0 comments No comments
  4. Anonymous
    2013-06-21T03:58:37+00:00

      

    Error: 87

    the online/cleanup-image/scanhealth option is unknown.

    You just forgot to type spaces...( at least 1 before each slash )

    dism    /online    /cleanup-image    /scanhealth

    Thank you! (gobonkers and Matthias)

    I followed their instructions. First i wrote this in the cmd prompt (in safe mode & Networking):

    *******************************************************************************************

    DISM.exe    /online    /cleanup-image    /scanhealth

    and the command window shows:

    Error: 3017

    The requestes operation failed. A system reboot is required to roll back changes made.

    *******************************************************************************************

    I rebooted the O.S. and i wrote this:

    *******************************************************************************************

    DISM.exe    /online    /cleanup-image    /restorehealth

    and the command window shows:

    Error: 3017

    The requestes operation failed. A system reboot is required to roll back changes made.

    ********************************************************************************************

    I rebooted the O.S. and i wrote this:

    ********************************************************************************************

    sfc /scannow

    and the command window shows:

    There is a system repair pending which requires reboot to complete. Restart windows and run sfc again.

    ********************************************************************************************

    I rebooted the O.S., i  can not fix the O.S.  problem.

    What could be the problem?

    Somebody Knows, how fix it?

    Was this answer helpful?

    0 comments No comments