Antispyware Beta 2 does not execute batchfiles correctly

[Markus]

Hello,

i don't know where to put bugreports for antispyware, so
here it is:
when antispyware blocks .bat or .cmd-files for the first
time to ask what to do with the file, the script is
executed but does not work correctly.
for example, when a program should be started from
the .bat or .cmd-file, the program is NOT started,
although the script itself is called. maybe there's a
problem with the working directory of the script or
environment variables.
one example is starting the oracle 9i worksheet
(C:\oracle\ora92\bin\oemapp.bat).
After adding the script to the allowed list, the next
time it is executed everything works fine.

 

[Andre Da Costa]

This is not beta 2, its beta 1, it has already been reported that MSAS Beta
1 has issues with scripts being blocked. The next beta of MSAS should
resolve this.
--
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

 

[Bill Sanderson]

You are quite right. This can be a dangerous bug.

When a script or batch file is first executed--i.e. when you get the prompt
allowing you to block or allow it--the script executes in the %system32%
context, rather than the location of the script file.

If the script is not written carefully, this will have unexpected results.

I haven't tested this issue with build .614, but I haven't heard that it is
fixed, so I wouldn't expect that.