I can't click, type, or close anything #9917

Closed
opened 2026-01-31 02:07:21 +00:00 by claunia · 6 comments
Owner

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

Environment

Windows build number: [run `[Win]::10 1909` for powershell, or `ver` for cmd]
Windows Terminal version (if applicable):1.2.2022.0

Any other software?
Window Notes

Steps to reproduce

I opened up the Window Notes Tab, and he couldn't type anything, and then I shut him down, and then I opened him up again, and the Window Notes tab was working, and when I copied the tab to Terminal, he stopped moving, and he couldn't type anything, or even shut him down, except from the task manager. I had the same problem last time, but it wasn't triggered by the Window Notes Tab. Instead, I used Terminal to connect to four remote Linux hosts, and after four hours of inactivity, when I tried to use it, I couldn't do it or shut it down. What you are currently experiencing are two remote hosts, three powershells, two of which run the NPM command

Expected behavior

image

Actual behavior

I can't click, type, or close anything

Originally created by @Fcscanf on GitHub (Jul 29, 2020). <!-- 🚨🚨🚨🚨🚨🚨🚨🚨🚨🚨 I ACKNOWLEDGE THE FOLLOWING BEFORE PROCEEDING: 1. If I delete this entire template and go my own path, the core team may close my issue without further explanation or engagement. 2. If I list multiple bugs/concerns in this one issue, the core team may close my issue without further explanation or engagement. 3. If I write an issue that has many duplicates, the core team may close my issue without further explanation or engagement (and without necessarily spending time to find the exact duplicate ID number). 4. If I leave the title incomplete when filing the issue, the core team may close my issue without further explanation or engagement. 5. If I file something completely blank in the body, the core team may close my issue without further explanation or engagement. All good? Then proceed! --> <!-- This bug tracker is monitored by Windows Terminal development team and other technical folks. **Important: When reporting BSODs or security issues, DO NOT attach memory dumps, logs, or traces to Github issues**. Instead, send dumps/traces to secure@microsoft.com, referencing this GitHub issue. If this is an application crash, please also provide a Feedback Hub submission link so we can find your diagnostic data on the backend. Use the category "Apps > Windows Terminal (Preview)" and choose "Share My Feedback" after submission to get the link. Please use this form and describe your issue, concisely but precisely, with as much detail as possible. --> # Environment ```none Windows build number: [run `[Win]::10 1909` for powershell, or `ver` for cmd] Windows Terminal version (if applicable):1.2.2022.0 Any other software? Window Notes ``` # Steps to reproduce I opened up the Window Notes Tab, and he couldn't type anything, and then I shut him down, and then I opened him up again, and the Window Notes tab was working, and when I copied the tab to Terminal, he stopped moving, and he couldn't type anything, or even shut him down, except from the task manager. I had the same problem last time, but it wasn't triggered by the Window Notes Tab. Instead, I used Terminal to connect to four remote Linux hosts, and after four hours of inactivity, when I tried to use it, I couldn't do it or shut it down. What you are currently experiencing are two remote hosts, three powershells, two of which run the NPM command <!-- A description of how to trigger this bug. --> # Expected behavior ![image](https://user-images.githubusercontent.com/27654200/88767802-b802e900-d1ac-11ea-8054-05f612ff8430.png) <!-- A description of what you're expecting, possibly containing screenshots or reference material. --> # Actual behavior I can't click, type, or close anything <!-- What's actually happening? -->
claunia added the Needs-TriageNeeds-Tag-FixNeeds-AttentionProduct-Terminal labels 2026-01-31 02:07:21 +00:00
Author
Owner

@skyline75489 commented on GitHub (Jul 29, 2020):

This issue may be related to #7097 . Out of curiosity, are you using PowerToys?

@skyline75489 commented on GitHub (Jul 29, 2020): This issue may be related to #7097 . Out of curiosity, are you using PowerToys?
Author
Owner

@Fcscanf commented on GitHub (Jul 29, 2020):

Yes,I’m using PowerToys?

@Fcscanf commented on GitHub (Jul 29, 2020): Yes,I’m using PowerToys?
Author
Owner

@skyline75489 commented on GitHub (Jul 29, 2020):

I've actually run into the problem myself and guess what, I'm also having PowerToys running in the background. But it only happened once and I can not reliably reproduce it.

@skyline75489 commented on GitHub (Jul 29, 2020): I've actually run into the problem myself and guess what, I'm also having PowerToys running in the background. But it only happened once and I can not reliably reproduce it.
Author
Owner

@Fcscanf commented on GitHub (Jul 29, 2020):

Yes, my PowerToys is running, I rebooted the Terminal, and I'll try to shut it down next time, but, even though the problem is random and occasional, the solution is to restart the other one, there's enough tolerance for this kind of problem

@Fcscanf commented on GitHub (Jul 29, 2020): Yes, my PowerToys is running, I rebooted the Terminal, and I'll try to shut it down next time, but, even though the problem is random and occasional, the solution is to restart the other one, there's enough tolerance for this kind of problem
Author
Owner

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

Could you take a look at #6120? From that thread:

  • Are you using the Terminal on a high DPI display?
    • If so, and if possible, does dragging the window to a 100% scaling display magically restore mouse functionality to the Terminal?
  • Similarly, are you using the Terminal on your primary display?
    • If so, and if possible, does dragging the window to another display magically restore mouse functionality to the Terminal?
  • Does the PowerToys settings app similarly not respond to mouse input?
  • Do you have the Shortcut Guide enabled in PowerToys?
    • If so, does it actually work if you long press Win?
  • By any chance, did you recently uninstall any sort of IME (like a Chinese/Japanese/Korean language IME)?

If you're experiencing this, and you can interact with the PowerToys settings app (you might need to drag it to another monitor), then

  • can you fix the issue by disabling "Shortcut Guide" in PowerToys?
@zadjii-msft commented on GitHub (Jul 29, 2020): Could you take a look at #6120? From that thread: * Are you using the Terminal on a high DPI display? - If so, and if possible, does dragging the window to a 100% scaling display magically restore mouse functionality to the Terminal? * Similarly, are you using the Terminal on your primary display? - If so, and if possible, does dragging the window to another display magically restore mouse functionality to the Terminal? * Does the PowerToys settings app similarly not respond to mouse input? * Do you have the Shortcut Guide enabled in PowerToys? - If so, does it actually work if you long press <kbd>Win</kbd>? * By any chance, did you recently uninstall any sort of IME (like a Chinese/Japanese/Korean language IME)? If you're experiencing this, and you can interact with the PowerToys settings app (you might need to drag it to another monitor), then * can you fix the issue by disabling "Shortcut Guide" in PowerToys?
Author
Owner

@Fcscanf commented on GitHub (Jul 30, 2020):

@zadjii-msft ,yes,I'm using the Terminal on a high DPI display,I'm not as bad as # 6120, just occasionally, just restart the Terminal, thank you

@Fcscanf commented on GitHub (Jul 30, 2020): @zadjii-msft ,yes,I'm using the Terminal on a high DPI display,I'm not as bad as # 6120, just occasionally, just restart the Terminal, thank you
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/terminal#9917