sfc /scannow run from Installation Disk

I'm hoping someone can point me in the right direction. After running the sfc: Windows Resource Protection found corrupt files but was unable to fix some of them. So far I've been able to fix all but one. I ran the sfc from the windows install disc but not sure about the drive letters. Selected Repair your computer and it recognized my drive as F: (not C) Then Recovery Tools>Options menu>command prompt>enter In the command window > sfc /scannow /offbootdir=C:\ /offwindir=F:\Windows Is this correct? It found the corrupt file but couldn't fix it after 4 tries. My next guess would be to run a startup repair.

I'm not having any issues yet. Computer boots and runs OK. Will this corrupt file give me problems later and should I take care of it now? I'll attach the CBS.log after I ran the findstr command. Is this an important file? Thank for help!

Thank you Brink. I installed the System Update Readiness Tool but still have the corrupted file.

rickburton said:

sfc /scannow /offbootdir=C:\ /offwindir=F:\Windows Is this correct?

After reading some more of that tutorial it appears I may not have run the sfc correctly from Boot. I'will try that again and hope for the best Thanks again!

I ran the sfc 4 times from boot still couldn't fix it. I ran the startup repair and it didn't find any problems so I ran it one more and still no problems. I then installed and ran the 64 bit System Update Readiness Tool. Still no help. This is one stubborn little system file. Here's the last sfc.text log. I'm going to try to replace the corrupt file with the one off the installation disc. Could you confirm there's only one corrupt file from the sfc.text and that the file path is: C:\Windows\SysWOW64\NlsLexicons0416.dll. The [ml:48{24},l:46{23}]"\??\ in front of it has me a bit confused. Thanks again for all your help.

Replaced the file with one extracted from the install disc then ran the sfc command. Still had corrupt files. The sfc.text shows the original other three corrupt folders but not the one I just replaced. My bad, forgot to give the \SysWOW64 Folder back its permissions after taking ownership. Ran the sfc command four times and have only one corrupt file again. I’ll replace it like I did the other one and get the permissions right.Here's last sfc.text

I replaced it before I seen your post. I'm running sfc now. Thank you, that's good to know. If the CBS.log shows it's the same corrupt file after this sfc, do you think I can just ignore it unless I start having any issues my computer? I'm hoping to see no problems after the scan but I'm skeptical.

Well, It's still corrupt and sfc still can't fix it but it just the one file, isn't it? Last sfc.text: