SFC /scannow, A Microsoft bug? A mess? Or both?

[Juan I. Cahis]

Dear friends:

Before I installed SP2, I could run "SFC /scannow" without any
problem, but after I installed it, I could not run it again. Always I
got the message that SFC needed the SP2 CD-ROM.

But I never had the CD-ROM. I downloaded the full SP2 (266 MB) from
Microsoft from the net, and I unpacked it to a "C:\SPSource"
subdirectory on my hard disk. Then, I installed SP2 from the
"C:\SPSource\I386\Update" subdirectory without any problem.

But SFC never worked again. Thousand times I checked the
"SourcePackSourcePath" and "SourcePath" registry variables, and other
related variables that it were mentioned in this newsgroup related to
SFC, and all were OK. But the problem persisted.

Finally, I found Microsoft's article Q328096, from the year 2002!!!
Although not related to SP2, it is related to SP1 and SFC. It
recommends to copy the contents of two of the Service Pack's
subdirectories to the Service Pack's *base* subdirectory ("I386"). And
that means to copy hundreds of files!!!

In my case, that meant to do the following:

COPY C:\SPSource\I386\new\*.* C:\SPSource\I386
COPY C:\SPSource\I386\ip\*.* C:\SPSource\I386

and then, SFC ran OK!!!

But, does this solution have any logic? Is there a better one? If
this is the only solution to the problem, then SFC is a buggy program,
why Microsoft has not corrected it?

I have an ACER C-110TC Tablet PC.


Thanks
Juan I. Cahis
Santiago de Chile (South America)
Note: Please forgive me for my bad English, I am trying to improve it!

 

[Guest]

Dear friends:

Before I installed SP2, I could run "SFC /scannow" without any
problem, but after I installed it, I could not run it again. Always I
got the message that SFC needed the SP2 CD-ROM.

But I never had the CD-ROM. I downloaded the full SP2 (266 MB) from
Microsoft from the net, and I unpacked it to a "C:\SPSource"
subdirectory on my hard disk. Then, I installed SP2 from the
"C:\SPSource\I386\Update" subdirectory without any problem.

But SFC never worked again. Thousand times I checked the
"SourcePackSourcePath" and "SourcePath" registry variables, and other
related variables that it were mentioned in this newsgroup related to
SFC, and all were OK. But the problem persisted.

Finally, I found Microsoft's article Q328096, from the year 2002!!!
Although not related to SP2, it is related to SP1 and SFC. It
recommends to copy the contents of two of the Service Pack's
subdirectories to the Service Pack's *base* subdirectory ("I386"). And
that means to copy hundreds of files!!!

In my case, that meant to do the following:

COPY C:\SPSource\I386\new\*.* C:\SPSource\I386
COPY C:\SPSource\I386\ip\*.* C:\SPSource\I386

and then, SFC ran OK!!!

But, does this solution have any logic? Is there a better one? If
this is the only solution to the problem, then SFC is a buggy program,
why Microsoft has not corrected it?

I have an ACER C-110TC Tablet PC.


Thanks
Juan I. Cahis
Santiago de Chile (South America)
Note: Please forgive me for my bad English, I am trying to improve it!

Installing a service Pack is almost like installing an entirely new
operating system it will work differently in the case of sfc /scannow it is
looking for files that
are no longer there, or they are different than the ones it is using for the
base
analysis.(I hope that I explaned this ok)
What you need to do is create a new XP CD with SP2 incorparated in it this
is called slipstreaming,after you have done this the sfc funtion should be as
it was.
http://www.neowin.net/forum/index.php?showtopic=188337&st=0&#entry2453585