Sfc is catewonkus

[Andy]

Despite having the correct path in the registy,

I can't use sfc /scannow, it keeps asking for a CD when I have the files in c:\i386.

 

[meerkat]

Despite having the correct path in the registy,

I can't use sfc /scannow, it keeps asking for a CD when I have the files
in c:\i386.

Hi A. go here and read the article, it`ll tell you how to direct SFC to look
on the hard drive
for the files, instead of asking for the Windows CD.
http://www.updatexp.com/scannow-sfc.html
good luck.

 

[Paul]

Despite having the correct path in the registy,

I can't use sfc /scannow, it keeps asking for a CD when I have the files in c:\i386.

I seem to remember editing two registry entries to get mine working.

My files (copy of CD) are on a FAT32 partition, D:\i386, and I needed to
point SFC to that. It's been a while since I tried it, perhaps
a previous install etc...

http://www.updatexp.com/scannow-sfc.html

Paul

 

[J. P. Gilliver (John)]

From: "Paul" <[email protected]> []

http://www.updatexp.com/scannow-sfc.html

Paul

HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Setup
SourcePath = C:\

If it is; C:\i386

SourcePath = D:\

If it is; D:\i386

..\i386 should be the same Service Pack level as the OS.

Both the referred webpage and what you've said imply I should have a key
in that part of the registry called SourcePath.

I don't have that key at all! I do have a key in that place called
ServicePackSourcePath, which is set to C:\WINDOWS; I do have a
C:\WINDOWS\I386 folder, which has 5,447 objects totalling 351MB in it (I
think they're all *.??_ files).

Should I have the other key there too? System is SP3, and was bought
with that preinstalled.

 

[David H. Lipman]

From: "Paul" <[email protected]> []

http://www.updatexp.com/scannow-sfc.html

Paul

HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Setup
SourcePath = C:\

If it is; C:\i386

SourcePath = D:\

If it is; D:\i386

..\i386 should be the same Service Pack level as the OS.

Both the referred webpage and what you've said imply I should have a key in that part of
the registry called SourcePath.

I don't have that key at all! I do have a key in that place called
ServicePackSourcePath, which is set to C:\WINDOWS; I do have a C:\WINDOWS\I386 folder,
which has 5,447 objects totalling 351MB in it (I think they're all *.??_ files).

Should I have the other key there too? System is SP3, and was bought with that
preinstalled.

I am running XP SP3

I have a c:\i386 folder which is all the XP installation files.

C:\i386 is at SP3 level (slip-streamed)

http://multi-av.thespykiller.co.uk/other/HKLM.jpg

 

[J. P. Gilliver (John)]

From: "Paul" <[email protected]> []
http://www.updatexp.com/scannow-sfc.html

Paul

HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Setup
SourcePath = C:\

If it is; C:\i386

SourcePath = D:\

If it is; D:\i386

..\i386 should be the same Service Pack level as the OS.

Both the referred webpage and what you've said imply I should have a
key in that part of
the registry called SourcePath.

I don't have that key at all! I do have a key in that place called
ServicePackSourcePath, which is set to C:\WINDOWS; I do have a
C:\WINDOWS\I386 folder,
which has 5,447 objects totalling 351MB in it (I think they're all
*.??_ files).

Should I have the other key there too? System is SP3, and was bought
with that
preinstalled.

I am running XP SP3

I have a c:\i386 folder which is all the XP installation files.

C:\i386 is at SP3 level (slip-streamed)

http://multi-av.thespykiller.co.uk/other/HKLM.jpg

So should I have the other key or not?

 

[Andy]

Despite having the correct path in the registy,



I can't use sfc /scannow, it keeps asking for a CD when I have the files in c:\i386.

I have sp3 and 561 Mb in the i386 folder.

Sfc will only work for me if I use my sp2 install disk in the cd drive.

I have an sp3 slipstream with sp3, but sfc won't use it even though source path points to it.

There are two versions of sfc dated 2004 and 2010.

I don't have time to babysit sfc telling it to skip whatever file it can't find.

Sfc needs this switch. sfc /if_file_isnt_There_go_to_next /scannow


Andy

 

[Paul]

I have sp3 and 561 Mb in the i386 folder.

Sfc will only work for me if I use my sp2 install disk in the cd drive.

I have an sp3 slipstream with sp3, but sfc won't use it even though source path points to it.

There are two versions of sfc dated 2004 and 2010.

I don't have time to babysit sfc telling it to skip whatever file it can't find.

Sfc needs this switch. sfc /if_file_isnt_There_go_to_next /scannow


Andy

The "thing" you use as a reference source of information for SFC,
has to match the service pack level. If the system is installed to SP2,
then the CD used would be SP2. If the system is rev'ed to SP3, then
the CD used for SFC should be SP3 as well. They have to match.
(Similarly, if you want to do a repair install later, you should
have that slipstreamed CD handy as well. That can solve the >137GB
disk drive problem, depending when you bumped up the size of your
hard drive.) In my case, I keep D:\i386 as a copy of the CD, and
it's at the same Service Pack level as my installed system.

The article here, makes reference to two registry entries. Adjust
these as you see fit, until SFC runs.

http://www.updatexp.com/scannow-sfc.html

"HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Setup
SourcePath D: <--- means D:\i386

"HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Setup\
ServicePackSourcePath C:\WINDOWS\ServicePackFiles <--- installed SPx

These may not be set by default on your system. When I tried SFC
on a previous install of WinXP, it kept asking for the CD as if it
didn't know where it was. I recollect having to edit two registry
entries, and then it did run. My config likely would match what
I've placed in the above two lines. Since I've reinstalled since then,
that registry info is gone (returned to defaults, whatever they are).
I'd have to re-test the above, and I have to do a backup first.
(I don't really trust SFC that much.)

I'm not at all convinced SFC does a good job. Yes, it occasionally
fixes a coincidentally damaged file (hard drive problem). But,
if you've been messing around, there was malware or whatever,
there's no guarantee this will fix it. It's not as good as a
repair install. It is not intended as a repair install (i.e.
put back all the SP2 files, tidy things up, polish the registry
or whatever). It doesn't do that. It's dumb and mechanical,
and compares a manifest to what it finds.

Here's a guy who keeps his two folders on a NAS. And pictures
are included of his registry settings. This would suggest
he's even gone to the trouble of moving the C:\WINDOWS\ServicePackFiles
off onto his NAS (network attached storage).

http://ask-leo.com/can_i_remove_the_servicepackfiles_folder_from_my_windows_folder.html

I don't actually have a C:\WINDOWS\ServicePackFiles on this machine,
and the reason for that, is the installer CD is a retail WinXP SP3
disc. So it was up-to-date at purchase. And no ServicePackFiles is
necessary. I probably don't need the second registry entry to complete
SFC in my current condition.

Did I mention backups ? Always a good idea, when dumb mechanical
scripts (SFC) are running, which have access to thousands of files.
One mistake and you could be non-bootable!

Good luck,
Paul

 

[J. P. Gilliver (John)]

From: "J. P. Gilliver (John)" <[email protected]>

In message <[email protected]>, David
H. Lipman
From: "Paul" <[email protected]>
[]
http://www.updatexp.com/scannow-sfc.html

Paul

HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Setup
SourcePath = C:\

If it is; C:\i386

SourcePath = D:\

If it is; D:\i386

..\i386 should be the same Service Pack level as the OS.

Both the referred webpage and what you've said imply I should have
a key in that part of
the registry called SourcePath.

I don't have that key at all! I do have a key in that place called
ServicePackSourcePath, which is set to C:\WINDOWS; I do have a
C:\WINDOWS\I386 folder,
which has 5,447 objects totalling 351MB in it (I think they're all
*.??_ files).

Should I have the other key there too? System is SP3, and was
bought with that
preinstalled.

I am running XP SP3

I have a c:\i386 folder which is all the XP installation files.

C:\i386 is at SP3 level (slip-streamed)

http://multi-av.thespykiller.co.uk/other/HKLM.jpg

So should I have the other key or not?

I gave you the information so you can draw your own conclusion.

The above post from you is timestamped 13:22:42 today (meaning mine is
earlier). Your post that mentioned both registry keys (SourcePath and
ServicePackSourcePath) is timestamped 18:16:16. I'm not clairvoyant (-:
(I have marked that later post for saving.)

 

[Andy]

From: "J. P. Gilliver (John)" <[email protected]>

In message <[email protected]>, David H. Lipman
From: "J. P. Gilliver (John)" <[email protected]>

In message <[email protected]>, David
H. Lipman
From: "Paul" <[email protected]>
[]
http://www.updatexp.com/scannow-sfc.html

Paul

HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Setup
SourcePath = C:\

If it is; C:\i386

SourcePath = D:\

If it is; D:\i386

..\i386 should be the same Service Pack level as the OS.

Both the referred webpage and what you've said imply I should have
a key in that part of
the registry called SourcePath.

I don't have that key at all! I do have a key in that place called
ServicePackSourcePath, which is set to C:\WINDOWS; I do have a
C:\WINDOWS\I386 folder,
which has 5,447 objects totalling 351MB in it (I think they're all
*.??_ files).

Should I have the other key there too? System is SP3, and was
bought with that
preinstalled.

I am running XP SP3

I have a c:\i386 folder which is all the XP installation files.

C:\i386 is at SP3 level (slip-streamed)

http://multi-av.thespykiller.co.uk/other/HKLM.jpg

So should I have the other key or not?

I gave you the information so you can draw your own conclusion.

The above post from you is timestamped 13:22:42 today (meaning mine is

earlier). Your post that mentioned both registry keys (SourcePath and

ServicePackSourcePath) is timestamped 18:16:16. I'm not clairvoyant (-:

(I have marked that later post for saving.)

--

J. P. Gilliver. UMRA: 1960/<1985 MB++G()AL-IS-Ch++(p)Ar@T+H+Sh0!:`)DNAf



