Error when starting AntiSpyware

[Guest]

When I try to start AntiSpyware, I get the message "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." I tried the
Repair option in Control Panel, but it did not solve the problem. I then
uninstalled AntiSpyware, re-downloaded the program, and re-installed it. The
error is still happening. Any suggestions on how to fix this, or what is
causing the problem to occur?

 

[Dave M]

Hi Larry;
I could be on the wrong track, but I like Tom Emmelot's suggestion of a
total cleanup.
This is from thread "Errors 1904, 1905, 101" by Jerry started on 9/14 in
this newsgroup,
so if your not seeing the dll errors you might hold off on the system32
deletes on the first attempt:

uninstall, Delete MSAS folder and

delete in C:\windows\system32 the following files:
GCCollection.dll
hashlib.dll
gcUnCompress.dll

run a regceaner (Ccleaner)

http://www.ccleaner.com/ccdownload.asp

Also use the temp cleaner of Ccleaner.

Do a fresh install with version .615 (latest)
http://www.microsoft.com/downloads/...A2-6A57-4C57-A8BD-DBF62EDA9671&displaylang=en

Be shure you are on admin account!

 

[Guest]

Thanks for your suggestions, Dave. However, they didn't work. The same
problem still exists. Any other suggestions?

 

[Dave M]

Hi Larry,
There have been a number of suggestions about the 101 error, but
unfortunatly you've been through the more straightforward and perhaps more
successful ones (repair install and clean-up). There are two more that I'm
aware of... one from Microsoft and another listed on the Castlecops
(trustworthy) security site. Here's both references:

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.

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

 

[Guest]

THANK YOU, Dave!

The second part of your second e-mail, (from CastleCops), did the trick.

Thanks for all your help.

Larry

Hi Larry,
There have been a number of suggestions about the 101 error, but
unfortunatly you've been through the more straightforward and perhaps more
successful ones (repair install and clean-up). There are two more that I'm
aware of... one from Microsoft and another listed on the Castlecops
(trustworthy) security site. Here's both references:

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.

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

--
Regards, Dave

Thanks for your suggestions, Dave. However, they didn't work. The same
problem still exists. Any other suggestions?

 

[Dave M]

Great we nailed it. Thanks for getting back to us with your success.
Nothing is more frustrating than supplying a fix and having the outcome just
go off into a bit bucket. This is a learning process for everyone here.