Non-Admin user?

[rox.scott]

Why am I not getting updates or scans as per schedule?
Is it because I am not running as an Admin user?

Last Scan: 9 days ago
Definitions: 14 days ago
Scan Schedule: Runs at 2:00 AM every day
AutoUpdater: Active
- in updater options, "Daily" is selected, but no time
selected, and both notifications are checked ON

(using Microsoft AntiSpyware Version: 1.0.501)

 

[Monitor]

Select the time

 

[Andre Da Costa]

To get updates you must be logged on to the machine as an Administrator.
Also update your build from .501 to .509.
http://download.microsoft.com/downl...-fca2f2c6f0cc/MicrosoftAntiSpywareInstall.exe

 

[rox.scott]

So there is no service I can run as Admin or something
like that? I actually have to log on as an Admin to get
updates? Doesn't that defeat proper security procedure
for PC usage?

--scott

 

[Andre Da Costa]

No, Microsoft AntiSpyware does not run as a service, only as a process.
Would be nice if it could run as a Service though.

 

[Jacques]

Is there anyone who tried "run as" from a limited account (and with spyware
in order to see what's appening).

 

[Bill Sanderson]

Neither I nor Microsoft disagrees with you about this. Let's see how it
changes with further beta versions.

 

[Bill Sanderson]

If you are asking did they test this car before they let it out of the
factory, the answer is yes, they did.

They purchased the technology from a third party--I think in the first week
in January. They released the first build of this beta about 3 weeks later.

They are quite aware of the shortcomings that we are all seeing. Some of
these will require substantial work to fix--and this area of limited users
versus administrators is one.

 

[Jacques]

Have you any idea about risks for my computer if I use this feature for my
wife's account?

 

[Andre Da Costa]

Here's the reason for shortcoming on Limited Accounts by Steve Dodson:
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.

 

[Bill Sanderson]

I think that the risks are mainly of having popups from the program that
don't indicate real problems, and which may be confusing (in fact, the
program may be confused!) I don't think this is an issue which might
involve data loss, nor do I think that the real-time protection is weaker.

I'd try it out, but keep an eye out for issues--I don't have a clear picture
of this situation. My machine gets shared very seldom, as you can see from
my posting times. I often work via remote desktop, so I am not sitting in
front of it, but it get's used periodically all day.

 

[rox.scott]

I tried RunAs from the shortcut, and also tried to
execute GIANTAntiSpywareMain.exe from an Admin dos prompt.
In both cases, I get 101 error:
"Warning, MSAS has encountered a critical error (Error
101). Please restart ..."

--scott