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-07-04T19:16:15+00:00

                   

    DISM /Online /Cleanup-Image /RestoreHealth

    I get ERROR: 21

    device not ready or sth

    heres the dism.log:

    http://sembia.org/dism.log

    You have a CD or DVD in the drawer while you ran the command ?

    Or an external CD/DVD connected ?

    Might unplug all external things you don't absolutely need and try the DISM commands again.  Like flash drives, cd drives,  or cell phone, or xbox, etc. & no cd or dvd in the drives.

    Was this answer helpful?

    0 comments
  2. Anonymous
    2013-07-04T13:24:55+00:00

    HELP... 

    my windows 8 randomly reboots and spending hours reading and searching for a fix, ms said i should run these commands. but when i type the following on cmd:

    DISM /Online /Cleanup-Image /RestoreHealth

    I get ERROR: 21

    device not ready or sth

    heres the dism.log:

    http://sembia.org/dism.log

    Was this answer helpful?

    0 comments
  3. Anonymous
    2013-06-26T13:32:59+00:00

    Okay, I did sfc /scannow and it said some files couldn't be repaired like 15 minutes after the verification was 100%. So I rebooted and I'm running the command. Microsoft needs to get their act together for these updates. Seriously, I'm tempted to go back to Windows 7.

     

    dism /online /cleanup-image /restorehealth

     

    How long should this take? Its been at 20.0% for a while and it just went to 40%.

     

    Microsoft needs to get their act together for these updates. Seriously, I'm tempted to go back to Windows 7.

    I'm sorry that you're having to go through this, CannedBullets, too, as a consumer of 

    MS Windows 8. I agree that this is extremely frustrating, especially when the apparent

    "experts" in this community appear to be snobbishly concluding that it's the consumer's

    fault that we are having trouble with Microsoft's Windows 8 updates. Wish they could see

    our records of carefully updating and virus checking our Windows 8 computers to

    prevent issues. IT's MS UNTESTED UPDATES THAT IS THE ISSUE would be my reply.

    I've now done sfc check and restore health check so many times I can't remember how

    long it takes when. But as I recall, sfc checker takes quite a bit of time (as in over a half

    hour) to repair the update's system damage, and resto (re health can take a while (something

    just a little shorter perhaps) to finish repairing files. I believe some of the early posters

    in this thread reported times of over an hour. Just let sfc file checker and restore health

    run until completed. Once started, I believe it is very unwise to stop either process.

    As a non-techie consumer, not sure just why. Perhaps the experts could weigh in on

    times required.

    Personally since system damage inflicted by 2821895 on June 15, I've spent three 8 hour

    days (at least) correcting and restoring my Windows 8 system. MS does need to be

    more careful with their update work (and perhaps OS design) - I agree. Long, cold

    day before I'll jump in on a new product again. And I've been with MS since 3.1 Almost

    pre-ordered SurfacePro. That's not going to happen.

    Was this answer helpful?

    0 comments
  4. Anonymous
    2013-06-26T06:14:42+00:00

    Okay, I did sfc /scannow and it said some files couldn't be repaired like 15 minutes after the verification was 100%. So I rebooted and I'm running the command. Microsoft needs to get their act together for these updates. Seriously, I'm tempted to go back to Windows 7.

    dism /online /cleanup-image /restorehealth

    How long should this take? Its been at 20.0% for a while and it just went to 40%.

    Microsoft needs to get their act together for these updates. Seriously, I'm tempted to go back to Windows 7.

    Was this answer helpful?

    0 comments