Sfc /scannow

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

I recently run the above command along with /scanboot. How do I verify that
the command ran, and where do i find what it found and did? Thanks
 
mrwhite said:
I recently run the above command along with /scanboot. How do I verify that
the command ran, and where do i find what it found and did? Thanks
Click to expand...

Description of Windows XP and Windows Server 2003 System File Checker (Sfc.exe)
http://support.microsoft.com/kb/310747

Silj

--
siljaline

MS - MVP Windows (IE/OE) & Windows Security, AH-VSOP

Security Tools Updates
http://aumha.net/viewforum.php?f=31

Reply to group, as return address is invalid that we may all benefit.
 
Thank you for the links. However they do not address the original question.
yesterday, I restarted the laptop. sfc /scanboot did run. The question is
where do I go to discover what the command found wrong with my files, which
were the bad files, and what it did to correct the errors? Thanks.
 
Hi mrwhite - As others have pointed out, when sfc replaces a file, it notes
it in the Event Viewer. One additional thing to be aware of, however, is
that while sfc will replace corrupt, mis-versioned or missing system .dll's,
it does NOT re-register them. You need to do this for any such showing up
in the Event Viewer after sfc has completed, using

regsvr32 'filename' (without the quotes) for each such file. (You'll get
a confirmation after each one.)

in a CMD window in %SystemRoot%\System32


For reference, here are a couple of useful articles:

scannow sfc (sfc.exe)
http://www.updatexp.com/scannow-sfc.html

Windows File Protection
http://www.updatexp.com/windows-file-protection.html


--
Regards, Jim Byrd, MVP, DTS, ASVOP
My Blog, Defending Your Machine,
http://defendingyourmachine.blogspot.com/



In mrwhite <[email protected]> typed:
|| Thank you for the links. However they do not address the original
|| question. yesterday, I restarted the laptop. sfc /scanboot did run.
|| The question is where do I go to discover what the command found
|| wrong with my files, which were the bad files, and what it did to
|| correct the errors? Thanks. --
|| ss
||
||
|| "siljaline" wrote:
||
||| "mrwhite" wrote:
|||| I recently run the above command along with /scanboot. How do I
|||| verify that the command ran, and where do i find what it found and
|||| did? Thanks
|||
||| Description of Windows XP and Windows Server 2003 System File
||| Checker (Sfc.exe) http://support.microsoft.com/kb/310747
|||
||| Silj
|||
||| --
||| siljaline
|||
||| MS - MVP Windows (IE/OE) & Windows Security, AH-VSOP
|||
||| Security Tools Updates
||| http://aumha.net/viewforum.php?f=31
|||
||| Reply to group, as return address is invalid that we may all
||| benefit.
 
mrwhite said:
I recently run the above command along with /scanboot. How do I verify that
the command ran, and where do i find what it found and did? Thanks
Click to expand...


In order to really find out what was going on I'd run FileMon,
filtering on the command and including only WRITE records.

Actually including only WRITE records would just show you what
it was changing. You would also have to include READ records
to know where it was getting the copies from that it was writing.

E.g. I think that the files in ServicePackFiles (at least) play
an undocumented role in what gets copied but the only clue
that you may have that it was a source may be
a) that no indication was given that the CD was involved
or b) that the version of the resulting file matches the version
of the same file there.

Hmm... Ok. Now that I actually go looking for clues about that source
it does seem pretty definite:

<title>Inside Update.exe - The Package Installer for Windows and Windows Components</title>
http://www.microsoft.com/technet/prodtechnol/windowsserver2003/deployment/winupdte.mspx

(Live Search for
servicepackfiles "Windows File Protection" site:microsoft.com
)

<quote>
Windows File Protection, which replaces corrupted or missing operating system files, and the Windows Optional Component
Manager, which installs Windows components, both use Setup API functions to find the necessary files to install.

When Setup API is asked to retrieve a system file, it follows a sequence to find the file. It first looks for the file in the
dllcache
directory (%WINDIR%\system32\dllcache). It then looks in the driver cache (%WINDIR%\Driver Cache), and next in the
ServicePackFiles directory. The last place it looks is the original installation operating system CD-ROM.

</quote>



HTH

Robert Aldwinckle
---
 
Back
Top