I avoid most of the "numbered" error threads these days because I don't feel
like I have a simple answer.
I don't think that this is an issue that is new with the new build--but the
reinstallation process seems to be creating that appearance.
The requirement for a reboot relates to the need to remove the shell execute
hook, as I understand it. The current installer cannot do that without the
restart. A new install doesn't require a restart.
It's been my general feeling about this product that most issues can be
fixed by uninstalling and reinstalling, perhaps with an additional step of
deleting the .gcd files (or, sometimes, JUST deleting the gcd files)--but
this issue seems to be beyond that and get to the multi-user issues, which I
expect must relate to the user registry hive, and perhaps permissions in
other registry hives. This is an area I'm pretty weak in--another hesitancy
to speak up.
I didn't note whether the machines in this thread were XP Home, or Pro?
Either can have multiple users.
I'm tempted to recommend using a good registry cleaner which is capable of
examining all the user hives for Microsoft Antispyware related entries and
removing them--but this is really blind advice. I've never looked at what
this program does in the registry--it hasn't been needed for the main run of
issues that people have here.
That kind of advice and the Windows Installer Cleanup tool, perhaps--are
what I think of in terms of returning the machine to a state as though the
beta had never been installed, and being able to start over.
I don't have very many machines with multiple users--perhaps a handful that
have two regular users, typically both administrators, and some other cases
where somebody uses a vacant office and signs in using their credentials
creating a new profile. I haven't seen these errors. Every once in a while
I'll see an error 101 on a server where I also come in by Remote Desktop--and
it is usually spurious--the app is up and running for both users.
Many of the numbered errors, and this is one, are generic errors from the
Windows Installer. There are KB articles, and perhaps newsgroup threads,
relating to these errors in other products:
http://support.microsoft.com/kb/237294/
for example.
This article may have some grains of wisdom that will help make sense of
this issue, as may others referencing the same error.
I can recall doing this for some other numbered error in the early days of
the beta, but I don't recall the outcome, or that I learned much about the
products workings from that effort. Because these are installer errors,
there will be third-party hits as well as Microsoft hits--a lot to sift
through.
I'll try to stick with this thread if you think it will help--I'd love to
have a test case for this myself--maybe I can try to create one with a
Virtual PC running Windows 2000 that I have.
