Won't Start

[Tim]

The tool installed correctly, but when I try to start it
says:
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 verson of Windows
AntiSpyware. You can use Add or Remove Programs in the
Control Panel to uninstall this version of Windows
AntiSpyware. [OK]

I tried rebooting. I tried running the install again,
looking for a repair. I uninstalled and reinstalled.
Same problem. Any ideas?

 

[Engel]

Subject: Error 101 - Possible Workaround - Please Test
From: "Steve Dodson [MSFT]"

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.

 

[Richard]

I, too, am having the same problem. I have been running
the software since January with no problems and suddenly
this week, she wont load. The Gcasdtserv program takes
upwareds of 98% of CPU and just hangs.

I am running the Home edition and have changed the registry
per the previous post and set it to 0. This has made no
difference for me.

Anything new?

-----Original Message-----
Subject: Error 101 - Possible Workaround - Please Test
From: "Steve Dodson [MSFT]"

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.

-----Original Message-----
The tool installed correctly, but when I try to start it
says:
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 verson of Windows
AntiSpyware. You can use Add or Remove Programs in the
Control Panel to uninstall this version of Windows
AntiSpyware. [OK]

I tried rebooting. I tried running the install again,
looking for a repair. I uninstalled and reinstalled.
Same problem. Any ideas?
.

.

 

[Guest]

If you find out, let me know as I'm getting the same
problem.

 

[Tim]

I tried the workaround on my XP Pro system. Same
problem, even after rebooting.

-----Original Message-----
Subject: Error 101 - Possible Workaround - Please Test
From: "Steve Dodson [MSFT]"

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.

-----Original Message-----
The tool installed correctly, but when I try to start it
says:
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 verson of Windows
AntiSpyware. You can use Add or Remove Programs in the
Control Panel to uninstall this version of Windows
AntiSpyware. [OK]

I tried rebooting. I tried running the install again,
looking for a repair. I uninstalled and reinstalled.
Same problem. Any ideas?
.

.