sfc /scannow not fixing bad file problems

[aqj]

I have run sfc /scannow multiple times. I have downloaded and run the System Update Readiness Tool and then rerun sfc. My log file continues to show many unfixed errors. The most recent log is attached. Help would be greatly appreciated!

 

[windude99]

I have run sfc /scannow multiple times. I have downloaded and run the System Update Readiness Tool and then rerun sfc. My log file continues to show many unfixed errors. The most recent log is attached. Help would be greatly appreciated!

Run sfc and reboot between each run. Do this 5 times.

 

[aqj]

Ran sfc 5 times with reboot between each. Final file attached. Still showing many issues. What next?

 

[andrew129260]

You can do this:

After taking ownership of those files, you can then extract/replace them from your Windows installation media.
http://www.sevenforums.com/tutorials/42776-extract-files-windows-7-installation-dvd.htmlhttp://www.sevenforums.com/tutorials/42776-extract-files-windows-7-installation-dvd.html

Or wait for someone like noel or tom who is an expert with this sort of thing.

 

[NoelDP]

There's only two problem files...

2014-08-15 10:15:12, Info                  CSI    00000331 [SR] Repairing 2 components
2014-08-15 10:15:12, Info                  CSI    00000332 [SR] Beginning Verify and Repair transaction
2014-08-15 10:15:12, Info                  CSI    00000334 [SR] Cannot repair member file [l:30{15}]"lltdres.dll.mui" of Microsoft-Windows-NetworkTopology.Resources, Version = 6.1.7600.16385, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture = [l:10{5}]"en-US", VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
2014-08-15 10:15:12, Info                  CSI    00000336 [SR] Cannot repair member file [l:20{10}]"lltdio.sys" of Microsoft-Windows-NetworkTopology-Inf, Version = 6.1.7600.16385, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch

(and there is NEVER any point in running SFC more than twice - the second time merely to tidy up the log to make it more readable)

I'll post a fix protocol later.

 

[NoelDP]

I've uploaded a file - aqjaa.zip - to my OneDrive at Noel's OneDrive
Please download and save it.

Right-click on the saved file and select Extract all...
Change the target to C:\ and click on Extract
Close all windows (it would be a good idea to print these instructions!)

Now reboot to the Repair Environment - as soon as the machine restarts, start tapping F8 - this should bring up the Advanced Boot Menu, at the top of which should be the option 'Repair my Computer'
Pick that
You'll have to log in with your username and password.

Pick the option to use a Command Prompt
At the prompt type
DIR C:\aqjaa
hit the enter key - if you get a 'Not Found' error try
DIR D:\aqjaa
or
DIR E:\aqjaa



The drive letter in use when you find the folder will need to be substituted (for<drive>) into the following command...



XCOPY <drive>:\aqjaa <drive>:\windows\winsxs /y /i /s /v /h



(e.g. XCOPY P:\wfire P:\windows\winsxs /y /i /s /v /h )



run the command (it should take almost no time) and when the prompt returns, type
EXIT
and hit the Enter key to exit Command Prompt - reboot to Normal Mode Windows.

Now run SFC /SCANNOW in an Elevated Command Prompt
then reboot and upload the new CBS.log file to your reply

 

[aqj]

Many thanks. The F8 key posed a problem but I managed to follow your instructions and reran sfc as the admin from the command prompt. The current file is attached.

 

[NoelDP]

There's nothing new in the file you attached? - it's still dated the 19th.

Please upload the full CBS.log file as requested - but you will also probably now have to upload the latest CBSPersist file as well