Don't run MSAS at startup

[CLM]

I need to turn off MSAS so it will not run start up when
Windows starts - I couldn't find a way to do it
gracefully. I could take it of the startup manually but
I want to put it back in later. Am I missing something
or is there not a graceful way to do this?

On another note, I've had great luck with MSAS.

Thanks,
CLM

 

[Bill Sanderson]

You can't do this with the System Explorers, startup programs in Microsoft
Antispyware, because it won't let you. It seems like the perfect place, but
in fact, it is too smart for us and doesn't allow the action.

I would recommend msconfig. Start, run, msconfig <enter>
Click on the startup tab, and uncheck the box next to gcasServ
When you restart, you will need to check an additional box to request that
msconfig not alert you to the disabled startup item at each startup.

You can switch back by simply reversing that action.

 

[Michael Jennings]

With the Security Agents Status screen indicating
that all agents were inactive but with
Options | Settings | Real-time screen allowing "ask me"
for the script blocking security agent options,
that agent is loaded at startup. We say, you don't say
seems to be the way it's set up. Perhaps that's best for
the intended users - not usually unaflicted beta testers.

 

[Bill Sanderson]

That's wierd--it doesn't look that way on my machine--and all the ones I've
looked at--everything is consistent.

 

[Michael Jennings]

wierd an aflicted mebbe - weer speling chalenged iguess.
U could give it a whirl - disable all but prompt script sniff.
Then run a new bat file and see it stopped.

 

[Bill Sanderson]

I've tried disabling and enabling--both at the agent level, and at the
individual checkpoint level, and I've been able to both disable and enable
on my machine.

I'm not totally sure just what you want me to test, though--want to try that
again?

 

[Michael Jennings]

click on the real-time shield. Disable the agents. Now each of
the three groups is marked "In-active" in red. click on the
Options menu item, then on Settings (the only selection). Select
Real-time Protection on the left. Clear Startup options and
Real-time spyware threat detection. Under Script-Blocking
Security Agent options leave the mark in "Ask me what to do
(recommended)". Script blocking is one of the disabled
application agents and you just said, "don't load on startup,"
so it ought to be double dead, but it's ready and waiting,
before or after a reboot. Here's a bat file:

@echo off
title dosbox
cd \
cmd /k color 1a

It's harmless. Paste it in notepad and save as type All Files,
giving it the batch file .bat extension. Mine is named
"dosbox.bat" - double click it to see it stopped. If you allow
it, you'll need to rename it to somethingelse.bat to see it
stopped again - unchecking "remember" doesn't work.

I don't want you to test this unless you don't believe it.

message

 

[Bill Sanderson]

I believe you--but lets see whether this is different from one system to
another.

 

[Bill Sanderson]

I can confirm your findings. There are at least two juicy bugs here. 1)
the program is not honoring the settings in the UI--at least some real-time
protection is still there even with everything marked as inactive, and a
restart. 2) on the script-blocking, if I allow the operation but uncheck the
box to remember the action, I should get challenged again when I re-run the
script with the same name. Didn't happen. It remembered the action.

I think these issues in general (program not taking action based on the
users choices in the UI) have been well documented here. I'll try to
reinforce that feedback, though.

 

[Michael Jennings]

Yes. Clearing "Run at startup" is as ineffective as clearing
"remember this." Thanks for checking that out, Bill.

"Bill Sanderson" <[email protected]>
wrote in message
news:%[email protected]...

 

[Bill Sanderson]

I'm sure this stuff'll be fixed, but it is definitely not the behavior you
expect from the UI presented, and that's really annoying!