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-26T11:06:39+00:00

    Log Name:      Application

    Source:        ESENT

    Date:          7/26/2013 6:29:58 AM

    Event ID:      412

    Task Category: Logging/Recovery

    Level:         Error

    Keywords:      Classic

    User:          N/A

    Computer:      TheTouch

    Description:

    SettingSyncHost (15172) {300DFFBC-E056-4526-B1C1-CE85A6F87D28}: Unable to read the header of logfile C:\Users\Richard\AppData\Local\Microsoft\Windows\SettingSync\metastore\edb00001.log. Error -530.

    Event Xml:

    <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">

      <System>

        <Provider Name="ESENT" />

        <EventID Qualifiers="0">412</EventID>

        <Level>2</Level>

        <Task>3</Task>

        <Keywords>0x80000000000000</Keywords>

        <TimeCreated SystemTime="2013-07-26T10:29:58.000000000Z" />

        <EventRecordID>61655</EventRecordID>

        <Channel>Application</Channel>

        <Computer>TheTouch</Computer>

        <Security />

      </System>

      <EventData>

        <Data>SettingSyncHost</Data>

        <Data>15172</Data>

        <Data>{300DFFBC-E056-4526-B1C1-CE85A6F87D28}: </Data>

        <Data>C:\Users\Richard\AppData\Local\Microsoft\Windows\SettingSync\metastore\edb00001.log</Data>

        <Data>-530</Data>

      </EventData>

    </Event>

    Was this answer helpful?

    0 comments
  2. Anonymous
    2013-07-25T21:38:25+00:00

    You said logging problems... can you be specific?  Logging of what?

    Was this answer helpful?

    0 comments
  3. Anonymous
    2013-07-25T21:37:29+00:00

    Given that I have a server that this lovely patch is loaded on, I have to sit tight as well.

    Besides the sfc/ what other specific issues are you seeing?

    Was this answer helpful?

    0 comments
  4. Anonymous
    2013-07-25T12:33:42+00:00

    Thanks for that.

    Does that mean this update will continue to cause me problems if or until they issue a fix?

    Was this answer helpful?

    0 comments