What would be unusual would be if there weren't any coincidences at all for

several days in a row. Andy Roberts (UMRAt), 23rd. October 1998.

Your message is cryptic.

Can you translate that to American English ?

Andy

 

[Andy]

The "thing" you use as a reference source of information for SFC,

has to match the service pack level. If the system is installed to SP2,

then the CD used would be SP2. If the system is rev'ed to SP3, then

the CD used for SFC should be SP3 as well. They have to match.

(Similarly, if you want to do a repair install later, you should

have that slipstreamed CD handy as well. That can solve the >137GB

disk drive problem, depending when you bumped up the size of your

hard drive.) In my case, I keep D:\i386 as a copy of the CD, and

it's at the same Service Pack level as my installed system.



The article here, makes reference to two registry entries. Adjust

these as you see fit, until SFC runs.



http://www.updatexp.com/scannow-sfc.html



"HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Setup

SourcePath D: <--- means D:\i386



"HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Setup\

ServicePackSourcePath C:\WINDOWS\ServicePackFiles <--- installed SPx



These may not be set by default on your system. When I tried SFC

on a previous install of WinXP, it kept asking for the CD as if it

didn't know where it was. I recollect having to edit two registry

entries, and then it did run. My config likely would match what

I've placed in the above two lines. Since I've reinstalled since then,

