sfc /scannnow - log?

[chmillman]

Hi all,

Ran an sfc /scannow on my laptop, the result reported some corrupt files that it couldn't fix (not very precise, didn't tell me how many...). Does it ever NOT find corrupt files?

As suggested by the tutorial, afterwards I typed in findstr /c:"[SR]" %windir%\logs\cbs\cbs.log >%userprofile%\Desktop\sfcdetails.txt to the command line and got a text file sfcdetails on my desktop... blank. Nothing in it.

OK, what did I do wrong? I did try going into cbs.log and reading that... OMG, the thing is miles (kilometers) long and has entries back to before the computer was created... The last section is the scan, but it's also miles long, and I have no way to interpret what's in there and what it fixed or considers needing fixing... :-( Is there any other way to distill this data so mere mortals can understand what might need to be fixed?

The computer is running, I'm just trying to track down a bunch of nagging annoyances that have plagued this machine since day one... so I thought I'd start with an sfc.

Thanks, --ch

 

[Brink]

Hello Chmillman,

Strange. Did you type that in a elevated command prompt?

In the cbs.log, the lines with the [SR] tag at the front are the ones for the SFC scan results.

Hope this helps,
Shawn

 

[chmillman]

Well, I left the elevated command prompt open after I ran sfc, so I assumed it was still elevated... Do I have to close the command window and run it again as administrator? --ch

 

[Brink]

CH,

No, no need to close and open the elevated prompt again.

Not sure why the .txt file would be blank though after running the sfc scan, but you can still resad the cbs.log itself and look for the [SR] tags.

 

[chmillman]

I tried that, there are 132 POQ entries, takes awhile to go through all, all "repair results created: " are blank... There are a number of entries about "ignoring duplicate ownership" of directories, a bunch of move file entries and some setting of registry keys... Well, anyway, doesn't look like it did much, and I don't know how to find the entries it said it couldn't fix (if any really exist).

Just to note opening the entire CBS.log file in Word, it's 11,000+ pages... --ch

 

[Brink]

You might run the scan again to see if you can use findstr /c:"[SR]" %windir%\logs\cbs\cbs.log >%userprofile%\Desktop\sfcdetails.txt to make it easier. Sometimes you will need to restart the computer after running the sfc /scannow command for it to finish doing repairs.

For corrupt files, you will need to run the chkdsk /f or chkdsk C: /f command to see if it can repair the corruption.

 

[SIW2]

Hi,

You could try this instead -

http://www.vistax64.com/tutorials/66978-system-files-sfc-command.html

Hope it helps

SIW2

 

[robertpri]

This a GREAT tool!
Many thanks!

I have this same error string about 10 times:

2009-02-09 16:45:18, Info CSI 00000291 [SR] Could not reproject corrupted file [ml:520{260},l:46{23}]"\??\C:\Windows\System32"\[l:22{11}]"autochk.exe"; source file in store is also corrupted

Ten times or so, it says "autochk.exe" is bad or corrupted, along with source file.
What is autochk.exe and how would i fix/replace it?

thanks

 

[SIW2]

Hi Robert,

It's easiest to download a copy from here and replace it - halfway down this tutorial

http://www.vistax64.com/tutorials/130824-chkdsk-will-not-run-startup-vista.html

Hope it helps

SIW2

 

[robertpri]

SIW2, many thanks again!

I'll find the valium and try it. Heh, who said Vista was difficult?

On that tutor page, it said this will reset chkdsk to not run at startup.

Does this mean is does run at boot? If so, could that be a problem with dual booting?

 

[SIW2]

Hi robert,

The download at STEP 2 is a fix only if it keeps trying to run at startup when you have not scheduled it.

The download at STEP 3 is the one you want - you can use it to replace your corrupt autochk file. There is one for if you have SP1 installed and a different one if you don't have SP1

Hope it helps

SIW2

 

[robertpri]

Did all the steps, registry merges, download the SP1 version, etc. Everything went well, except the properties of autochk.exe did not change in the target.

Refreshed, no change. tried to copy/paste again, and this time it says cannot be run in Win32 mode. I never tried to run it, just copy/paste.

Every step went perfectly well until this very last one.


----more
tried the old fashioned way--rename and replace, but it says i need permission. Obviously, I missed a step.

more more
I can take ownership of files "above and below" that one, but not autochk.exe or any exe file. I'll start over--after a break

more again:
I have full permissions in properties, owner, full control, effective permissions, etc. But the file won't right click to take ownership, and it still gives me that 'cannot run in win32 mode" I have SP1 and downloaded the 1800 version.

 

[SIW2]

Hi,

You could probably do that in Safe Mode , but as I can't be bothered to boot into Safe and back, I would just Take Ownership of the file I am trying to Replace.

I edited the registry to add Take Ownership to my right click context menu , but this .reg file will do it for you.

View attachment InstallTakeOwnership.zip

Hope it helps

SIW2

 

[robertpri]

Many thanks SIW2, you are truly a guru, but it's been too many hours now. I am the full owner on every property on that file, but it won't let me take ownership.

I will play with it tommow. Might try safemode. Considering how long this has taken, it might have been faster.

 

[SIW2]

Hope it works for you tomorrow in Safe Mode - not sure why that file is being so difficult.


I have heard of the "cannot run in win 32 mode" - believe it happens to drives / all programs on a drive , not sure if this is the same error.

SIW2

 

[neiby]

While researching my own sfc /scannow issues, I saw lots of reports of autochk getting corrupted. What the heck is up with that? Do Vista files get corrupted just by looking at your PC the wrong way or what? It appears that I have some sort of file system corruption and I have no idea why or what might have caused it. Very weird.

 

[jonny321321]

robertpri are u sure ur a administrator if u have never done this then u better do this and see if it works then

1. Logon to Vista using your normal username and password.
2. Click on the Start button
3. Click on Start Search.
4. Type,cmd.
5. Right-click cmd, select 'Run as administrator' from the shortcut menu.
6. In the black 'DOS box', type the following at the command line:
   Net help user
7. The idea of the last command is just to observe the options for Net User. In particular, examine the syntax to set the password.
8. The next instruction is the crucial command. I have chosen password = p£ssworD, you may want to choose different characters.
9. Net user administrator p£ssw0rd
10. Net user administrator /active:yes
11. Check the message : The command completed successfully
12. Switch User, or logoff
13. Logon as Administrator Password p£ssw0rD (Your password may be different!)

Trap1: There should be no space between the word 'active' and the colon.
/active :yes is wrong.
/active:yes is correct.

Trap2: You need a forward slash before /active
Net user administrator active:yes is wrong
Net user administrator /active:yes is correct
Thanks to Rob Hilton for pointing out this trap.
Trapx: Pay close attention to the command, it should be active, not activate.

thats a quote from http://computerperformance.co.uk/vista/vista_administrator_activate.htm

 

[robertpri]

jonny321321, many thanks, and I will give that a try.

First, please some clarifications:

1- if I log on as admin for some task, afterwards, I should logoff/on as user?
2- is it true we should not remain logged on as admin because it opens the door for possible problems? We should remain logged on as a user and not admin?

BTW: I am the only user on this laptop.

thanks

 

[SIW2]

Hi robert,

Yes if you enable the Super Admin account , it is a good idea to disable it when you are done.

http://www.vistax64.com/tutorials/67567-administrator-account.html

Hope it helps

SIW2

 

[jonny321321]

It depends how safe u are lol i run my account with full admin rights and no uac only because its very annoying when u find urself in another situation like that so i advise keep the admin account but also keep ur original account with not as many rights and use that one then u can switch when u need to!!