1. This site uses cookies. By continuing to use this site, you are agreeing to our use of cookies. Learn More.

SFC

Discussion in 'Windows XP' started by Humpty Dumpty, May 20, 2010.

  1. Humpty Dumpty

    Humpty Dumpty Flightless Bird

    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
     
  2. Jose

    Jose Flightless Bird

    On May 20, 3:04 am, "Humpty Dumpty" <so...@antispam.net> 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.
     
  3. SC Tom

    SC Tom Flightless Bird

    "Humpty Dumpty" <sorry@antispam.net> wrote in message
    news:-Ov8rmq%239KHA.5848@TK2MSFTNGP06.phx.gbl...
    >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
    >


    I agree with Jose's post. I haven't seen any real results from SFC since
    Win98.

    If you want to try it though, your best bet would be to slipstream SP3
    (assuming you're at SP3) onto an XP installation disk, then run SFC. Here's
    some instructions if you're not sure on how to do it:
    How to Slipstream Windows XP Service Pack 3
    http://www.howtohaven.com/system/slipstream-xp-service-pack-3.shtml
    That way, all the files SFC would need are on that CD, and if you need to do
    a re-installation of XP, you won't have to go through the aggravation of all
    the updates.

    If you're having a problem with your PC, explaining the problem here may
    bring you a better and easier solution than what you are trying now. Just a
    thought ;-)
    --
    SC Tom
     
  4. philo

    philo Flightless Bird

    On 05/20/2010 02: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
    >
    >
    >
    >




    Unless you have updated your SFC repository after all updates

    and unless you use SFC to restore files from there

    all you'll do is hose your system.

    Using SFC is just a plain bad idea
     
  5. Jose

    Jose Flightless Bird

    On May 20, 9:27 am, philo <ph...@privacy.net> wrote:
    > On 05/20/2010 02:04 AM, Humpty Dumpty wrote:
    >
    >
    >
    >
    >
    > > I want to redirect SFC to the i386 folder in my root directory, becauseI
    > > 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

    >
    > Unless you have updated your SFC repository after all updates
    >
    > and unless you use SFC to restore files from there
    >
    > all you'll do is hose your system.
    >
    > Using SFC is just a plain bad idea


    How does one update the SFC repository - especially after all updates?

    I have seen suggestions to update it, check it, verify it but never
    any instructions on how to do any of those things.

    I would like to know if my SFC repository is up to date, when should I
    update it and what to do about it if it is not up to date.
     
  6. Humpty Dumpty

    Humpty Dumpty Flightless Bird

    "Jose" <jose_ease@yahoo.com> wrote in message
    news:d94603b8-49be-4a8c-887d-33577fcf8664@40g2000vbr.googlegroups.com...
    On May 20, 3:04 am, "Humpty Dumpty" <so...@antispam.net> 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
     
  7. Jose

    Jose Flightless Bird

    On May 20, 11:43 am, "Humpty Dumpty" <so...@antispam.net> wrote:
    > "Jose" <jose_e...@yahoo.com> wrote in message
    >
    > news:d94603b8-49be-4a8c-887d-33577fcf8664@40g2000vbr.googlegroups.com...
    > On May 20, 3:04 am, "Humpty Dumpty" <so...@antispam.net> wrote:
    >
    >
    >
    >
    >
    > > I want to redirect SFC to the i386 folder in my root directory, becauseI
    > > 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


    Good.

    I think the best advice is to locate a genuine bootable XP
    installation CD and use it to create a new XP installation CD with SP3
    slipsreamed (as suggested by SC Tom). If you can't find yours (store
    bought systems generally do not come so equipped), just borrow a
    genuine bootable XP installation CD from a friend and use it to make
    one of your very own.

    Having that CD will help you now - with your sfc /scannow thing and
    may be of benefit to you in the future. sfc /scannow should run with
    no problem when you have all the proper pieces in place and it is a
    good feeling when it does.
     
  8. philo

    philo Flightless Bird

    On 05/20/2010 08:50 AM, Jose wrote:
    > On May 20, 9:27 am, philo<ph...@privacy.net> wrote:
    >> On 05/20/2010 02: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

    >>
    >> Unless you have updated your SFC repository after all updates
    >>
    >> and unless you use SFC to restore files from there
    >>
    >> all you'll do is hose your system.
    >>
    >> Using SFC is just a plain bad idea

    >
    > How does one update the SFC repository - especially after all updates?
    >
    > I have seen suggestions to update it, check it, verify it but never
    > any instructions on how to do any of those things.
    >
    > I would like to know if my SFC repository is up to date, when should I
    > update it and what to do about it if it is not up to date.
    >



    Never used SFC

    I bet a Google search would give results though
     
  9. Twayne

    Twayne Flightless Bird

    In news:-Ov8rmq%239KHA.5848@TK2MSFTNGP06.phx.gbl,
    Humpty Dumpty <sorry@antispam.net> typed:
    > 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


    That can depend on which i386 you pointed it to. Often there are multiple
    versions spread around your disk unless it's new and you haven't installed
    any large applications yet.
    Not all i386 folders are created equal and they definitely don't have the
    same revision levels.
    I'd opt for finding your CD.

    HTH,

    Twayne`
     
  10. Twayne

    Twayne Flightless Bird

    PS Re: SFC

    I decided to send you an example of the multiple locations and got more than
    I bargained for, lol! Anyway, here is the current listing of my own i386
    folders on this particular machine, FYI:

    i386 0 10/27/2009 11:24 AM d
    C:/drivers\audio\R178832\common\

    i386 0 10/27/2009 11:24 AM d
    C:/drivers\audio\R178832\lang\

    i386 0 10/27/2009 11:24 AM d
    C:/drivers\audio\R178832\win2k_xp\

    I386 0 11/4/2009 9:49 PM d C:/

    I386 0 3/28/2010 9:48 PM d
    C:/pebuilder3110a\BartPE\

    i386 0 10/27/2009 5:34 AM d C:/Program
    Files\Creative\Sound Blaster X-Fi\Program\support\vista\

    i386 0 10/27/2009 5:34 AM d C:/Program
    Files\Creative\Sound Blaster X-Fi\Program\support\xp\

    i386 0 10/27/2009 5:34 AM d C:/Program
    Files\Creative\Sound Blaster X-Fi\Program\vista\common\

    i386 0 10/27/2009 5:34 AM d C:/Program
    Files\Creative\Sound Blaster X-Fi\Program\vista\lang\

    i386 0 10/27/2009 5:34 AM d C:/Program
    Files\Creative\Sound Blaster X-Fi\Program\vista\win2k_xp\

    i386 0 10/27/2009 5:34 AM d C:/Program
    Files\Creative\Sound Blaster X-Fi\Program\xp\common\

    i386 0 10/27/2009 5:34 AM d C:/Program
    Files\Creative\Sound Blaster X-Fi\Program\xp\lang\

    i386 0 10/27/2009 5:34 AM d C:/Program
    Files\Creative\Sound Blaster X-Fi\Program\xp\win2k_xp\

    I386 0 11/4/2009 9:49 PM d C:/Program
    Files\Dell\DBRM\osmedia\

    i386 0 11/10/2009 2:12 PM d C:/Program
    Files\Java\jre1.6.0_16\lib\

    i386 0 4/2/2010 8:19 PM d C:/Program
    Files\Java\jre6\lib\

    i386 0 2/23/2010 8:17 PM d C:/Program
    Files\Lavasoft\Ad-Aware\Drivers\

    i386 0 11/6/2009 3:34 PM d C:/Program
    Files\NetObjects\NetObjects Fusion 11.0\NetObjects System\JRE\1.4\lib\

    i386 0 3/29/2010 11:50 AM d C:/Program
    Files\NetObjects\NetObjects Fusion Essentials\NetObjects System\JRE\1.4\lib\

    i386 0 11/3/2009 8:21 PM d C:/Program
    Files\Norton Ghost\Agent\VirtualDrivers\lsilogic.scsi\2003\

    i386 0 11/3/2009 8:21 PM d C:/Program
    Files\Norton Ghost\Agent\VirtualDrivers\lsilogic.scsi\XP\

    i386 0 4/15/2010 10:10 AM d C:/WINDOWS\Driver
    Cache\

    i386 0 10/27/2009 11:24 AM d
    C:/WINDOWS\system32\ReinstallBackups\0001\DriverFiles\

    i386 0 10/27/2009 11:24 AM d
    C:/WINDOWS\system32\ReinstallBackups\0002\DriverFiles\

    i386 0 10/27/2009 11:24 AM d
    C:/WINDOWS\system32\ReinstallBackups\0003\DriverFiles\

    i386 0 10/27/2009 11:24 AM d
    C:/WINDOWS\system32\ReinstallBackups\0004\DriverFiles\

    i386 0 10/27/2009 11:24 AM d
    C:/WINDOWS\system32\ReinstallBackups\0005\DriverFiles\

    i386 0 10/27/2009 11:24 AM d
    C:/WINDOWS\system32\ReinstallBackups\0006\DriverFiles\

    i386 0 10/27/2009 11:24 AM d
    C:/WINDOWS\system32\ReinstallBackups\0007\DriverFiles\

    i386 0 10/27/2009 11:24 AM d
    C:/WINDOWS\system32\ReinstallBackups\0008\DriverFiles\

    i386 0 10/27/2009 11:24 AM d
    C:/WINDOWS\system32\ReinstallBackups\0009\DriverFiles\

    i386 0 10/27/2009 11:24 AM d
    C:/WINDOWS\system32\ReinstallBackups\0010\DriverFiles\

    i386 0 10/27/2009 11:24 AM d
    C:/WINDOWS\system32\ReinstallBackups\0011\DriverFiles\

    i386 0 10/27/2009 11:24 AM d
    C:/WINDOWS\system32\ReinstallBackups\0013\DriverFiles\

    i386 0 11/4/2009 8:27 PM d
    C:/WINDOWS\system32\ReinstallBackups\0014\DriverFiles\

    i386 0 11/5/2009 9:36 PM d
    C:/WINDOWS\system32\ReinstallBackups\0015\DriverFiles\

    i386 0 11/6/2009 12:31 PM d
    C:/WINDOWS\system32\ReinstallBackups\0016\DriverFiles\

    i386 0 4/25/2008 5:38 PM d
    C:/WINDOWS\system32\spool\XPSEP\

    i386 0 4/25/2008 5:38 PM d
    C:/WINDOWS\system32\spool\XPSEP\i386\



    HTH,



    Twayne`
     

Share This Page