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-14T15:40:22+00:00

    Hey, I had that two hour clean disk session..  dropped c drive from 40gb to 30, then back up to 33 when it made that side by side reserve.tmp 3.0gb file             Don't delete that , it will go away at the right time.

    Here on technet:

    social.technet.microsoft.com/Forums/en-US/w8itproperf/thread/e800e7d8-0a57-4071-a9ea-c97a26b3eb0f

    http://social.technet.microsoft.com/Forums/en-US/w8itproperf/thread/e800e7d8-0a57-4071-a9ea-c97a26b3eb0f

    they state, that a new LZX compression algorithm is used by TiWorker.exe for the WinSxs folder after this update, which is quite CPU-intensive.

    Both sfc and Disk Cleanup use TiWorker. 

    So far ok, MS has announced to give Windows a smaller system disk footprint and also my Windows folder has dropped in size.

    But there's still the problem of the giant CBS error logs, and the need to fix this via DISM. ( and the question whether it's really fixed by that ).

    Was this answer helpful?

    0 comments
  2. Anonymous
    2013-06-14T14:40:54+00:00

    Same problem here. The DISM fix seems to work. As I know, DISM downloads from Microsft the files that have problems, while SFC uses only local backups.

    Was this answer helpful?

    0 comments
  3. Anonymous
    2013-06-14T14:11:36+00:00

    Hi,

    Same Problem with KB2821895 for me on Win8 x86

    I discovered it to be problematic when I ran cleanmgr.exe afterwards, which took nearly 2 hours under 100 % CPU Usage.

    Thereafter got same problems with System File Checker reported by the others here.

    Also strange:

    After Update & running cleanmgr.exe, there is a huge "Reserve.tmp"-file in Windows/WinSxs, about 2 Gigs on my system, other folks in german forums report the same with different sizes from ca. 100 MB to > 3 Gigs. 

    Hey, I had that two hour clean disk session..  dropped c drive from 40gb to 30, then back up to 33 when it made that side by side reserve.tmp 3.0gb file             Don't delete that , it will go away at the right time.

    Here's an article on win Vista explaining sxs..  its roots are same on win 8 I think;

    http://blogs.technet.com/b/askcore/archive/2008/09/17/what-is-the-winsxs-directory-in-windows-2008-and-windows-vista-and-why-is-it-so-large.aspx

    I spot checked after DISM and all those files show up in sxs,  and many in regular tree folders. But not all - at least one is actually newer than the kb article shows.  Maybe that's because of DISM.  

    You know Microsoft will send out a fix for this, or patch/break/disable the sfc from checking those files :)

    Lots of things need fixing I think in win8, too dang sensitive to too many things.  Look in event logs

    ApplicationResourceManagement   lots have 100's and more errors there continuously without ever knowing.

    Was this answer helpful?

    0 comments
  4. Anonymous
    2013-06-14T10:03:52+00:00

    Hi

    I can confirm I have the same problem as others had explained. I'm using Windows 8 Pro x64 and did a fresh install. All windows updates are working except KB2821895 !

    This update is rotten all the new .ddl`s and files is not properly install in the system !

    Thanks

    Was this answer helpful?

    0 comments