Windows 8.1. This has been an issue for me on multiple computers including Windows 7 and Server 2008 R2. At various stages, for no discernable reason, PowerShell will just stop what it's doing until I press a key to wake it up. Here is 1 example:
Yesterday I ran a command and forgot about it; left it running:
ping -t 10.1.7.10
Pretty basic, right? As I said, I forgot about it. At the end of the day I locked my computer and went home. I came in this morning, and here is all that I have in my PowerShell window:
PS U:\> ping -t 10.1.7.10 Pinging 10.1.7.10 with 32 bytes of data: Request timed out.
There was only 1 ping attempt! If you are not familiar with ping, the -t switch tells it to send a never-ending stream of ICMP packets until I tell it to stop.
As soon as I highlighted the text and pressed Enter to copy it to the clipboard for this post, the ping command picked up right where it left off; it resumed pinging and showing me the results. I already have a full page of "Request timed out."
What gives? Am I doing something to interrupt PowerShell without realizing it?