Limited User- New Beta Release

[wankel]

I installed MSAS newest release while logged in as an
administrator. Everything OK. When I log in to my power
user account, I get an error message saying unexpected
error, quiting. MSAS will not run at all except in the
admin account. Tried uninstalling and re installing, but
have had no luck. Anybody got a solution?

 

[Robin Walker [MVP]]

I installed MSAS newest release while logged in as an
administrator. Everything OK. When I log in to my power
user account, I get an error message saying unexpected
error, quiting. MSAS will not run at all except in the
admin account. Tried uninstalling and re installing, but
have had no luck.

At present, Microsoft AntiSpyware Beta 1 will only operate correctly in
accounts with Administrator rights. This is a known restriction and will
probably change in future, but do not hold your breath.

 

[Andre Da Costa]

You have a limited user account running the application looking for spyware
on all files and folders. This includes the administrator account which
limited users may not be able to access. So we have to approach this
carefully in order to remove the spyware from all locations, but also
preserve file and folder permissions and access.

In short, we are addressing this for a future release, but it involves some
major coding and testing.
--
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

 

[Robin Walker [MVP]]

So we have to
approach this carefully in order to remove the spyware from all
locations, but also preserve file and folder permissions and access.

In short, we are addressing this for a future release, but it
involves some major coding and testing.

"We"??? I think you should make clear whom you are quoting.

 

[Andre Da Costa]

Oops, Steve Dodson, sorry, I sure I had copied that.
--
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

 

[Michael Seidner]

I understand the thinking that limited users are not in the best position to
do computer scans but shouldn't they at least have the "Real Time"
protection functioning?

Oops, Steve Dodson, sorry, I sure I had copied that.
--
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

 

[Robin Walker [MVP]]

I understand the thinking that limited users are not in the best
position to do computer scans but shouldn't they at least have the
"Real Time" protection functioning?

Much of the real-time protection and blocking involves reading or writing
parts of the registry that limited-user accounts might not have access to.

Unfortunately, when the precursor of MSAS was written (not by Microsoft)
almost all of the guidelines to developers (on the design of applications to
run in limited-user account status) were flouted. For instance, it stores
its preferences and data in a directory to which limited-user accounts do
not normally have write-access. MSAS Beta 1 is still in this messy state.

 

[Michael Seidner]

Thanks for the explanation. So maybe a way to avoid the "unexpected error -
quitting" message when the limited-user logs on would be nice.

 

[-Dan-]

While logged in a a power user, have you (or anyone) tried running it as Administrator. Just right click and select "Run As".

--
--Dan--



|I installed MSAS newest release while logged in as an
| administrator. Everything OK. When I log in to my power
| user account, I get an error message saying unexpected
| error, quiting. MSAS will not run at all except in the
| admin account. Tried uninstalling and re installing, but
| have had no luck. Anybody got a solution?

 

[lmb]

(e-mail address removed) <[email protected]> wrote:

At present, Microsoft AntiSpyware Beta 1 will only operate correctly
in accounts with Administrator rights. This is a known restriction
and will probably change in future, but do not hold your breath.

