New version uploaded. It searches Program Files, Program Files (x86), and bin (the latter being a good place to put installs of additional versions, especially if you use the "portable" feature, since Modern Windows won't like an application trying to write to the normal system app directories.

You wouldn't believe how many strange errors pop up when path names contain parenthesis! The windows commands scanner is text-based, and apparently if you have a code block (delimited by parens!), and it includes an expansion of a path variable (containing parens), you start getting mysterious errors about "xxx unexpected here", even though things appear to be working.

The solution to the other "early evaluation" problems is to have the "late evaluation" instantiation of the script write out a temporary .bat file, which the "early eval" instantiation then "calls"... Gross!