When running a batch file for the first time, an Alert
pops up: 'An Unknown Script File Attempting to Run
Requires Approval'.

If you hit 'Allow', the file continues to run, but the
current working directory has been changed
to 'C:\Windows\System32'.

This causes the batch file to execute on files within the
System32 directory and not the original one with
potentially unpredictable results.

After Allowing the batch file the first time, it works as
expected.

I'm running Microsoft Windows XP Professional, Version
2002 with Service Pack 2 and all the critical patches as
of 6-1-05.

I don't expect a follow-up, but wanted to inform the
developers of this issue.

Otherwise, it is a fantastic product with great features.

Thanks for the report. You've described what happens accurately, and this
is indeed a serious bug. It's been reported since early January, and for a
time we had a nice article from the scripting guys at www.microsoft.com to
point to explaining this and other issues.

It should be fixed in beta2, but it is unclear when beta2 will arrive.
--

"G James" <(E-Mail Removed)> wrote in message
news:04d401c566e9$a36add70$(E-Mail Removed)...
> When running a batch file for the first time, an Alert
> pops up: 'An Unknown Script File Attempting to Run
> Requires Approval'.
>
> If you hit 'Allow', the file continues to run, but the
> current working directory has been changed
> to 'C:\Windows\System32'.
>
> This causes the batch file to execute on files within the
> System32 directory and not the original one with
> potentially unpredictable results.
>
> After Allowing the batch file the first time, it works as
> expected.
>
> I'm running Microsoft Windows XP Professional, Version
> 2002 with Service Pack 2 and all the critical patches as
> of 6-1-05.
>
> I don't expect a follow-up, but wanted to inform the
> developers of this issue.
>
> Otherwise, it is a fantastic product with great features.