I have the same problem but both users are administrators (so your answer
that this happens with a limited user isn't true). Everything worked
perfectly ok (even with a Guest account) before I upgraded to version
615. I now get an error when accessing 1 account, but not with the other.
Tried every possible solutin that I found in this newsgroup, but the
problem persists. This is the error message I get on one of the
(administrator) accounts

"Error 1904. Module C:\Program Files\Microsoft AntiSpyware
\gcAntiSpywareLibrary.dll failed to register. HRESULT - 2147220473.
Contact your support personnel"

If I install MSAS on the other (administrator) account I don't get the
error, but the other user gets this error box "unexpected error,
quiting" as soon as they log on and MSAS doesn't start on that account.

On my daughters computer, also with 2 adminstrator users everything works
ok and they don't get errors on either on of the accounts and the program
and icon runs on both accounts too!

Any suggetions welcome. Is there a way I can download and go back to
version 614, that work work perfect for me.

LMB
ON Canada

 

[Michael Seidner]

While logged in a a power user, have you (or anyone) tried running it as
Administrator. Just right click and select "Run As".

Yes, that works but the user would still get the "Unexpected error -
quitting" message when they log on.


--
--Dan--



|I installed MSAS newest release while logged in as an
| administrator. Everything OK. When I log in to my power
| user account, I get an error message saying unexpected
| error, quiting. MSAS will not run at all except in the
| admin account. Tried uninstalling and re installing, but
| have had no luck. Anybody got a solution?

 

[jaime]

When connecting to Internet I work all the time as a limited user.
No problems of any kind here.Every updates and upgrades implemented smooth.
Real time protection active
Currently last version 615 with last definitions 5737
I can make scannings, but of course for a deep scan do it as ADM .

 

[Michael Seidner]

Hey Robin, how do you explain Jaime's situation?

When connecting to Internet I work all the time as a limited user.
No problems of any kind here.Every updates and upgrades implemented
smooth.
Real time protection active
Currently last version 615 with last definitions 5737
I can make scannings, but of course for a deep scan do it as ADM .

 

[Robin Walker [MVP]]

Hey Robin, how do you explain Jaime's situation?

Maybe he is running a FAT32 filing system that has no file-system security??

 

[lmb]

While logged in a a power user, have you (or anyone) tried running it
as Administrator. Just right click and select "Run As".

Yes, that works but the user would still get the "Unexpected error -
quitting" message when they log on.

Still same error here too, and both users are ADMINISTRATORS. Everything
worked perfectly ok with version 614, it started the errors after
upgrading to version 615. Can I donwload and install former version
anywhere. I uninstalled MSAS for now till this problem goes away.

LMB
ON Canada

 

[gerick]

OK. Expanation excepted.

Can you tell me what parts of the registry is being
addressed so I can give my "Limited" account access to
that part of the registry.

-----Original Message-----

I understand the thinking that limited users are not in the best
position to do computer scans but shouldn't they at least have the
"Real Time" protection functioning?

Much of the real-time protection and blocking involves reading or writing
parts of the registry that limited-user accounts might not have access to.

Unfortunately, when the precursor of MSAS was written (not by Microsoft)
almost all of the guidelines to developers (on the design of applications to
run in limited-user account status) were flouted. For instance, it stores
its preferences and data in a directory to which limited- user accounts do
not normally have write-access. MSAS Beta 1 is still in this messy state.

--
Robin Walker [MVP Networking]
(e-mail address removed)


.

 

[Robin Walker [MVP]]

Can you tell me what parts of the registry is being
addressed so I can give my "Limited" account access to
that part of the registry.

Huge swathes of it. If you were to give Limited users wider access to the
Registry, then they would not be Limited users any more. If you want wide
access to the Registry, run as an Administrator.

 

[Guest]

Then the product is useless. Uninstall.

-----Original Message-----

Can you tell me what parts of the registry is being
addressed so I can give my "Limited" account access to
that part of the registry.

Huge swathes of it. If you were to give Limited users wider access to the
Registry, then they would not be Limited users any more. If you want wide
access to the Registry, run as an Administrator.

--
Robin Walker [MVP Networking]
(e-mail address removed)


.

 

[Dan]

I'm running XP Pro SP2, in a workgroup, not a domain. I
have multiple logins, all members of the Administrators
group. Only the user who installed the software can use it.

Billions of the zillions of registry entries MSAS uses (the
HKCR\CLSID\* entries are ok) have permissions that allow
the installing user and the System account access to the
registry keys. The Administrators group is NOT granted
access -- which is what causes the other logins to fail
with the uninformative "Unexpected error; quitting" message.

In a fit of anal-retentive pique I manually edited the
registry to grant Administrators Full permission to the
HKCR\Microsoft.AntiSpyware.Trust*,
HKLM\Software\Classes\Microsoft.AntiSpyware.Trust*,
HKCR\gc*, and HKLM\SOFTWARE\Classes\gc* keys. This solved
the problem (though it took me 30+ minutes) -- until I next
upgraded and/or reinstalled.

So this problem is NOT just about Administrator accounts,
it is also about the installer setting inappropriately
restrictive permissions on the registry keys. At the very
least it should be possible to have an installer that gave
permissions to Administrators rather than a single member
of the Administrators group...

You may keep the change from my $0.02 worth.

Dan

 

[LMB]

Thanks!! Your solution actually worked. It was a lot of work (lots of keys
to change) and I was not "allowed" to change the ...Trust* keys. But even
leaving those the way they were, it works again now for my husbands account
(an administrator) and even for my Guest account too!
I certainly hope it doesn't get changed back again with a future update,
because I don't like to have to do that again.