that registry info is gone (returned to defaults, whatever they are).

I'd have to re-test the above, and I have to do a backup first.

(I don't really trust SFC that much.)



I'm not at all convinced SFC does a good job. Yes, it occasionally

fixes a coincidentally damaged file (hard drive problem). But,

if you've been messing around, there was malware or whatever,

there's no guarantee this will fix it. It's not as good as a

repair install. It is not intended as a repair install (i.e.

put back all the SP2 files, tidy things up, polish the registry

or whatever). It doesn't do that. It's dumb and mechanical,

and compares a manifest to what it finds.



Here's a guy who keeps his two folders on a NAS. And pictures

are included of his registry settings. This would suggest

he's even gone to the trouble of moving the C:\WINDOWS\ServicePackFiles

off onto his NAS (network attached storage).



http://ask-leo.com/can_i_remove_the_servicepackfiles_folder_from_my_windows_folder.html



I don't actually have a C:\WINDOWS\ServicePackFiles on this machine,

and the reason for that, is the installer CD is a retail WinXP SP3

disc. So it was up-to-date at purchase. And no ServicePackFiles is

necessary. I probably don't need the second registry entry to complete

SFC in my current condition.



Did I mention backups ? Always a good idea, when dumb mechanical

scripts (SFC) are running, which have access to thousands of files.

One mistake and you could be non-bootable!



Good luck,

Paul

Paul,

have backups because software and hardware make mistakes besides myelf.


When I see multiple versions of SFC and many other utilities, I start to gaze at the stars in heaven.

But fear not, Linux is a bit on the "iffy" side when it comes to being consistent and reliable.

Bringing up some issues about it on a Li*ux newsgroup brought on a firestorm of criticism.

Bill is a pretty decent person.

Take care,

Andy

 

[Paul]

Paul,

have backups because software and hardware make mistakes besides myelf.


When I see multiple versions of SFC and many other utilities, I start to gaze at the stars in heaven.

But fear not, Linux is a bit on the "iffy" side when it comes to being consistent and reliable.

Bringing up some issues about it on a Li*ux newsgroup brought on a firestorm of criticism.

Bill is a pretty decent person.

Take care,

Andy

Post back, what it took to get it working.
And whether it was worth the effort.
I've kinda given up on SFC.

Paul

 

[J. P. Gilliver (John)]

Your message is cryptic.

Can you translate that to American English ?

Andy

.... I replied [in British English (-:] by email.