The first 2 commands give the identical results as your example.

You sure?

The only thing I am aware of that could be affecting this, is if the ftype were set wrong. For example, if the ftype were set as:

Perl="c:\perl64\bin\perl.exe" "%1"
[download]

That would disable the passing of arguments:

C:\test>type argtest.pl
#! perl -slw
use strict;

print for @ARGV;


C:\test>ftype Perl
Perl="c:\perl64\bin\perl.exe" "%1"

C:\test>argtest 1 2 3 4 5           ### NOTE ### no args printed becau
+se %* is missing above.

C:\test>ftype Perl="c:\perl64\bin\perl.exe" "%1" %*
Perl="c:\perl64\bin\perl.exe" "%1" %*

C:\test>argtest 1 2 3 4 5           ### NOTE ### Now it works.
1
2
3
4
5
[download]