Sorry--I don't think I have further guidance. If you are on build 509,
theres information in the help file--search on "known issues" and select
"release notes" from the results. Basically, they recommend several
reinstall options to try.
Microsoft developers are still investigating this error--it will help their
development effort if you are able to send an email with your errors.log
file attached to:
(e-mail address removed)
Put in the subject header "Error 101, fix did not work"
and include the information you've posted in this message about your windows
version and what you've tried, and what happened.
It is unlikely that you'll get a response, but it may well help the
development effort, since you seem to have a case that is outside the
boundaries that the current fix is able to deal with.
errors.log is a file found in the installation folder of Microsoft
Antispyware, typically c:\program files\microsoft antispyware. Feel free to
zip it if it is large.
I'd be interested to hear whether any of the suggestions in help are
effective for you. A simple uninstall leaves behind a good deal of
structure in the install folder. If you don't need to preserve settings or
quarantine, you can remove this. It also leaves behind a set of GC*.* files
in System32. GCDEF.DLL is part of the OS, and protected by SFP. The rest
can be deleted, moved, or renamed safely, in my experience. I haven't
investigated what's left in the registry, and haven't seen any posts here
where worrying about that had any objective effect on the outcome of any
problem.
--
FAQ for Microsoft Antispyware:
http://www.geocities.com/marfer_mvp/FAQ_MSantispy.htm
m said:
I tried searching here first, but the search feature is
broken. I have XP Pro, and changing that option still
doesn't work for me. When I try to run it, it loads spyware
signatures and then crashes with that error (101) when it
tries to start the spyware engine.
-----Original Message-----
Actually, the advice should be to read here, and then post, but anyway....
Here's the advice on this error from Microsoft:
--------------------------------------
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
