84

Periodically I notice PowerShell seems to take forever to finish doing whatever it is I told it to do until it occurs to me to "wake it up" by pressing enter. This is not the fault of any one process as best I can tell, as I have even run custom apps that just log their output to the screen every few seconds and even in these cases, PowerShell will stop doing anything after a while until I "give it a kick" by pressing enter.

Any ideas what might be causing this?

123
+50

If the QuickEdit Mode and\or Insert options are checked within the console\window properties, and you click within the console, it will pause the output. If those options are not checked, the output can't be paused by clicking within the console.

alt text

  • 5
    Ah, yes, it never occurred to me that clicking the screen could interrupt the output. After running some tests, this indeed seems to be the issue. – Nathan Ridley Nov 25 '10 at 14:37
  • 5
    OMG Shell fail. – meawoppl Nov 24 '14 at 20:41
  • 10
    That is extremely annoying :) Another undocumented feature? – user274326 Mar 3 '15 at 23:44
  • 4
    literally joined server fault to upvote, been years since i observed it first time, but it never became problem big enough to look into, until today i stepped on this 'rake' again :) – drk Aug 14 '15 at 13:16
  • 6
    Like drk, I joined this site to upvote :D. This solved one of the most annoying mysteries in my life lol. – Jan Apr 7 '17 at 12:09
0

If you are running PowerShell script from within Cygwin like so:

powershell.exe -Command '<...>'

and you get this problem, you can fix it by piping in a newline:

echo | powershell.exe -Command '<...>'

Your Answer

By clicking "Post Your Answer", you acknowledge that you have read our updated terms of service, privacy policy and cookie policy, and that your continued use of the website is subject to these policies.

Not the answer you're looking for? Browse other questions tagged or ask your own question.