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-06-18T13:44:59+00:00

    I can identify with this taking hours and hours of repair work on the part of Windows 8

    owners. sfc did not fix the corruption on my tablet. DISM ... Restore Health was unable to

    fix it after I applied 2821895.

    I repeat: I have sfc failure log saved as text file. I also have DISM text file showing much

    unrepairable corruption that was not fixed after application.

    If anyone at Microsoft is listening, can furnish these to help MS get a clue!!! Would be

    delighted to see Microsoft that concerned about individual consumers.  Still working on

    getting my Acer tablet re-set after disaster that occurred on Saturday and was system

    recovered on Sunday, and this is Tuesday.

    Was this answer helpful?

    0 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-17T18:55:13+00:00

    Am having similar problems others described on Iconia W510 hybrid tablet purchased Nov 2012 from MS Store.  No big techie but ran sfc /scannow and saved sfc log. Then saw post on Dism restore health on EightForums but that failed. Kept CBS log which showed corrupt data. Need smaller Win8 footprint on my 32GB system even though allows micro SD cards. So finally ran complete system disk restore using Acer disks reloaded and reupdated except for 1895 KB. Ran sfc again and no integrity violations. Now even though have hidden KB... 1895 on update history, MS keeps offering it over and over again. Also my update history says I never installed any updates. I personally won't be doing any further updates until MS straightens this out. MS owes its users and early adopters of Windows 8 that much.

    Also went from having 1.84 GB of free space to having 9.8-something on C: drive after reinstall recovery, no insignificant change on my little tablet system.

     Be happy to upload logs if you all will tell me where. Can't be making this up 'cause I wouldn't know how.

     Updated 6-15. Immediate problems. Reinstalled June 16. Belive Acer may use same type of UEFI as poster above mentions on this tablet but not sure.

    Was this answer helpful?

    0 comments
  4. Anonymous
    2013-06-16T23:41:56+00:00

    If you look here http://support.microsoft.com/kb/2821895 you will see this:

    The installer in the Unified Extensible Firmware Interface (UEFI) firmware does not work correctly.

    I run under UEFI.  Can this be the problem? 

    Hi,

    First of all as we see from this thread, the problem is not connected with this update of UEFI installation.

    But, you are right, I have the same concern that this one is the most important update from the package regarding UEFI installation.

    Best Regards, Nikolator

    Was this answer helpful?

    0 comments