My Windows version was 1909, and PowerShell was downloaded from the Microsoft store, and I opened a PowerShell Window, a PowerShell Window that ran the NPM command, and four PowerShell windows that ssh to, and after connecting successfully, four hours … #9812

Closed
opened 2026-01-31 02:04:29 +00:00 by claunia · 3 comments
Owner

Originally created by @Fcscanf on GitHub (Jul 24, 2020).

My Windows version was 1909, and PowerShell was downloaded from the Microsoft store, and I opened a PowerShell Window, a PowerShell Window that ran the NPM command, and four PowerShell windows that ssh to, and after connecting successfully, four hours later, the PowerShell application window can not be clicked, closed, or typed, and can only be restarted

Originally created by @Fcscanf on GitHub (Jul 24, 2020). My Windows version was 1909, and PowerShell was downloaded from the Microsoft store, and I opened a PowerShell Window, a PowerShell Window that ran the NPM command, and four PowerShell windows that ssh to, and after connecting successfully, four hours later, the PowerShell application window can not be clicked, closed, or typed, and can only be restarted
Author
Owner

@thisVioletHydra commented on GitHub (Jul 24, 2020):

What a dirty headline... ☹

@thisVioletHydra commented on GitHub (Jul 24, 2020): What a dirty headline... ☹
Author
Owner

@zadjii-msft commented on GitHub (Jul 24, 2020):

@Fcscanf could you please fill out the issue template?

# Environment

Windows build number: [run `[Environment]::OSVersion` for powershell, or `ver` for cmd]
Windows Terminal version (if applicable):
Windows Powershell Version:

Any other software?

# Steps to reproduce

A description of how to trigger this bug. List off the exact steps you took to reproduce the issue.

# Expected behavior

A description of what you're expecting, possibly containing screenshots or reference material.

# Actual behavior

What's actually happening?

There are a few other issues on the repo that are similar, but honestly, I can't make heads or tails of that sentence. Are you running this in the Windows Terminal, or a legacy console window?

@zadjii-msft commented on GitHub (Jul 24, 2020): @Fcscanf could you please fill out the issue template? ```md # Environment Windows build number: [run `[Environment]::OSVersion` for powershell, or `ver` for cmd] Windows Terminal version (if applicable): Windows Powershell Version: Any other software? # Steps to reproduce A description of how to trigger this bug. List off the exact steps you took to reproduce the issue. # Expected behavior A description of what you're expecting, possibly containing screenshots or reference material. # Actual behavior What's actually happening? ``` There are a few other issues on the repo that are similar, but honestly, I can't make heads or tails of that sentence. Are you running this in the Windows Terminal, or a legacy console window?
Author
Owner

@ghost commented on GitHub (Jul 28, 2020):

This issue has been automatically marked as stale because it has been marked as requiring author feedback but has not had any activity for 4 days. It will be closed if no further activity occurs within 3 days of this comment.

@ghost commented on GitHub (Jul 28, 2020): This issue has been automatically marked as stale because it has been marked as requiring author feedback but has not had any activity for **4 days**. It will be closed if no further activity occurs **within 3 days of this comment**.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/terminal#9812