KB2821895 Windows 8 x64 Update 06.11.2013 problem

Anonymous

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.

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

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.

0 comments

117 additional answers

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 No comments
Anonymous

2013-08-01T05:02:28+00:00

A single run of DISM followed by a single run of SFC fixed this issue for me completely. Thank you!
Was this answer helpful?

0 comments No comments
Anonymous

2013-08-04T18:27:40+00:00

Do I have to run dism command every time before I can run sfc scan?
Was this answer helpful?

0 comments No comments
Anonymous

2014-02-04T10:26:36+00:00

hello

I've got the same problem with this update. I don't seem to get it fixed. I've tried a checkhealth, scanhealth and a restorehealth. The checkhealth is the only thing that works. It said that it was repairable, which pleased me. But the scanhealth and the restorehealth don't do anything. I've let both run for over half an hour with no results. I also checked the taskmanager and it indeed doesn't seem to be doing anything.

also, it seems to be impossible to simply delete the particular update for some reason. I'd like to know what my options are. Do I need to reboot or is there another way?

thank you
Was this answer helpful?

0 comments No comments