Solved sfc /scannow failed after Windows Update

[georgeks]

Hello all
2 days ago I installed the latest updates from Microsoft. Then as standard procedure I ran sfc /scannow and it failed (was unable to repair corrupt files found).

I recovered my system (a few times...) using a previous saved image until eventually narrowed down the culprit(s) to the Optional Updates, but there were too numerous to start testing/verifying one by one, e.g. installing the update, running sfc /scannow and if failing restoring the system and starting allover again.

Did a new clean installation, but at some point during updates the same issue popped up again, sfc /scannow failed and was unable to repair corrupt files found.

Then I ran (as Administrator) dism.exe /online /cleanup-image /restorehealth which resolved the issue, only to have it re-appear after installing the rest of the available updates.

Re-running the command successfully repaired the corrupt files, but now the question: Why?

No other applications were installed, all the drivers were through Windows update.

Any thoughts?

 

[richc46]

SFC not being able to repair corrupt files is not due to the updates. Very often SFC cannot repair files. In that case run SFC 3 times. If it is still unable to repair files, you must do a repair install.

 

[georgeks]

My bad, I did run sfc /scannow more times (about 4 I think each time).

The question remains: Why the corruption after the updates?
I even have a license code for Media Center, and I hadn't installed it thinking it may be the culprit.

After running dism.exe and fixed all corrupt files, I installed Media Center and sfc /scannow came up clean.

 

[Layback Bear]

OP's system specs.

Computer type PC/Desktop
OS Windows 8.1 Pro x64

Windows 8 Forums

dism.exe

 

[georgeks]

Even though I updated my system specs, I think you should read (or re-read) my first post.

This is the first time this happened and even though I resolved it, I am curious as to why it happened.

 

[derekimo]

I don't have an answer for you George but it would be interesting to know which files were corrupted.

It might help those with more knowledge on the subject to see the results in the CBS.log,

SFC /SCANNOW Command - Run in Windows 8

That should take you right to option three to view the logs.

 

[Layback Bear]

All I'm try to state is your question might have a better response and answer in the Eight Forum because (dism.exe) to the best of my knowledge is not used in Windows 7.

https://technet.microsoft.com/en-us/library/hh825236.aspx

The Eight Forum is a sister forum.

I will get out of the way and let the Boss guide you.

 

[georgeks]

Unfortunately (or fortunately) I have re-installed my system and have only saved images after sfc /scannow came up clean.

So as not to waste resources, please consider this thread closed (I will keep looking though)

Thank you for your time, really.

 

[georgeks]

Update: (and some information that was missing)

I noticed the sfc /scannow error after a short on a different PC at home, that caused a fuse to pop and my system to shut down as a result.
Restoring from images saved previously on external HDDs failed as well, even though I had verified system file integrity before creating the images.

S.M.A.R.T came up fine on the system HDD (SAMSUNG SSD 840 120GB)....
BUT
Windows 8 setup reported that it could not be installed on that HDD.
There was a 0 KB partition on that HDD that could not be "merged" even if the other partition was deleted.

At the end using BlackIce I found that sector 0 was corrupt.
Went to a friend and used his ParagonHard Disk Manager to delete all partitions and e-write the mbr, and then all went well after that.