Error 101

  • Thread starter Thread starter fred jacobowitz
  • Start date Start date
F

fred jacobowitz

I installed beta2 as administrator. It works fine. As
applied the patch for the updater. But, if i log in as
user Fred in administrators group I get message from
gcasDtserv.exe - Title: Error Text: Unexpected
error;quitting. Then I get the same message a second
time. (At minimun i would expect a Microsoft product to
put up a dialog box with the title set to the process
name.)
I click OK (no other choice). The splash screen says
LOADING. Then I get another box: Error Loaidng Microsoft
AntiSpyware
Information"Warining: 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. .....
Been there done that. I have uninstalled and re-
installed it many times as the Administrator. What is
error 101?
Fred Jacobowitz
 
Try all three

From: "Bill Sanderson" Sent: 3/27/2005 4:01:31 PM

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--you could forward what you've
posted here.
Use Error 101 as the subject header of the email.


From: "Steve Dodson [MSFT]" 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.



From: "Steve Dodson [MSFT]" Sent: 7/13/2005 12:04:48 PM

Please install the latest build (614) which expires in
December 2005 and let
me know if this is working for you. You can get the latest
build at
www.microsoft.com/spyware.
 
Thank you for your suggestions. I have tried all three but I shot another
message off to (e-mail address removed).
Thank you for your assistance.
Engel said:
Try all three

From: "Bill Sanderson" Sent: 3/27/2005 4:01:31 PM

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--you could forward what you've
posted here.
Use Error 101 as the subject header of the email.


From: "Steve Dodson [MSFT]" 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.



From: "Steve Dodson [MSFT]" Sent: 7/13/2005 12:04:48 PM

Please install the latest build (614) which expires in
December 2005 and let
me know if this is working for you. You can get the latest
build at
www.microsoft.com/spyware.
-----Original Message-----
I installed beta2 as administrator. It works fine. As
applied the patch for the updater. But, if i log in as
user Fred in administrators group I get message from
gcasDtserv.exe - Title: Error Text: Unexpected
error;quitting. Then I get the same message a second
time. (At minimun i would expect a Microsoft product to
put up a dialog box with the title set to the process
name.)
I click OK (no other choice). The splash screen says
LOADING. Then I get another box: Error Loaidng Microsoft
AntiSpyware
Information"Warining: 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. .....
Been there done that. I have uninstalled and re-
installed it many times as the Administrator. What is
error 101?
Fred Jacobowitz
.
Click to expand...
Click to expand...
 
-----Original Message-----
Thank you for your suggestions. I have tried all three but I shot another
message off to (e-mail address removed).
Thank you for your assistance.
Try all three

From: "Bill Sanderson" Sent: 3/27/2005 4:01:31 PM

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--you could forward what you've
posted here.
Use Error 101 as the subject header of the email.


From: "Steve Dodson [MSFT]" 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.



From: "Steve Dodson [MSFT]" Sent: 7/13/2005 12:04:48 PM

Please install the latest build (614) which expires in
December 2005 and let
me know if this is working for you. You can get the latest
build at
www.microsoft.com/spyware.
-----Original Message-----
I installed beta2 as administrator. It works fine. As
applied the patch for the updater. But, if i log in as
user Fred in administrators group I get message from
gcasDtserv.exe - Title: Error Text: Unexpected
error;quitting. Then I get the same message a second
time. (At minimun i would expect a Microsoft product to
put up a dialog box with the title set to the process
name.)
I click OK (no other choice). The splash screen says
LOADING. Then I get another box: Error Loaidng Microsoft
AntiSpyware
Information"Warining: 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. .....
Been there done that. I have uninstalled and re-
installed it many times as the Administrator. What is
error 101?
Fred Jacobowitz
.names roy.and here is my workaround remove microsoft
Click to expand...
Click to expand...
Click to expand...
antispyware if in add and remove menu,next download the
beta from microsoft download center,save to desktop as
usual,now try to run it from there,this has to be done
first ok if you get error now go to c:\windows open and
find downloaded installation folder open and there should
be windows installer package for microsoft
antispyware,open the installer and run,this has worked
twice for me flawlessly good luck and let us know if this
works ok regards roy
 
-----Original Message-----
I installed beta2 as administrator. It works fine. As
applied the patch for the updater. But, if i log in as
user Fred in administrators group I get message from
gcasDtserv.exe - Title: Error Text: Unexpected
error;quitting. Then I get the same message a second
time. (At minimun i would expect a Microsoft product to
put up a dialog box with the title set to the process
name.)
I click OK (no other choice). The splash screen says
LOADING. Then I get another box: Error Loaidng Microsoft
AntiSpyware
Information"Warining: 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. .....
Been there done that. I have uninstalled and re-
installed it many times as the Administrator. What is
error 101?
Fred Jacobowitz
.
Click to expand...

Hi Fred,

I have the same error but I got this while trying to fix a
customer's PC that is badly infected with trojans and
viruses. My hope was that this tool would give me a
starting off weapon against the problems. After the install
I launched the program and got the 101 error and message.
I would hope that MS would provide a tool that is
transparent to malware. I hope we get an answer to this
problem. It makes little sense to provide a rescue-like
tool that can only be installed on a "clean" PC. The
viruses and malware are desktophijack.b, msole32,
InProcSer32 error access denied (cannot install SP2), and
PSGUARD.exe disguising itself as an AV tool.
Regards,
Peter van Sprewenburg
 
Back
Top