SFC exe

  • Thread starter Thread starter Bearcat, Bc
  • Start date Start date
B

Bearcat, Bc

Is it safe to run the SFC.exe on a XP SP2 (Home) machine that has had all of
the updates added over it's life time (6 years) without replacing an updated
file with an older original XP file form the original disc? I get a missing
file error when I open Spy-Bot Search & Destroy after many years of no
problems. It still opens and runs correctly though. Just thought the SFC
might correct the problem, but did not want to make things worst.

Bc
 
Bearcat said:
Is it safe to run the SFC.exe on a XP SP2 (Home) machine that has had all
of the updates added over it's life time (6 years) without replacing an
updated file with an older original XP file form the original disc? I get
a missing file error when I open Spy-Bot Search & Destroy after many years
of no problems. It still opens and runs correctly though. Just thought the
SFC might correct the problem, but did not want to make things worst.

Bc

More information required. What is the file name that is missing?
 
Bearcat said:
Is it safe to run the SFC.exe on a XP SP2 (Home) machine that has had all
of the updates added over it's life time (6 years) without replacing an
updated file with an older original XP file form the original disc? I get
a missing file error when I open Spy-Bot Search & Destroy after many years
of no problems. It still opens and runs correctly though. Just thought the
SFC might correct the problem, but did not want to make things worst.

Bc
Sfc.exe on my machine was created in July of 2003. XP Pro SP2 with all
updates.
Jim
 
The file is "framedyn.dll" not found. I have removed spy bots totally and
reinstalled with newer version on several occasions but still have the same
error when I launch. I have even cleaned the registery several times after
removing and still same.
Bc
 
Thanks for the info as it fixed the issue. By the way the path had been over
written by the "Quick Time" path must be a conflict there.
Bc
 
Bearcat said:
Thanks for the info as it fixed the issue. By the way the path had been
over written by the "Quick Time" path must be a conflict there.

<snip>

Good to hear you got a result
 
Back
Top