Please drop an email to:
(e-mail address removed)
Jeff Dillon is seeking additional information to help
resolve the "error 101" issue.
Describe your experience.
I'm not sure if he is still looking for more information,
or how quickly you might hear back, but you should get a
response.
Use Error 101 as the subject header of the email.
---------------------------------------------
Here's the help file text:
* If you see a dialog box with the following message after
you start your computer or when you start Microsoft
Windows AntiSpyware, you need to repair or reinstall
Windows AntiSpyware. The following message can also refer
to Error 102 or Error 103:
Warning: Microsoft Windows AntiSpyware has encountered a
critical error (Error 101). Please restart Windows
AntiSpyware and run the program again.
If you continue to experience this problem, please
uninstall the program and install the most recent version
of Windows AntiSpyware. You can use Add or Remove Programs
in Control Panel to uninstall this version of Windows
AntiSpyware.
You can repair Windows AntiSpyware using Add or Remove
Programs in Control Panel. Click Microsoft AntiSpyware and
click Change. Click Next, and then click Update.
If you see the critical error message again, uninstall
Windows AntiSpyware and reinstall it. To do this, use Add
or Remove Programs in the Windows Control Panel. Click
Microsoft AntiSpyware and click Remove. You can reinstall
Microsoft Windows AntiSpyware at
www.microsoft.com/athome/security/spyware/software.
--------------------------------------------------
http://castlecops.com/t120958-
NEW_ERROR_101_FIX_that_works_for_Giant_and_MS_AS_5_15_2005.
html
http://castlecops.com/t119717-
Error_101_Possible_Workaround_Please_Test.html
-------------------------------------------------
From: "Steve Dodson [MSFT]"
<
[email protected]> Sent: 5/2/2005 7:12:33 AM
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.
