error 101

[janet]

also get "critical error 101" message when I try to load
Beta 1 to remove known spyware infection. was directed
to Giant Software in error.

 

[Guest]

Is been answer on other forums

 

[Bill Sanderson]

Here's what the program help recommends:

* 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.

----------------------------------------

Additionally:

Microsoft development staff are actively soliciting the file "errors.log"
from machines seeing this issue.

They won't acknowledge this help--i.e. you won't get a response or help
resolving the problem, but submissions will help to ensure that the breadth
of the issue is properly understood.

If you are able, please attach your errors.log file to an email sent to:

(e-mail address removed)

Use "error 101" as the subject header.

This file is found in the folder in which Microsoft Antispyware was
installed, typically c:\program files\microsoft antispyware

 

[Engel]

Subject: Error 101 - Possible Workaround - Please Test
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.

Please provide feedback if this is working.

--
-steve

Steve Dodson [MSFT]
MCSE, CISSP
PSS Security

--

This posting is provided "AS IS" with no warranties, and
confers no rights.
Use of included script samples are subject to the terms
specified at
http://www.microsoft.com/info/cpyright.htm

Note: For the benefit of the community-at-large, all
responses to this
message are best directed to the newsgroup/thread from
which they
originated.


..