SFC /scannow terminates at 17%

[halfbytecode]

I encounter lockups at random on my machine running Windows 7 Home Premium (x64). I followed an article on microsoft.com where it was suggested running "sfc /scannow". Unfortunately, it terminates at 17% every time I have tried running it. I have included the log, from one run, here.

Could anyone suggest what I should do to fix this?

Log file: 2015-03-10 06:12:12, Info CSI 00000009 [SR] Verifying 100 (0 - Pastebin.com

 

[maxseven]

Probably your best bet is to do a Repair Install which reinstalls clean system files back to the date of the disc you use to do the Repair. Be advised you need your Product Key and it will take quite some time after to do all the Windows Updates that have been released since the date of your disc.

 

[halfbytecode]

Thanks for the suggestion. I'm kind of confused at this point. I installed new windows updates, which included System Update Readiness Tool. I ran "sfc /scannow" again, and this time it went past 17%, but terminated at 23%.

The log includes mentions of the corrupted files this time. I find it rather strange that most of the files listed as corrupt, do not (or rather should not, if I may) exist on my system. These files are from different "language folders", such as "ar-SA", "nb-NO", within the "system32" folder.

I had removed all languages but "en-US", while integrating windows updates into the ISO which was used to install the system. This is a clean install from a little over 2 months ago.

I'm wondering if I could cleanup any potential remnants of language files/settings, and see if most of the errors go away? For the other errors, could I try extracting the files from the ISO and replacing the corrupted or non-existent files?

 

[maxseven]

All of those "language folders" are on all of my systems as well, and I might guess that the extreme number of errors from your having removed those MAY be the cause of the sfc failing to complete i.e. just too many errors. Clearly sfc/Windows does NOT like your assumption that they are not needed.

From what I saw in your log file there are only errors relating to these deletions. I think your best bet therefore is to do a Repair Install with a complete W7 ISO. Then in the future if you have any new system file problems you will at least have a prayer of finding (and fixing) them.

It is also the first step in troubleshooting IMO: Fix Known Problems (and maybe the odd ones will go away)!

 

[halfbytecode]

Oh well, I had actually removed the additional languages using the slipstream tool I used for update integration, which provided an option of removing the languages. I did not expect it may be a bad choice, as I have been previously been doing the same during the Windows XP days.

Anyway, I think I have the MSDN ISO saved. I may use that some time to do a repair install, or rather a fresh install if I'm at it.

Thanks for your help and suggestions.

 

[maxseven]

If this makes you feel any better, I selected all the non-English folders on this W7HPx64 computer I'm using and they only take-up about 11MB of space.

Maybe you can find them on an iso or from a friend's PC and copy them across to your own to see if that elimates at least all of those particular errors.

BTW alongside the en-US folder is a en folder--I assume you have that one intact on your PC--looks important.