101 Error

[Fat andy]

I can't get past the 101 error. I have googled the
problem but the answers are all way beyond my skill
level. It's a real shame as I liked the system explorer
and found it useful for getting rid of spyware type
downloads.

Any clues for computer dummy

 

[Andre Da Costa]

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
--
Andre
Extended64 | http://www.extended64.com
Blog | http://www.extended64.com/blogs/andre
http://spaces.msn.com/members/adacosta
FAQ for MS AntiSpy http://www.geocities.com/marfer_mvp/FAQ_MSantispy.htm

 

[Engel]

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

I'm not sure if he is still looking for more information,
or how quickly you might hear back, but you should get a
response.
Use "error 101" as the subject header.


Steve Dodson has since posted a possible fix for this
issue:

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.

Post your results to the newsgroup. Share with others.

 

[Steve Dodson [MSFT]]

Do you have this issue running build 614?

--
-steve

Steve Dodson [MSFT]
MCSE, CISSP
PSS Security
http://blogs.technet.com/stevedod
--

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]

The only info I can get is that it is version one. I have
removed and re installed countless times so it should be
the latest release. The 101 error comes up as soon as I
click on the icon so I cannot access any build info.

Andy

-----Original Message-----
Do you have this issue running build 614?

--
-steve

Steve Dodson [MSFT]
MCSE, CISSP
PSS Security
http://blogs.technet.com/stevedod
--

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.

I can't get past the 101 error. I have googled the
problem but the answers are all way beyond my skill
level. It's a real shame as I liked the system explorer
and found it useful for getting rid of spyware type
downloads.

Any clues for computer dummy

.

 

[Guest]

I can navigate to the correct place, but have no idea how
to "find a value"

Like I said I'm a complete computer idiot!!

Andy

-----Original Message-----
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
--
Andre
Extended64 | http://www.extended64.com
Blog | http://www.extended64.com/blogs/andre
http://spaces.msn.com/members/adacosta
FAQ for MS AntiSpy http://www.geocities.com/marfer_mvp/FAQ_MSantispy.htm

I can't get past the 101 error. I have googled the
problem but the answers are all way beyond my skill
level. It's a real shame as I liked the system explorer
and found it useful for getting rid of spyware type
downloads.

Any clues for computer dummy

.