Sharon, my XP (HE) installation is now 2 years old (re-installed once, early
days). SP1 installed when it became available, somewhat later. So, unlike
yours, my XP CD did/does not have SP1 included.
Hmm, sorry. Must not have explained it clearly enough. My situation is the
same as yours: installation created from an original XP CD. SP1 added
later.
Your explanation has seemingly conflicting statements (most unusual for you,
I may add)
1/ ".... source paths stored in the registry - SFC will use those (option to
select only appears when needed)" implication being that source paths
(should be) updated in the registry
The source paths in this situation are: One for the source at the time XP
was installed. One for when SP1 was installed. These are used by both
Windows File Protection (which appears to see and use both source paths)
and supposedly by SFC. However in my experience, SFC has not seen the path
to servicepackfiles or it was unable to use that path on my system for a
reason unknown to me.
2/ "You have personally used the source dialog to redirect ..." (which
conflicts with 1/ , in itself a conflict - either the paths are stored, or
not - either way, the stored path in my set-up is the XP CD, with no option
to redirect).
I use the Command prompt window for the sfc command too. The XP CD is
already in the CDrom drive before starting.
--SFC runs from start to end. No prompts. Watching the text in the command
prompt window, no replacements were made or they were made and the needed
files were accessible to SFC.
--SFC pauses, a gui dialog box appears and prompts for a source. It is
showing the drive with XP CD in the drop down box. So what other source do
I have for a WinXP installation? My SP1 files. Selecting the folder and
clicking OK, SFC continues.
--SFC continues. It again pauses (after being directed to the SP1 folder)
and wants a source again. So where can it be pointed? Back to the XP CD.
--Repeating the redirections when SFC requested a source until the tool
finally finishes.
--Running the tool one more time to make sure it got all the replacements
it needed and I am concerned about that having been accomplished after all
of the switching around from one source to another. When this run completes
successfully it finishes with no prompts.
Again, I have no idea why SFC does not pick up on the path for the Service
Pack Files (but Windows File Protection does). Or maybe SFC does pick this
up but -for whatever reason - couldn't find the target on my system for
some reason.
This is the important part:
Instead of *failing or skipping files* that it could not find, I was asked
for a source and the dialog box that appeared gave me the controls to
select it. I thinks it's reasonable to expect the same thing to occur on
anyone else's system if there was a file needing replacing and SFC couldn't
find a source.
Plus - it ran for some considerable time, then just closed at end with no
comment (should there not be a courtesy "No Problem found" (or "problem
fixed" info message, for courtesy?). That would reassure users, who have
posted same concern.
I agree and also think it's odd that there are no finishing comments from
SFC. But as we have seen from using it, it is the normal mode of operation
for this tool. If you see SFC start and it finishes without any visible
events that demand attention from the user, you can safely conclude that
the operation is complete and that whatever needed doing has been done.