Running sfc, etc.

[Robert11]

Hello,

a. After installing a new HD, I imagine it would be a good idea to run sfc.

Having problems with getting a specific program to run again, and a few other things.
Tried running it, but it requires that I be an Administrator.
To the best of my knowledge, I am logged on and set up as "the administrator"

What do I do next, please ?

b. assuming I can run the thing, what do I want to type in; e.g., any extensions, etc. after I type "sfc" ? Would like as complete a system check as possible, irrespective of time involved.

c. any other checking type of Windows programs that I should run similar to sfc, hopefully to pick up things in the reinstall that didn't go perfectly ?

Thanks,
Bob

 

[masoomsahib]

go to start and write cmd in the search bar.when it shows cmd,right click on it and click on Run as administrator.Than

try again using sfc.

 

[sk0t0s]

Here's the steps SFC /SCANNOW Command - System File Checker

 

[Robert11]

From OP: sfc Screen only on for a second or two ?

Hi,

First, a quick thanks for help.
Truly a great Forum, and Folks in it.
Over the years, lots of them, I would have been lost without all the help I've received.

Not too sharp with this, so please bear with me and my dumb questions.

Tried running sfc with the right mouse click to run as Administrator.

That black screen with what seems to be all of the old DOS lines in it comes up,
BUT only for a second or two, then disappears.

What's going on ?

Any other similar Windows checking program in W7 that I should also run, assuming I can get sfc to work ?

As reference, I posted several other questions as to what might wrong after I changed the hd in my PC. Most everything works again, surprisingly, except for one program. Trying to determine why.

Thanks,
Bob

 

[derekimo]

Did you get a UAC prompt when trying to open the command prompt window?

That closing after a second or two usually happens when it hasn't been elevated.

 

[Robert11]

From OP: Ran sfc, but cannot open the Log File it made ?

Hi,

Well, some progress, I guess.

Was able to run sfc, with all of your help.
It apparently found some corrupt files, but was not able to fix all of them, it says.

It also said that it generated a Log in:
C:\Windows\Logs\CBS\CBS.Log

But I can't seem to open it up when I go there. Keep getting the error msg. when I try of:
Notepad- Access is denied

I looked in Security for the file, and it seems like I have "Full Control" boxes ticked for everything: System, Local Sources, and Administrative.

I am down as the Administrator for this PC.

Any thoughts on hows to open this Log file ?

Thanks again,
Bob

 

[derekimo]

Yeah, if you move that log file to your desktop you should be able to open it.

You can run sfc a few times to see if it fixes those other ones, sometimes it can't fix them all at once.

 

[kado897]

You should run it up to three times and reboot between each run.

 

[sk0t0s]

Did you follow the option Number 3 of SFC /SCANNOW Command - System File Checker ?

If you follow those steps correctly you should be able to view your CBS.LOG file

 

[Robert11]

From OP: Still can't open

Hi,

I hate to appear dumber than I am with this stuff, but not sure if I selected option 3, or not. Will blame it on old age now.

I ran: sfc \scannow

It certainly did something, as there is a text Log file where i mentioned above.

But cannot open it.

Tried moving to desktop, and even tried WORD, but Word wouldn't open it either.

Any thoughts ?

Or, do i have to run it again ?

I am Administrator, and have all the security boxes for full control ticked.

Thanks,
Bob

 

[derekimo]

Try copy/paste with the log file instead of move, it just worked for me.

 

[sk0t0s]

If you follow the OPTION THREE correctly you should found sfcdetails.txt in your desktop

 

[Robert11]

From OP: Copy & Past Works To Open

Hi,

Yup, the copy and paste worked.
Weird though.

Thanks you very much for all the help, guys.

Bob

 

[derekimo]

You're welcome, have you run the sfc again?

 

[Robert11]

From OP:

Hi,

Got the Log report, but it is gibberish to me, frankly.

Still, running sfc was supposed to fix "some things", so was worth doing.

I will run it a few more times, as you suggested.

Thanks again,
Bob