Why powershell runs executables in separate window?

Posted by Artem Tikhomirov on Server Fault See other posts from Server Fault or by Artem Tikhomirov
Published on 2012-06-25T16:15:04Z Indexed on 2012/07/05 15:17 UTC
Read the original article Hit count: 356

Filed under:
|

On one of my servers (2008 R2) powershell refuses to run executables without extension, so typing cmd (or &cmd) in command prompt results in folowing error message:

The term 'cmd' is not recognized as the name of a cmdlet

Invoking executable one of the following ways pops out separate window (which executes asynchronously in respect to parent). I've tried that in x86 version of powershell and in x64 one. I've tried -Noprofile argument. PATH seems to be OK. It includes System32 and all.

The only way I've managed to execute cmd inline form powershell is opening standard cmd.exe shell, executing powershell.exe from it and executing cmd /c echo test from it. Inception, huh?

What should I try next?

© Server Fault or respective owner

Related posts about powershell

Related posts about cmd