SFC - Install from hard drive.

For convenience, I'm trying to run SFC from my hard drive, instead of digging out my XP Pro full install disk every time.

I've gone into the registry and changed
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\SourcePath to reflect the directory on my hard drive where I copied the XP disk.

It still looks for the CD.

I seem to remember that there is another key value that has to be changed also, something like "CDInstall," to say that it is not installing from a CD. It's not listed under the above key.

Does anyone know what I have to do?

WinXP 2600 Professional - up to date
512 RAM
Compaq 1gig Athlon.

 

Not that simple, you need to change 2 registry keys.

These:

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Setup

SourcePath change to what you want
-----------------------------------------------------------------------------
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion

SourcePath change to what you want it has to have an I386 folder

Mike

 

Additionally you should make this a slipstream with SP4 or the latest one you want to commit to.

If you run an sfc /scannow without the slipstream you will loose all previous updates and will have to do them all again manually.

Unless of course the Cd is already up to date. Which means it would need to be only a few weeks old.

Slipstreamed with your last servive pack and you will not need to do the manual reinstall.

Mike

 

Thanks Mike, exactly what I needed. There is also a key in the Setup section called "CDInstall" that I changed to 0.

I run Windows Update after every run of SFC and it never says I need any updates. Are you saying that even though the updates are still showing as installed that they really aren't?

I know that you have to reinstall the updates after a Windows XP repair.

Anyway, thanks again. My brain was fried from trying to find that key. I've bookmarked it.

Ed

 

You may be right ED!

I always have used a slipstream of the latest service pack. But now that I think of it, it probably is on a reinstall that this happens.

Glad it is fixed.

Mike