Solved sfc /scannow run from Installation Disk

[rickburton]

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!

 

[Brink]

Hello Rick, and welcome to Seven Forums.

You might see if the listed items in the blue note box under step 4 of OPTION TWO in the tutorial below may be able to help.

http://www.sevenforums.com/tutorials/1538-sfc-scannow-command-system-file-checker.html

Hope this helps for now,
Shawn

 

[rickburton]

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

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!

 

[rickburton]

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.

 

[Brink]

That's the only one that I see listed in your SFC log as well.

 

[rickburton]

[FONT=&quot]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[/FONT]

 

[Brink]

It's showing the same NlsLexicons0416.dll file, but in the component store location, being corrupted with a hash mismatch.

Since you already replaced it in the System32 folder, then I wouldn't worry about it anymore if you are not having any other issues.

 

[rickburton]

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.

 

[rickburton]

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

 

[Britton30]

Here's two NlsLexicons0416.dll files, one for system32, the other for SysWOW64 folders, try replacing yours with them. If not, use the PC as normal, as Brink suggests.


View attachment NlsLexicons0416.dll.zip

 

[rickburton]

Thank You! I'll give it a go and post back. You guys are awesome for all the help.

 

[Robbie77]

Hi, I'm not as experienced as all of you, but, if that File is showing as corrupt is it not possible to simply delete it from thr Windows Folder--then run sfc /scannow and replace the file from the Installation disk?
I've just moved up to W7 and want to run sfc*** but I see no "run" option in the Start menu as in XP ( which made life easy) ---Is there no such option in W7?
Robbie

 

[Britton30]

Yup, press the Windows logo key and "r" and it will bring up the run command, but you should start sfc /scannow from an Elevated cmd prompt. I don't think the SFC will grab it from a disk, it checks in the system's winsxs folder for good copies. If not there, it can't do a repair.
Before replacing the files, you can do this: http://www.sevenforums.com/tutorials/1911-take-ownership-shortcut.html and Take Ownership will be available in the right-click menu of any file.

This may help, run the steps outlined in this tutorial, Option Two, and reboot the system:
http://www.sevenforums.com/tutorials/1538-sfc-scannow-command-system-file-checker.html#post14392
You may get this result:

Windows Resource Protection found corrupt files and successfully repaired
them. Details are included in the CBS.Log windir\Logs\CBS\CBS.log. For
example C:\Windows\Logs\CBS\CBS.log
The system file repair changes will take effect after the next reboot.

Or a message that no integrity violations were found.
Or that Windows Resource Protection found errors it cannot repair.

 

[Robbie77]

Hi Brit,
Thanks for the help with the Keys. I tried the Command Prompt method--but hit a problem there---and see on these Forums that others have the same---My Command Prompt window shows C:\Users\Robert> ---when I type in the sfc /scannow --it tells me I must be logged in as Administrator.
I only have the Administrator Account...so it's obvious that is not being recognised somehow. When I go through Accessories>Command Prompt>, the Command prompt window shows C:\Users\Robert > and no Administrator.If I go Accessories >rt click "Run" > Properties > Advanced> the Window shows both properties greyed out ---"Run as Administrator" is unchecked and the "Run in separate memory space"(whatever that means) is checked --- How to "ungrey" those Advanced Properties options? Would that solve the problem by being able to check the Administrator box and uncheck the other?
I can run sfc /scannow if I rt click on Command prompt in Accessories and click on Run as Adminstrator, but that doesn't change the greyed out options!
Turning off User Acct Control > reboot, doesn't change anything either. What needs to be changed is the entry which comes up in the Command prompt Window. Is it a Registry error?
I have run the filechecker and got the "No integrity violations found" result---so happy about that!! I would like to resolve that "Greyed out" problem though.

 

[Britton30]

It's in the tutorial, http://www.sevenforums.com/tutorials/783-elevated-command-prompt.html

You can also type %windir%\system32\cmd.exe in the Start Search box and tap enter.

 

[Robbie77]

Brit--thanks for speedy response. In Command Prompt Properties, Shortcut tab--both Target and Start in entries are correct but the Command Prompt ALWAYS opens --in the Administrator: Command Prompt window-- with C:\Users\ my name and NOT with C:\Windows\System32>, which it should do. When I enter sfc /scannow --it runs, but no matter which method of Command Prompt entry I use I do not get C:\Windows\System32 in the CP Window ever. As I only have an Administrator Account it should not be necessary to open Cmd Prompt windows whenever I want to do something---otherwise there is no point to having an Admin Acct!
I get no requests for Login or Password --nothing.

Robbie

 

[Britton30]

Neither of the solution I posted will open the elevated cmd prompt?
Maybe you should tell me what it is you are wanting to do again, the cmd prompt isn't commonly used, but for chkdsk, sfc, diskpart, etc, it has to be.

Have a look at http://www.sevenforums.com/tutorials/507-built-administrator-account-enable-disable.html the Note box explains some info about admin accounts, then you may try to enable the hidden one.

 

[Robbie77]

Brit--I don't know how, but--the problem has resolved!! I followed the tutorial--and a couple of others--somewhere between something happened and the Advanced Properties greyed out options are now active--checked the Run as Administrator box---problem solved ---don't get the message telling me I have to be Administrator / have Administrator rigfhts to run sfc filecheckerHowever, the Command Prompt window still does not open with C:\Windows\System32> ---still C:\Userss \Robbie>. Why is that?

Regards Robbie

 

[Britton30]

dunno, did you try the link in my post #15?

 

[Robbie77]

Hi Brit---the answer is in your Post 17. Solved now--my Built-in Admin Acct was disabled - The Administrator Command Prompt now opens with correct ---C:\Windows\system32> entry.

Thanks for your help in solving this, Robbie