microsoft antispyware error

[ksh]

My microsoft antispyware had a critical error occur:
Error 101. I can't open up the software anymore. Any
help with explaining what this is & how I can fix it
would be much appreciated.

 

[Andre Da Costa]

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.
--
Andre
Extended64 | http://www.extended64.com
Blog | http://www.extended64.com/blogs/andre
http://spaces.msn.com/members/adacosta
FAQ for MS AntiSpy http://www.geocities.com/marfer_mvp/FAQ_MSantispy.htm

 

[Thomas]

I have been using Microsoft Antispyware beta version for a
while and it has been great. All of a sudden I have
started getting error 102. It told me to uninstall and
reinstall so I did. I still get error 102.

Any more ideas?

 

[Tag]

I am getting the same error. When I try to uninstall the
app. I get the message that the Windows installer is
corrupt. I can no longer re-install this app.

 

[Carolle]

-----Original Message-----
My microsoft antispyware had a critical error occur:
Error 101. I can't open up the software anymore. Any
help with explaining what this is & how I can fix it
would be much appreciated.
.
Solution:

Have read in Microsoft Anti-Spyware that when one
encounters errors 101, 102,103, that THEY MUST REMOVE
THE PROGRAM ENTIRELY IN "Control Panel" and then re-
install the MAS AGAIN.

Hope it helps - Seen this info on the MAS site.

 

[Guest]

I un-installed it and re-installed it and continue to recive critical error
101.
Please help, I have no dubt my system is runing slower because of spyware

 

[Dave M]

There are 6 known possible fixes for Error 101 listed here:

http://castlecops.com/t120958-NEW_ERROR_101_FIX_that_works_for_Giant_and_MS_AS_5_15_2005.html
http://www.geocities.com/marfer_mvp/FAQ_MSantispy.htm

In addition, there was a Ms suggested fix that I don't ever remember working for
anyone... but here it is:

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.

-- -steve
Steve Dodson [MSFT]
MCSE, CISSP PSS Security