Super User is a question and answer site for computer enthusiasts and power users. It's 100% free, no registration required.

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

Sometimes my PowerShell stops executing programs and I have yet to find out why. In this state, when I enter the name of an EXE file, the PowerShell immediately returns to a command prompt without executing anything. Cmdlets however appear to still work. There is also no error shown in the Windows event viewer or anywhere else I have looked.

I don't know how this state is triggered (I was developing a PS1 script the last time it happened), how I prevent it from happening, and how I can return to a working state without restarting my PowerShell.

Any ideas?

share|improve this question
I'm having this exact same problem - if you find a solution, please do come back and answer your own question! – mavnn Sep 19 '12 at 16:27
Unfortunately I didn't. It happened to me a lot more when developing a script but only rarely during "normal" use, so I stopped caring. Everything I knew about the problem I posted into this thread:… – fschoenm Sep 19 '12 at 20:12
Thanks for coming back. We're getting bitten by it in TeamCity build steps, which is a bit of a pain - but very rarely when actually running scripts in the console. It's concerning though, as a lot of our infrastructure deployment relies on Powershell... – mavnn Sep 20 '12 at 9:55
I have this problem a lot, too. In my case, it seems to be related to starting a Python process. Mercurial causes it to happen very rarely, but running our waf build seems to make it happen after 10 or 15 times. – moswald Feb 15 '13 at 16:04

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Browse other questions tagged or ask your own question.