BUG: Script blocking strips script parameters during script authorization

[Jonathan K. Shay]

The first time a VBS script is run, MSAS correctly blocks
the script and prompts the user for action (allow,
etc.). However, if the script is allowed to execute, no
parameters that were passed with the script ON THE
INITIAL EXECUTION are passed through the "authorization
filter". That is to say, once a user accepts script
authorization, any parameters passed with the script have
been dropped.

It appears this only happens the first time a script is
caught by MSAS. Subsequent script executions correctly
run with parameters passed to the script.

 

[Bill Sanderson]

Additionally, the script executes in the folder context of \system32, rather
than the script file's location.

 

[Jonathan K. Shay]

Indeed it does - I thought my errors were exclusively the
result of parameters being dropped, but now that I look
closely my script's working folder has been changed to
the \System32 folder...

BTW, is this the correct location to post bugs, or is
there a forum exclusively for that??

 

[Bill Sanderson]

These groups are the correct location. There's a school of thought that
nobody should post in or answer in, the announcements group, but it hasn't
gained many adherents yet.

You may find a given group more appropriate for a given post--false
positives are requested in .signatures, for example.

There was for a time a useful article written by "the scripting guys" about
the foibles of the beta and scripting. It disappeared without a trace one
day, unfortunately.

I expect these bugs, which are definitely high on the developers lists, to
be fixed in beta2, and I also expect beta2 to be released..... but when??