MSAS Wont remember allowed script

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

Hi, I have just updated to the newest version of MSAS, and whenevr I try to
launch a specific program (dos based) the MSAS warns that a script (.pif) is
trying to run, and asks if i want to allow it.
This same thing occured when I first installed MSAS months ago, and I
allowed the script and everything was fine.

Now when I choose to allow the script, the warnin pops up again, and my
(DOS) program will not run.
It is as thought MSAS doesn't want me to allow the script to run.
A workaround is to disable MSAS, Launch my program, then enable MSAS, but
this seems a little useless.
Any help would be appreciated,
 
Right click on the Microsoft AntiSpyware bulls eye in the notification area
and click Shutdown Microsoft AntiSpyware, then run the script. Hopefully
this will fixed in BETA 2.

Tip from Andy:

Run all the batch files once on your system and
choose "Allow" on the MSAS notice and check the
box "Remember This Action" for each .If these batch files
run again then it will not block them.
--
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
 
Thank you for your responce.
In reply to your first point; this is exactly what I have been doing as a
workaround.

I reply to your second point;MSAS will not accept me allowing the bat file
scripts to run. Even if I check the box marked "remember this action" and
select Allow. The pop-up (warning me about the script)will not stop popping
up.
 
Hi Gavin;

It's sort of a usability issue actually with Beta1. Open MSAS Manage
Allowed/Blocked Scripts first and leave it open while your attempting to allow
(or block) script execution. I think you'll see how it works more clearly if
this panel is open while you attempt to run the script. It's hard to describe
it's function otherwise. Maybe Beta2 will be more user friendly?
 
It is feeling more like a us(eless)ability issue. MSAS will not let me allow
the script. I opened the MSAS Manage Allow/Blocked Scripts first and all it
did was show me that I "decided to allow the script....". Alas, it didn't
allow the script. I have the "decided to allow.." message literally hundreds
of times, because it doesn't believe me and constantly asks me if i want to
allow.
I sincerely hope Beta2 is not only more friendly but actually works properly.

gavin
 
Gavin;
Are you attempting to run that script on a Limited user account or even an Admin
authority account that was not the original account from which MSAS was
installed? If so, try allowing it from the original installing account. This
forum is full of threads saying MSAS Beta1 was never designed to run in a
multi-user environment. The code is being re-written for release as Windows®
Defender and we expect multi-user installations to behave much differently
there.

If that's not the case, then something else has gone wrong in your new
installation... It sure works here, and nothing has changed in the MSAS code
except the expiration date since the prior release, so it has to be something
you are doing differently this time or a bad installation.
 
Back
Top