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: Newest
  1. Anonymous
    2013-06-21T16:09:04+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?

    You should be able to run sfc /scannow without having to restart.

    Was this answer helpful?

    0 comments No comments
  2. Anonymous
    2013-06-21T16:07:33+00:00

    dism /scanhealth will only scan for issues (similar to sfc /verifyonly) and will not try to fix them. You should run dism /restorehealth to fix the issues. If dism /scanhealth hasn't been run first, dism /restorehealth will scan for issues before fixing them.

    For anyone who still experiences sfc /scannow reporting corruption after you've run dism /restorehealth, could you please share your CBS log files (all files from C:\Windows\logs\CBS, in addition to CBS.log) with us?

    Was this answer helpful?

    0 comments No comments
  3. Anonymous
    2013-06-21T15:44:49+00:00

    This is my first Acer-anything. Slow processor, but 18 hour battery life and hybrid

    operation is tops and fun.

    So could it be the Acer OEM version of Windows8?

    Also, do not install optional updates, only the ones denominated as "important" in an

    attempt to keep Windows OS8 footprint small on 32 GB drive.  Have 32GB microSD

    and keep C: pared down as much as possible, but already about 20GB occupied even

    with all storage on D drive.

    None of those optional updates relate to KB2821895, do they, if anyone knows?

    Thanks.

    Was this answer helpful?

    0 comments No comments
  4. Anonymous
    2013-06-21T15:29:47+00:00

    fwiw

    I read through a lot of log details after the sScanHealth and it has some messages that say something to the effect  ... errors  found, on some lines and notes, will repair if askedr.     It then returned the message like all is OK component store.     Then when I follow up and run the RestoreHealth it always says the store was repaired.   

    RestoreHealth apparently looks at the log files or registry items that Scanhealth makes - sometimes RestoreHealth is only a 2 minute scan.    Sometimes it takes 15 minutes which is about same as ScanHealth time.

    Sorry DISM doesn't fix everybody's problems.  Hope that gets worked out soon.

          One site I visited .. everybody was running the DISM commands right after they installed the last batch of windows updates .. and it was taking 45 minutes up to 4 hours was mentioned by one, for it to complete, and ending with the reduced hard drive footprint.  So it apparently triggers one of the other updates.   The members there I saw had no mention of SFC errors..

    Was this answer helpful?

    0 comments No comments