Until today my Microsoft Anti Spyare was working fine,
today I got a critical error 101 message. I followed the
instruction and uninstalled the software and reinstalled
a new version from Microsoft but still got the 101
message when I tried to run?

I notice that this seems to be a common fault so I rang
Microsoft but they could not help and suggested I contact
the newsgroup.

Can anyone advise appropriate fix?

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_ER...5_15_2005.html




--

"CJB" <(E-Mail Removed)> wrote in message
news:007201c5b807$7c3fe050$(E-Mail Removed)...
> Until today my Microsoft Anti Spyare was working fine,
> today I got a critical error 101 message. I followed the
> instruction and uninstalled the software and reinstalled
> a new version from Microsoft but still got the 101
> message when I tried to run?
>
> I notice that this seems to be a common fault so I rang
> Microsoft but they could not help and suggested I contact
> the newsgroup.
>
> Can anyone advise appropriate fix?

Tried his fix and it DIDNT work so am trying other
suggestion.

>-----Original Message-----
>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
>
>
>
>
>--
>
>"CJB" <(E-Mail Removed)> wrote in
message
>news:007201c5b807$7c3fe050$(E-Mail Removed)...
>> Until today my Microsoft Anti Spyare was working fine,
>> today I got a critical error 101 message. I followed
the
>> instruction and uninstalled the software and
reinstalled
>> a new version from Microsoft but still got the 101
>> message when I tried to run?
>>
>> I notice that this seems to be a common fault so I rang
>> Microsoft but they could not help and suggested I
contact
>> the newsgroup.
>>
>> Can anyone advise appropriate fix?
>
>
>.
>

I finally fixed the problem by using the Repair Function
in the ADD / REMOVE PROGRAM section in the Control
Panel. No other fix worked.

>-----Original Message-----
>Until today my Microsoft Anti Spyare was working fine,
>today I got a critical error 101 message. I followed
the
>instruction and uninstalled the software and reinstalled
>a new version from Microsoft but still got the 101
>message when I tried to run?
>
>I notice that this seems to be a common fault so I rang
>Microsoft but they could not help and suggested I
contact
>the newsgroup.
>
>Can anyone advise appropriate fix?
>.
>

Great!!! and congratulations. Thank you for posting back
your results.

Engel
>-----Original Message-----
>I finally fixed the problem by using the Repair Function
>in the ADD / REMOVE PROGRAM section in the Control
>Panel. No other fix worked.
>
>>-----Original Message-----
>>Until today my Microsoft Anti Spyare was working fine,
>>today I got a critical error 101 message. I followed
>the
>>instruction and uninstalled the software and reinstalled
>>a new version from Microsoft but still got the 101
>>message when I tried to run?
>>
>>I notice that this seems to be a common fault so I rang
>>Microsoft but they could not help and suggested I
>contact
>>the newsgroup.
>>
>>Can anyone advise appropriate fix?
>>.
>>
>.
>

Thanks!

--

"CJB" <(E-Mail Removed)> wrote in message
news:008601c5b820$2a3d6ca0$(E-Mail Removed)...
> Tried his fix and it DIDNT work so am trying other
> suggestion.
>
>>-----Original Message-----
>>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
>>
>>
>>
>>
>>--
>>
>>"CJB" <(E-Mail Removed)> wrote in
> message
>>news:007201c5b807$7c3fe050$(E-Mail Removed)...
>>> Until today my Microsoft Anti Spyare was working fine,
>>> today I got a critical error 101 message. I followed
> the
>>> instruction and uninstalled the software and
> reinstalled
>>> a new version from Microsoft but still got the 101
>>> message when I tried to run?
>>>
>>> I notice that this seems to be a common fault so I rang
>>> Microsoft but they could not help and suggested I
> contact
>>> the newsgroup.
>>>
>>> Can anyone advise appropriate fix?
>>
>>
>>.
>>

Hmm - repair, and not update? That's certainly one to put first on the list
of items to try--interesting.

--

"CJB" <(E-Mail Removed)> wrote in message
news:01ae01c5b83d$e81f5310$(E-Mail Removed)...
>I finally fixed the problem by using the Repair Function
> in the ADD / REMOVE PROGRAM section in the Control
> Panel. No other fix worked.
>
>>-----Original Message-----
>>Until today my Microsoft Anti Spyare was working fine,
>>today I got a critical error 101 message. I followed
> the
>>instruction and uninstalled the software and reinstalled
>>a new version from Microsoft but still got the 101
>>message when I tried to run?
>>
>>I notice that this seems to be a common fault so I rang
>>Microsoft but they could not help and suggested I
> contact
>>the newsgroup.
>>
>>Can anyone advise appropriate fix?
>>.
>>

The repair function also worked for me, it was quick and
easy.
>-----Original Message-----
>Hmm - repair, and not update? That's certainly one to
put first on the list
>of items to try--interesting.
>
>--
>
>"CJB" <(E-Mail Removed)> wrote in
message
>news:01ae01c5b83d$e81f5310$(E-Mail Removed)...
>>I finally fixed the problem by using the Repair Function
>> in the ADD / REMOVE PROGRAM section in the Control
>> Panel. No other fix worked.
>>
>>>-----Original Message-----
>>>Until today my Microsoft Anti Spyare was working fine,
>>>today I got a critical error 101 message. I followed
>> the
>>>instruction and uninstalled the software and
reinstalled
>>>a new version from Microsoft but still got the 101
>>>message when I tried to run?
>>>
>>>I notice that this seems to be a common fault so I rang
>>>Microsoft but they could not help and suggested I
>> contact
>>>the newsgroup.
>>>
>>>Can anyone advise appropriate fix?
>>>.
>>>
>
>
>.
>

This is excellent news--I do have the feeling that this error may have
multiple causes, but I'll certainly cite this fix first when I get this
question.

--

"Stan" <(E-Mail Removed)> wrote in message
news:018701c5be3d$fc5616b0$(E-Mail Removed)...
> The repair function also worked for me, it was quick and
> easy.
>>-----Original Message-----
>>Hmm - repair, and not update? That's certainly one to
> put first on the list
>>of items to try--interesting.
>>
>>--
>>
>>"CJB" <(E-Mail Removed)> wrote in
> message
>>news:01ae01c5b83d$e81f5310$(E-Mail Removed)...
>>>I finally fixed the problem by using the Repair Function
>>> in the ADD / REMOVE PROGRAM section in the Control
>>> Panel. No other fix worked.
>>>
>>>>-----Original Message-----
>>>>Until today my Microsoft Anti Spyare was working fine,
>>>>today I got a critical error 101 message. I followed
>>> the
>>>>instruction and uninstalled the software and
> reinstalled
>>>>a new version from Microsoft but still got the 101
>>>>message when I tried to run?
>>>>
>>>>I notice that this seems to be a common fault so I rang
>>>>Microsoft but they could not help and suggested I
>>> contact
>>>>the newsgroup.
>>>>
>>>>Can anyone advise appropriate fix?
>>>>.
>>>>
>>
>>
>>.
>>