[BUG] AntiSpyware Scheduled Scan and Fast User Switching

  • Thread starter Thread starter Brian Hartvigsen
  • Start date Start date
B

Brian Hartvigsen

I noticed today that scheduled scans scan as all logged on users instead
of System or some other privelleged user.

I had scanning processes for 3 differant users going.. And let me tell
you that tied up quite a bit of processing power/memory. Not only that,
but 2 of the users did not even have Administrative privileges so it
wouldn't have been able to fix much.

Why don't scheduled scans run as System instead of logged on users?
Would avoid this.

-- Brian
 
I noticed today that scheduled scans scan as all logged on users instead of
System or some other privelleged user.

I had scanning processes for 3 differant users going.. And let me tell
you that tied up quite a bit of processing power/memory. Not only that,
but 2 of the users did not even have Administrative privileges so it
wouldn't have been able to fix much.

Why don't scheduled scans run as System instead of logged on users? Would
avoid this.

-- Brian
Click to expand...


It's a security matter and needs a lot of consideration - however this
problem has been reported already and MSAS Team works on it, I think.
 
Yes--Microsoft Antispyware is running as a user process, and not as a
service--which would allow it to run in a security context different from
the current user. I would expect this to change in beta2, but we haven't
seen beta2!
 
Mikolaj said:
It's a security matter and needs a lot of consideration - however this
problem has been reported already and MSAS Team works on it, I think.
Click to expand...

I was sure it probably had, but wading through over 5000 headers [before
my eyes started to pop out of my head] in this group alone and a quick
search which didn't turn up anything, I figured it was worth posting.

Thanks for the heads up, I'll wait for beta2 like everyone else ;)

-- Brian
 
Back
Top