Microsoft's recommendation:
---
We have a possible workaround in place for the 101 error.
Please test this and provide feedback on the following
steps:
For Windows XP Professional:
To change the setting on Windows XP Professional,
open "Local Security Policy" in Administrative Tools, or
run secpol.msc. You need to be an admin. to use this
tool. In the left pane, browse to Security Settings \
Local Policies \ Security Options. The policy name
is "System objects: Default owner for objects created by
members of the Administrators group". The allowable
settings are "Administrators group" or "Object creator".
Change it to "Administrators group." After that change
has been made, please refresh the policy by
typing: "gpupdate /force" from a command prompt.
For Windows XP Home Edition:
IMPORTANT: This article contains information about
modifying the registry.
Before you modify the registry, make sure to back it up
and make sure that you understand how to restore the
registry if a problem occurs. For information about how
to back up, restore, and edit the registry, click the
following article number to view the article in the
Microsoft Knowledge Base:
256986 Description of the Microsoft Windows Registry
The "Local Security Policy" snap-in is not available on
Windows XP Home Edition. To change the setting on XP
Home, you need to modify the Registry directly. Please
back up your registry in case you need to restore it. If
you do not feel comfortable doing this, do not try this
workaround.
In Regedit, navigate to
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa.
Find the value called "nodefaultadminowner". The
supported values are "0" for "Administrators group",
or "1" for "Object creator". Set the value to 0.
Please provide feedback if this is working.
An alternative solution that some claim works better:
http://castlecops.com/t120958-
NEW_ERROR_101_FIX_that_works_for_Giant_and_MS_AS_5_15_2005
..html
OR
Repair Function in the ADD / REMOVE PROGRAM section in
the Control Panel.
Engel
