"Jose" wrote in message
news:d94603b8-49be-4a8c-887d-33577fcf8664@40g2000vbr.googlegroups.com...
On May 20, 3:04 am, "Humpty Dumpty" wrote:
> I want to redirect SFC to the i386 folder in my root directory, because I
> don't remember where I misplaced my Windows CD. So, I performed the
> changes
> in the Registry that I found somewhere adviced:
>
> HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Setup
> HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\SourcePath
>
> In these places, I changed the original value which pointed to the CD
> drive
> (E:\)and wrote instead the actual location of the I386 folder in my
> computer
> (which I found with "search")
> as follows:
>
> C:\Windows\ServicePackFiles\ServicePackCache
>
> Nevertheless, after restart, SFC keeps asking me to insert the Windows
> installation CD. What can this be? And how can this be overcome?
>
> TIA
> Humpty
Here is a good article:
http://www.updatexp.com/scannow-sfc.html
Where did you get your idea?
I looked on my system in the C:\Windows\ServicePackFiles
\ServicePackCache folder (as you indicated) and there is a i386 folder
there, but it doesn't have much in it (18 files) so it appears
inappropriate for a reference point for SFC to look for files.
Depending on your situation, sfc looks out there and can't find what
it needs so asks you for another source. What is in the C:\Windows
\ServicePackFiles\ServicePackCache\i386 folder on your machine? If
you point sfc there, there needs to be a lot of stuff out there.
If your system is store bought, there is usually a c:\i386 folder in
the root of the C drive so you just change the registry to c:\ (don't
add i386) and be on your way.
Keep in mind that sfc /scannow only checks the 3498 specific files
that XP thinks are important so wherever you point it for a reference,
there needs to be a lot more than18 files, so your adjustment would
not work on my computer.
You did not say why you are running sfc /scannow, but if you are
having some issue that you think it will correct, you will probably
find it will not correct it. This is because if sfc /scannow ever
finds anything to do, you have some other problem with your Windows
File Protection mechanism. I will never recommend running sfc /
scannow for any issue and have never seen it fix a problem. It is
usually a frustrating waste of time and never solves any problem. If
it finds anything to do, something else is broken. If your system is
working properly you should never have to run sfc /scannow If you
think your Windows File Protection mechanism is broken, test it and
fix it if it needs fixing.
sfc /scannow is a popular shot in the dark suggestion and a thing to
"try" for situations where there is some issue that is not well
understood, but in the long run it is unlikely to fix your real
problem. You can try things all day long that might work maybe... but
if you have a problem, you need to be doing things, not trying things.
sfc /scannow should never find anything to do on a properly configured
system, but it is a good feeling to have it run successfully and find
nothing to do.
////////////////////////////////
Thank you, José, very clear and thorough. You're right. I found the i386
folder location by performing a search. And you're right: the folders I
found so named are not the real thing, and include only a few files.
In the root directory I don't find such a folder, so I think that for a
reason or another it is missing from my system. My next step will be to find
the Installation Disk and run sfc from it.
The reason I wanted to check the files system is that I am experiencing
problems with OE which I will post in the appropriate group.
Thanks a lot
Humpty