PowerShell for Windows

Re: Should PS be able to run a VBscript this simply?

Archdeacon — Wed, 14 Dec 2011 04:38:27 GMT

The problem has been solved by removing the .VBS tag from the $env:PathExt collection.

Re: Should PS be able to run a VBscript this simply?

Tobias — Thu, 08 Dec 2011 22:45:53 GMT

If you do not move your VBScripts, and if they have colliding names, then the same problem exists in a regular cmd session as well. I would move the VBScripts to some private folder.

Re: Should PS be able to run a VBscript this simply?

RSiddaway — Mon, 05 Dec 2011 13:54:02 GMT

If you don't need VBScript you could disable the file association. Also if you can run them by just using the script name it suggests that

cscript //H:CScript

has been run to make the command line the default

if you run

cscript //H:WScript

the defaults are reset which means you will use the graphical interface which will slow things down

best thing is to get theose scripts off the execution path

Re: Should PS be able to run a VBscript this simply?

Archdeacon — Mon, 05 Dec 2011 12:27:34 GMT

I see, but this runs by just typing 'default' (without the quotes). I have a bunch of VBS scripts with PS accessible names, like format, args, param (all .vbs) so these will be triggered if I do not move them. Seems very risky to me! Thanks, anyway.

Re: Should PS be able to run a VBscript this simply?

Tobias — Mon, 05 Dec 2011 09:14:14 GMT

PS can only launch files this simple when they are placed in one of the folders listed in $env:path. In all other places, a relative or absolute path name is required, i.e.

.\default.vbs

Should PS be able to run a VBscript this simply?

Archdeacon — Mon, 05 Dec 2011 08:23:07 GMT

How do I prevent PowerShell from running a named vbs Script? For example, I have a script
called 'Default.vbs', admittedly in the current $pwd directory, so that whenever I type 'default' in the PS console that script runs. Is there a way to stop this, as a simple 'typo' can act as a trigger?