On Fri, 20 Jul 2007 20:08:00 -0700, Glen D <Glen
Eish, this is a real "heartsink" post, and I've been eyeing it awhile
Windows will spawn a temporary profile if the profile can't load,
which is often due to a bad registry hive, or a bad rehgistry hive log
file. The hive log file you can rename away or delete, but the hive
itself you would need to recover e.g. from System Restore \SVI.
This temporary profile is transient; changes are not persisted across
runtime sessions. So you're stuck with unsafe UI duhfaults etc.
Windows will spawn a duplicate profile with the PC name appended to
the end of the subtree name, if you "just" do a repair install. This
is in effect a new user account that has a different underlying CLSID
(or is that GUID?) and it will persist across runtimes as you expect.
An implication of this is that you should not hard-code account
subtree references, even to "known" names such as "All Users", as
these may no longer be active after a "repair" install.
Repairing the file system (ChkDsk /F or AutoChk) may re-facilitate
access, or irreversibly damage bent files in a way that ChkDsk can
then no longer detect as being bent.
All of the above is from XP experience, BTW, as are my notes [*1] on
recovering registry hives from \SVI via Bart. The concepts should
carry over where applicable, but the mechanisms will differ.
The most accurate diagnostic instrument
in medicine is the Retrospectoscope