starred/terminal
1
0
Fork 0
mirror of https://github.com/microsoft/terminal.git synced 2026-02-04 05:35:20 +00:00
Code Issues 19.0k Packages Projects Releases 20 Wiki Activity

Windows Terminal: Loss of Mouse Interactivity (PowerToys) #8471

New Issue
Closed
opened 2026-01-31 01:30:14 +00:00 by claunia · 38 comments
claunia commented 2026-01-31 01:30:14 +00:00
Owner
Copy Link

Originally created by @hectormz on GitHub (May 22, 2020).

Environment

Windows build number: [Version 10.0.19041.264]
Windows Terminal version (if applicable): 1.0.1401.0

Any other software?

Steps to reproduce

This seems to happen when I leave Windows Terminal running long enough. I haven't been able to nail down the exact situation that leads to it happening. I started noticing this recently, which may be due to a new problem, or just more use of Windows Terminal.

I'm certain that leading up to the unresponsiveness, my machine has been locked and/or asleep at some point. But I have put my computer asleep, or locked it without reproducing the problem.

Expected behavior

Normal mouse interactivity.

Actual behavior

At least once a day now, my Windows Terminal become unresponsive to mouse interactions. This includes selecting text, pasting text with right click, clicking tabs and dropdown menu, minimize/maximizing the window etc. The only mouse interaction that works is grabbing the title bar and moving the window.

I am seeing this behavior with Windows Terminal, but I have a feeling it might be UWP related. I don't (knowingly) use many UWPs, but when the Windows Terminal is like this, I've tested the Microsoft Store application as well. I'm able to minimize/maximize Microsoft Store, but cannot drag it around via the title bar. When Windows Terminal is behaving properly, the Microsoft Store is fine.

When Windows Terminal has been misbehaving, I've opened Windows Terminal (Preview), and it was acting similarly unresponsive.

This issue is not resolved by closing and reopening Windows Terminal. I have to restart my computer to fix it.

If I can provide any more info, or narrow down what leads to this happening, I'll report back.

Originally created by @hectormz on GitHub (May 22, 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: [Version 10.0.19041.264] Windows Terminal version (if applicable): 1.0.1401.0 Any other software? ``` # Steps to reproduce <!-- A description of how to trigger this bug. --> This seems to happen when I leave Windows Terminal running long enough. I haven't been able to nail down the exact situation that leads to it happening. I started noticing this recently, which may be due to a new problem, or just more use of Windows Terminal. I'm certain that leading up to the unresponsiveness, my machine has been locked and/or asleep at some point. But I have put my computer asleep, or locked it without reproducing the problem. # Expected behavior <!-- A description of what you're expecting, possibly containing screenshots or reference material. --> Normal mouse interactivity. # Actual behavior <!-- What's actually happening? --> At least once a day now, my Windows Terminal become unresponsive to mouse interactions. This includes selecting text, pasting text with right click, clicking tabs and dropdown menu, minimize/maximizing the window etc. The only mouse interaction that works is grabbing the title bar and moving the window. I am seeing this behavior with Windows Terminal, but I have a feeling it might be UWP related. I don't (knowingly) use many UWPs, but when the Windows Terminal is like this, I've tested the Microsoft Store application as well. I'm able to minimize/maximize Microsoft Store, but cannot drag it around via the title bar. When Windows Terminal is behaving properly, the Microsoft Store is fine. When Windows Terminal has been misbehaving, I've opened Windows Terminal (Preview), and it was acting similarly unresponsive. This issue is not resolved by closing and reopening Windows Terminal. I have to restart my computer to fix it. If I can provide any more info, or narrow down what leads to this happening, I'll report back.
claunia commented 2026-01-31 01:30:15 +00:00
Author
Owner
Copy Link

@DHowett commented on GitHub (May 22, 2020):

Do you have PowerToys installed?

@DHowett commented on GitHub (May 22, 2020): Do you have PowerToys installed?
claunia commented 2026-01-31 01:30:15 +00:00
Author
Owner
Copy Link

@DHowett commented on GitHub (May 22, 2020):

(This could be a XAML platform bug -- that's the only thing in common between that set of applications. Hmm.)

@DHowett commented on GitHub (May 22, 2020): (This could be a XAML platform bug -- that's the only thing in common between that set of applications. _Hmm._)
claunia commented 2026-01-31 01:30:16 +00:00
Author
Owner
Copy Link

@hectormz commented on GitHub (May 22, 2020):

@DHowett Yes, I updated to PowerToys v0.18.0 this week. Before that, I was several versions behind (v0.13.0).

Do you think that's involved? Would closing PowerToys when this issue happens fix it?

@hectormz commented on GitHub (May 22, 2020): @DHowett Yes, I updated to PowerToys `v0.18.0` this week. Before that, I was several versions behind (`v0.13.0`). Do you think that's involved? Would closing PowerToys when this issue happens fix it?
claunia commented 2026-01-31 01:30:16 +00:00
Author
Owner
Copy Link

@DHowett commented on GitHub (May 22, 2020):

It's worth a shot!

@DHowett commented on GitHub (May 22, 2020): It's worth a shot!
claunia commented 2026-01-31 01:30:17 +00:00
Author
Owner
Copy Link

@hectormz commented on GitHub (May 22, 2020):

I'll report back.

You made me wonder if this could be caused by FancyZones use, but that didn't cause any issues yet.

@hectormz commented on GitHub (May 22, 2020): I'll report back. You made me wonder if this could be caused by FancyZones use, but that didn't cause any issues yet.
claunia commented 2026-01-31 01:30:17 +00:00
Author
Owner
Copy Link

@softwarenerd commented on GitHub (May 22, 2020):

I am experiencing this, too. It's random and happens when Windows Terminal has been running for a little while. I always have two Windows PoweShell tabs open There are no steps to reproduce this other than to start Windows Terminal and open two Windows PoweShell tabs.

Windows Terminal
Version: 1.0.1401.0

@softwarenerd commented on GitHub (May 22, 2020): I am experiencing this, too. It's random and happens when Windows Terminal has been running for a little while. I always have two Windows PoweShell tabs open There are no steps to reproduce this other than to start Windows Terminal and open two Windows PoweShell tabs. Windows Terminal Version: 1.0.1401.0
claunia commented 2026-01-31 01:30:18 +00:00
Author
Owner
Copy Link

@Domain commented on GitHub (May 22, 2020):

I have the same issue. And when I exit PowerToys, it works fine now.

@Domain commented on GitHub (May 22, 2020): I have the same issue. And when I exit PowerToys, it works fine now.
claunia commented 2026-01-31 01:30:18 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (May 22, 2020):

@softwarenerd do you have powertoys installed as well?

@crutkas We're still seeing some intermittent mouse issues with the Terminal and PowerToys, even on updated versions of PowerToys, anything we can do to get logging from these users to debug?

@zadjii-msft commented on GitHub (May 22, 2020): @softwarenerd do you have powertoys installed as well? @crutkas We're still seeing some intermittent mouse issues with the Terminal and PowerToys, even on updated versions of PowerToys, anything we can do to get logging from these users to debug?
claunia commented 2026-01-31 01:30:19 +00:00
Author
Owner
Copy Link

@softwarenerd commented on GitHub (May 22, 2020):

@crutkas I don't have PowerToys installed.

@softwarenerd commented on GitHub (May 22, 2020): @crutkas I don't have PowerToys installed.
claunia commented 2026-01-31 01:30:19 +00:00
Author
Owner
Copy Link

@hectormz commented on GitHub (May 23, 2020):

@zadjii-msft @crutkas @DHowett

This morning I lost mouse function again.

Closing PowerToys did the trick. I closed it and all was fine again. I opened PowerToys again and it's still fine.

I also updated to v.0.18.1 some time before this happened.

@hectormz commented on GitHub (May 23, 2020): @zadjii-msft @crutkas @DHowett This morning I lost mouse function again. Closing PowerToys did the trick. I closed it and all was fine again. I opened PowerToys again and it's still fine. I also updated to v.0.18.1 some time before this happened.
claunia commented 2026-01-31 01:30:20 +00:00
Author
Owner
Copy Link

@crutkas commented on GitHub (May 23, 2020):

@hectormz. Did you drag the window with fancyzones at any time before?

@crutkas commented on GitHub (May 23, 2020): @hectormz. Did you drag the window with fancyzones at any time before?
claunia commented 2026-01-31 01:30:20 +00:00
Author
Owner
Copy Link

@hectormz commented on GitHub (May 23, 2020):

@crutkas I did drag other windows into FancyZones last night, but not Terminal.

Last night everything was okay, and computer was asleep over night. Some time after waking the computer today and doing work, I noticed Terminal not responding again.

@hectormz commented on GitHub (May 23, 2020): @crutkas I did drag other windows into FancyZones last night, but not Terminal. Last night everything was okay, and computer was asleep over night. Some time after waking the computer today and doing work, I noticed Terminal not responding again.
claunia commented 2026-01-31 01:30:20 +00:00
Author
Owner
Copy Link

@muzzar78 commented on GitHub (May 25, 2020):

I have experienced the same issue and it occurred when I unlocked my laptop from sleep. I had two tabs open and I don't have powertoys installed. If I right click close from the taskbar, I get close tabs dialogue but it is unresponsive too. This has happened several times over the last month (both prior to v1 and now on v1).

image

Killing the windowsterminal process and relaunching resolves the issue.

@muzzar78 commented on GitHub (May 25, 2020): I have experienced the same issue and it occurred when I unlocked my laptop from sleep. I had two tabs open and I don't have powertoys installed. If I right click close from the taskbar, I get close tabs dialogue but it is unresponsive too. This has happened several times over the last month (both prior to v1 and now on v1). ![image](https://user-images.githubusercontent.com/13233154/82773450-6fb20c80-9e85-11ea-951b-953f7f18aaa6.png) Killing the windowsterminal process and relaunching resolves the issue.
claunia commented 2026-01-31 01:30:20 +00:00
Author
Owner
Copy Link

@crutkas commented on GitHub (May 25, 2020):

@muzzar78 do you have PowerToys installed?

@crutkas commented on GitHub (May 25, 2020): @muzzar78 do you have PowerToys installed?
claunia commented 2026-01-31 01:30:20 +00:00
Author
Owner
Copy Link

@muzzar78 commented on GitHub (May 25, 2020):

@muzzar78 do you have PowerToys installed?

No, I don't.

@muzzar78 commented on GitHub (May 25, 2020): > @muzzar78 do you have PowerToys installed? No, I don't.
claunia commented 2026-01-31 01:30:21 +00:00
Author
Owner
Copy Link

@SergioMorchon commented on GitHub (May 26, 2020):

I also don't have Power Toys installed, and experience the same issue.
Also to close it, even if I right-click on the task bar icon with the mouse, anc select "Close", the terminal shows the dialog (that warns about having multiple tabs that will be closed) but if I click over the dialog buttons, it just do nothing.
I have to close it from the Windows task manager

@SergioMorchon commented on GitHub (May 26, 2020): I also don't have Power Toys installed, and experience the same issue. Also to close it, even if I right-click on the task bar icon with the mouse, anc select "Close", the terminal shows the dialog (that warns about having multiple tabs that will be closed) but if I click over the dialog buttons, it just do nothing. I have to close it from the Windows task manager
claunia commented 2026-01-31 01:30:21 +00:00
Author
Owner
Copy Link

@ihor-sviziev commented on GitHub (May 26, 2020):

I also getting issue with dialog on Ubuntu 20.04 WSL2 with following command:

HEIGHT=0
WIDTH=0
dialog \
    --backtitle "System Information" \
    --title "Menu" \
    --clear \
    --cancel-label "Exit" \
    --menu "Please select:" $HEIGHT $WIDTH 4 \
    "1" "Display System Information" \
    "2" "Display Disk Space" \
    "3" "Display Home Space Utilization"

It just stops reacting on mouse clicks just after few clicks to different options. Also I hadn't this issue on Terminal Preview versions.
Windows Terminal Version: 1.0.1401.0
Windows Version 2004 (OS Build 19041.264)

@ihor-sviziev commented on GitHub (May 26, 2020): I also getting issue with dialog on Ubuntu 20.04 WSL2 with following command: ```bash HEIGHT=0 WIDTH=0 dialog \ --backtitle "System Information" \ --title "Menu" \ --clear \ --cancel-label "Exit" \ --menu "Please select:" $HEIGHT $WIDTH 4 \ "1" "Display System Information" \ "2" "Display Disk Space" \ "3" "Display Home Space Utilization" ``` It just stops reacting on mouse clicks just after few clicks to different options. Also I hadn't this issue on Terminal Preview versions. Windows Terminal Version: 1.0.1401.0 Windows Version 2004 (OS Build 19041.264)
claunia commented 2026-01-31 01:30:21 +00:00
Author
Owner
Copy Link

@arntj commented on GitHub (May 27, 2020):

I'm having the same issue. When it happens, it persists when I close and re-open Terminal. But if I shut down Powertools, then it disappears.

I also noticed that if I run Terminal as administrator while PowerTools is running then I get this notification:
image

@arntj commented on GitHub (May 27, 2020): I'm having the same issue. When it happens, it persists when I close and re-open Terminal. But if I shut down Powertools, then it disappears. I also noticed that if I run Terminal as administrator while PowerTools is running then I get this notification: ![image](https://user-images.githubusercontent.com/7281836/83039484-88195700-a03e-11ea-9eec-3387023a719d.png)
claunia commented 2026-01-31 01:30:21 +00:00
Author
Owner
Copy Link

@transiient commented on GitHub (May 27, 2020):

I have the same issue. Exiting PowerToys restores functionality - Terminal doesn't even need to be restarted after PowerToys is exited.

@transiient commented on GitHub (May 27, 2020): I have the same issue. Exiting PowerToys restores functionality - Terminal doesn't even need to be restarted after PowerToys is exited.
claunia commented 2026-01-31 01:30:22 +00:00
Author
Owner
Copy Link

@leandrowilliam commented on GitHub (May 28, 2020):

I have the same issue... But when I close PowerToys it run good again without restarting the Terminal. The issued started with the v0.18.1 of powerToys, that ask to intall/update the netFramework too

@leandrowilliam commented on GitHub (May 28, 2020): I have the same issue... But when I close PowerToys it run good again without restarting the Terminal. The issued started with the _v0.18.1_ of powerToys, that ask to intall/update the netFramework too
claunia commented 2026-01-31 01:30:22 +00:00
Author
Owner
Copy Link

@crutkas commented on GitHub (May 28, 2020):

I'm having the same issue. When it happens, it persists when I close and re-open Terminal. But if I shut down Powertools, then it disappears.

I also noticed that if I run Terminal as administrator while PowerTools is running then I get this notification:
image

If terminal is run as admin, we can't resize the terminal window since PT runs at a lower permission. This is PowerToys telling you 'hey, you're in a state odd stuff may happen'

@crutkas commented on GitHub (May 28, 2020): > I'm having the same issue. When it happens, it persists when I close and re-open Terminal. But if I shut down Powertools, then it disappears. > > I also noticed that if I run Terminal as administrator while PowerTools is running then I get this notification: > ![image](https://user-images.githubusercontent.com/7281836/83039484-88195700-a03e-11ea-9eec-3387023a719d.png) If terminal is run as admin, we can't resize the terminal window since PT runs at a lower permission. This is PowerToys telling you 'hey, you're in a state odd stuff may happen'
claunia commented 2026-01-31 01:30:22 +00:00
Author
Owner
Copy Link

@transiient commented on GitHub (May 28, 2020):

This is PowerToys telling you 'hey, you're in a state odd stuff may happen'

This is interesting! However, (to the best of my knowledge) this issue isn't caused by running an elevated instance of Terminal. I think the same thing happens with regular permissions.

@transiient commented on GitHub (May 28, 2020): > This is PowerToys telling you 'hey, you're in a state odd stuff may happen' This is interesting! However, (to the best of my knowledge) this issue isn't caused by running an elevated instance of Terminal. I think the same thing happens with regular permissions.
claunia commented 2026-01-31 01:30:22 +00:00
Author
Owner
Copy Link

@crutkas commented on GitHub (May 28, 2020):

This is interesting! However, (to the best of my knowledge) this issue isn't caused by running an elevated instance of Terminal. I think the same thing happens with regular permissions.

this dialog is all about making users aware that FancyZones can't resize elevated apps. This GH issue and that are unrelated. Just wanted to clarify that.

@crutkas commented on GitHub (May 28, 2020): > This is interesting! However, (to the best of my knowledge) this issue isn't caused by running an elevated instance of Terminal. I think the same thing happens with regular permissions. this dialog is all about making users aware that FancyZones can't resize elevated apps. This GH issue and that are unrelated. Just wanted to clarify that.
claunia commented 2026-01-31 01:30:22 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Jun 23, 2020):

I've finally gotten a live repro of this on my machine. I'm on PT 0.18.0, but I'm certainly not about to update until we attempt to debug this. Now I'm just waiting on @crutkas to wake up and sign in 😜

CRAZILY, I've found an interesting piece of the puzzle - this only repros on my primary, high-DPI display. Both my external monitors are 96DPI, and if I drag the Terminal window to those displays, it works like a charm. I'm getting very similar behavior with the XAML Studio app, so I'd bet there's a weird interaction with XAML islands here.

@zadjii-msft commented on GitHub (Jun 23, 2020): I've _finally_ gotten a live repro of this on my machine. I'm on PT 0.18.0, but I'm certainly not about to update until we attempt to debug this. Now I'm just waiting on @crutkas to wake up and sign in 😜 CRAZILY, I've found an interesting piece of the puzzle - this only repros on my primary, high-DPI display. Both my external monitors are 96DPI, and if I drag the Terminal window to those displays, it works like a charm. I'm getting very similar behavior with the XAML Studio app, so I'd bet there's a weird interaction with XAML islands here.
claunia commented 2026-01-31 01:30:23 +00:00
Author
Owner
Copy Link

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

Hey all, just a follow up on this thread - if you're hitting this, could you try providing any of the following information:

  • 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)?

I just hit this yesterday, and although we don't have exact repro steps yet, we're trying to figure out anything that could be useful.

See also:

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 (Jun 24, 2020): Hey all, just a follow up on this thread - if you're hitting this, could you try providing any of the following information: * 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)? I just hit this yesterday, and although we don't have exact repro steps yet, we're trying to figure out anything that could be useful. See also: * https://github.com/microsoft/PowerToys/issues/4360 * https://github.com/microsoft/PowerToys/issues/3833 * https://github.com/microsoft/PowerToys/issues/3250 * https://github.com/microsoft/PowerToys/issues/3090 * (this list is not comprehensive) 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?
claunia commented 2026-01-31 01:30:23 +00:00
Author
Owner
Copy Link

@hectormz commented on GitHub (Jun 27, 2020):

So, I just encountered this again (since you posted this @zadjii-msft ).
I normally am using my laptop which has a high DPI display, which is off, and is connected to a high DPI monitor. (Scaling is set to recommended 250%)

I was using my laptop without an external monitor and couldn't interact with Windows Terminal with mouse.

I opened the powertoys settings, but couldn't click anything. But I do have the shortcut guide enabled, and it did come up after holding Win key.

After this, I went back to PowerToys settings which were now working, and I went back to Windows Terminal which was also back to normal. Seemingly just from bringing up the shortcut guide.

I have not uninstalled any IME to my knowledge.

@hectormz commented on GitHub (Jun 27, 2020): So, I just encountered this again (since you posted this @zadjii-msft ). I normally am using my laptop which has a high DPI display, which is off, and is connected to a high DPI monitor. (Scaling is set to recommended 250%) I was using my laptop without an external monitor and couldn't interact with Windows Terminal with mouse. I opened the powertoys settings, but couldn't click anything. But I do have the shortcut guide enabled, and it did come up after holding `Win` key. After this, I went back to PowerToys settings which were now working, and I went back to Windows Terminal which was also back to normal. Seemingly just from bringing up the shortcut guide. I have not uninstalled any IME to my knowledge.
claunia commented 2026-01-31 01:30:23 +00:00
Author
Owner
Copy Link

@masterashu commented on GitHub (Jun 30, 2020):

I had this same issue with Windows Terminal Version: 1.0.1401.0. I also experienced loss of mouse interactivity in the Twitter PWA Store app.

@masterashu commented on GitHub (Jun 30, 2020): I had this same issue with Windows Terminal Version: 1.0.1401.0. I also experienced loss of mouse interactivity in the Twitter PWA Store app.
claunia commented 2026-01-31 01:30:23 +00:00
Author
Owner
Copy Link

@crutkas commented on GitHub (Jun 30, 2020):

I had this same issue with Windows Terminal Version: 1.0.1401.0. I also experienced loss of mouse interactivity in the Twitter PWA Store app.

Do you have PowerToys installed. If so what is enabled.

@crutkas commented on GitHub (Jun 30, 2020): > I had this same issue with Windows Terminal Version: 1.0.1401.0. I also experienced loss of mouse interactivity in the Twitter PWA Store app. Do you have PowerToys installed. If so what is enabled.
claunia commented 2026-01-31 01:30:24 +00:00
Author
Owner
Copy Link

@masterashu commented on GitHub (Jun 30, 2020):

Yes Powertoys (v0.18.2) is installed. The enable features are: Image Resizer, Power Rename, and PowerToys Run.

@masterashu commented on GitHub (Jun 30, 2020): Yes Powertoys (v0.18.2) is installed. The enable features are: Image Resizer, Power Rename, and PowerToys Run.
claunia commented 2026-01-31 01:30:24 +00:00
Author
Owner
Copy Link

@crutkas commented on GitHub (Jun 30, 2020):

Yes Powertoys (v0.18.2) is installed. The enable features are: Image Resizer, Power Rename, and PowerToys Run.

But not shortcut guide or fancyzones? Interesting

@crutkas commented on GitHub (Jun 30, 2020): > Yes Powertoys (v0.18.2) is installed. The enable features are: Image Resizer, Power Rename, and PowerToys Run. But not shortcut guide or fancyzones? Interesting
claunia commented 2026-01-31 01:30:24 +00:00
Author
Owner
Copy Link

@mike-loux-planview commented on GitHub (Jul 24, 2020):

Just noticed this behavior for the first time this AM. Thank god for this thread or I'd be climbing the walls rn.

Hey all, just a follow up on this thread - if you're hitting this, could you try providing any of the following information:

  • Are you using the Terminal on a high DPI display?

Don't know - Samsung 27" curved 1080p gaming monitor.

  • If so, and if possible, does dragging the window to a 100% scaling display magically restore mouse functionality to the Terminal?

Dragging it to an identical, non-primary display does restore functionality.

  • Similarly, are you using the Terminal on your primary display?

It's considered display #2 by the system (LT screen is #1), but it IS my main display.

  • If so, and if possible, does dragging the window to another display magically restore mouse functionality to the Terminal?

It does indeed.

  • Does the PowerToys settings app similarly not respond to mouse input?

Yup. It sure doesn't.

  • Do you have the Shortcut Guide enabled in PowerToys?

Yup.

  • If so, does it actually work if you long press Win?

Not sure - I typically only have the shortcut keys pop up by accident. Did not try it this AM.

  • By any chance, did you recently uninstall any sort of IME (like a Chinese/Japanese/Korean language IME)?

No.

I just hit this yesterday, and although we don't have exact repro steps yet, we're trying to figure out anything that could be useful.

See also:

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?

Yup. That did the trick. I use Mouse in Windows Terminal for selecting text in PS several hundred times a day, so this is a good workaround for me. Thank you!

@mike-loux-planview commented on GitHub (Jul 24, 2020): Just noticed this behavior for the first time this AM. Thank god for this thread or I'd be climbing the walls rn. > Hey all, just a follow up on this thread - if you're hitting this, could you try providing any of the following information: > > * Are you using the Terminal on a high DPI display? Don't know - Samsung 27" curved 1080p gaming monitor. > > * If so, and if possible, does dragging the window to a 100% scaling display magically restore mouse functionality to the Terminal? Dragging it to an identical, non-primary display does restore functionality. > * Similarly, are you using the Terminal on your primary display? It's considered display #2 by the system (LT screen is #1), but it IS my main display. > > * If so, and if possible, does dragging the window to another display magically restore mouse functionality to the Terminal? It does indeed. > * Does the PowerToys settings app similarly not respond to mouse input? Yup. It sure doesn't. > * Do you have the Shortcut Guide enabled in PowerToys? Yup. > > * If so, does it actually work if you long press Win? Not sure - I typically only have the shortcut keys pop up by accident. Did not try it this AM. > * By any chance, did you recently uninstall any sort of IME (like a Chinese/Japanese/Korean language IME)? No. > > I just hit this yesterday, and although we don't have exact repro steps yet, we're trying to figure out anything that could be useful. > > See also: > > * [microsoft/PowerToys#4360](https://github.com/microsoft/PowerToys/issues/4360) > * [microsoft/PowerToys#3833](https://github.com/microsoft/PowerToys/issues/3833) > * [microsoft/PowerToys#3250](https://github.com/microsoft/PowerToys/issues/3250) > * [microsoft/PowerToys#3090](https://github.com/microsoft/PowerToys/issues/3090) > * (this list is not comprehensive) > > 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? Yup. That did the trick. I use Mouse in Windows Terminal for selecting text in PS several hundred times a day, so this is a good workaround for me. Thank you!
claunia commented 2026-01-31 01:30:24 +00:00
Author
Owner
Copy Link

@matteocontrini commented on GitHub (Aug 8, 2020):

Just happened to me.

Are you using the Terminal on a high DPI display?

No, but the resolution is 2560x1080

Similarly, are you using the Terminal on your primary display?

Yes

If so, and if possible, does dragging the window to another display magically restore mouse functionality to the Terminal?

I can't test unfortunately

Does the PowerToys settings app similarly not respond to mouse input?

Yes, it doesn't respond to mouse input

Do you have the Shortcut Guide enabled in PowerToys?

Yes

If so, does it actually work if you long press Win?

No, it doesn't

By any chance, did you recently uninstall any sort of IME (like a Chinese/Japanese/Korean language IME)?

No

@matteocontrini commented on GitHub (Aug 8, 2020): Just happened to me. > Are you using the Terminal on a high DPI display? No, but the resolution is 2560x1080 > Similarly, are you using the Terminal on your primary display? Yes > If so, and if possible, does dragging the window to another display magically restore mouse functionality to the Terminal? I can't test unfortunately > Does the PowerToys settings app similarly not respond to mouse input? Yes, it **doesn't** respond to mouse input > Do you have the Shortcut Guide enabled in PowerToys? Yes > If so, does it actually work if you long press Win? No, it doesn't > By any chance, did you recently uninstall any sort of IME (like a Chinese/Japanese/Korean language IME)? No
claunia commented 2026-01-31 01:30:24 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Aug 17, 2020):

Oh my goodness, would you look at that. There's also #3325 which is another (much older) thread about this exact same issue. Maybe we should close this thread and link the two up?

@zadjii-msft commented on GitHub (Aug 17, 2020): Oh my goodness, would you look at that. There's also #3325 which is another (much older) thread about this exact same issue. Maybe we should close this thread and link the two up?
claunia commented 2026-01-31 01:30:25 +00:00
Author
Owner
Copy Link

@vlovich commented on GitHub (Nov 14, 2020):

For me, dragging to a second monitor fixes it but it's still broken on the primary monitor when I drag it back. Turning off the powertoys shortcut guide re-enabled mouse again for me in the broken terminal.

@vlovich commented on GitHub (Nov 14, 2020): For me, dragging to a second monitor fixes it but it's still broken on the primary monitor when I drag it back. Turning off the powertoys shortcut guide re-enabled mouse again for me in the broken terminal.
claunia commented 2026-01-31 01:30:25 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Jan 29, 2021):

You know what, I'm just gonna close this in favor of /dup #3325, to try and keep the discussion in one place. Thanks!

@zadjii-msft commented on GitHub (Jan 29, 2021): You know what, I'm just gonna close this in favor of /dup #3325, to try and keep the discussion in one place. Thanks!
claunia commented 2026-01-31 01:30:25 +00:00
Author
Owner
Copy Link

@ghost commented on GitHub (Jan 29, 2021):

Hi! We've identified this issue as a duplicate of another one that already exists on this Issue Tracker. This specific instance is being closed in favor of tracking the concern over on the referenced thread. Thanks for your report!

@ghost commented on GitHub (Jan 29, 2021): Hi! We've identified this issue as a duplicate of another one that already exists on this Issue Tracker. This specific instance is being closed in favor of tracking the concern over on the referenced thread. Thanks for your report!
claunia commented 2026-01-31 01:30:25 +00:00
Author
Owner
Copy Link

@julie777 commented on GitHub (Oct 8, 2022):

I just discovered the same issue. I am running fancy zones. If I use the windows key shortcut to move the terminal to a different location the mouse works. If I use the shortcut to move it back the mouse stops working.

@julie777 commented on GitHub (Oct 8, 2022): I just discovered the same issue. I am running fancy zones. If I use the windows key shortcut to move the terminal to a different location the mouse works. If I use the shortcut to move it back the mouse stops working.
claunia commented 2026-01-31 01:30:25 +00:00
Author
Owner
Copy Link

@endrelovas commented on GitHub (Jul 4, 2023):

Did anyone got a resolution to this? I do not have Powertoys installed. Never had. Killing the process won't help. Dragging to another screen won't help. No high res. Nothing fancy here except for oh-my-posh.

@endrelovas commented on GitHub (Jul 4, 2023): Did anyone got a resolution to this? I do not have Powertoys installed. Never had. Killing the process won't help. Dragging to another screen won't help. No high res. Nothing fancy here except for oh-my-posh.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
⛺ Reserved
A11yCO
A11yMAS
A11ySev1
A11ySev2
A11ySev3
A11yTTValidated
A11yUsable
A11yVoiceAccess
A11yWCAG
Area-Accessibility
Area-AtlasEngine
Area-AzureShell
Area-Build
Area-Build
Area-Chat
Area-CmdPal
Area-CodeHealth
Area-Commandline
Area-CookedRead
Area-DefApp
Area-Extensibility
Area-Fonts
Area-GroupPolicy
Area-i18n
Area-Input
Area-Interaction
Area-Interop
Area-Localization
Area-Output
Area-Performance
Area-Portable
Area-Quality
Area-Remoting
Area-Rendering
Area-Schema
Area-Server
Area-Settings
Area-SettingsUI
Area-ShellExtension
Area-ShellExtension
Area-ShellExtension
Area-Suggestions
Area-Suggestions
Area-TerminalConnection
Area-TerminalControl
Area-Theming
Area-UserInterface
Area-VT
Area-Windowing
Area-WPFControl
AutoMerge
Blocking-Ingestion
Culprit-Centennial
Culprit-WinUI
Disability-All
Disability-Blind
Disability-LowVision
Disability-Mobility
External-Blocked-WinUI3
Fixed
Gathering-Data
good first issue
HCL-E+D
HCL-WindowsTerminal
Help Wanted
Impact-Compatibility
Impact-Compliance
Impact-Correctness
Impact-Visual
In-PR
InclusionBacklog
InclusionBacklog-Windows TerminalWin32
InclusionCommitted-202206
Issue-Bug
Issue-Docs
Issue-Feature
Issue-Feature
Issue-Question
Issue-Samples
Issue-Scenario
Issue-Task
Needs-Attention
Needs-Author-Feedback
Needs-Bisect
Needs-Discussion
Needs-Repro
Needs-Tag-Fix
Needs-Tag-Fix
Needs-Triage
No-Recent-Activity
Priority-0
Priority-1
Priority-2
Priority-3
Product-Cmd.exe
Product-Colortool
Product-Colortool
Product-Colortool
Product-Conhost
Product-Conpty
Product-Meta
Product-Powershell
Product-Terminal
Product-WSL
pull-request
Mirrored from GitHub Pull Request
 Resolution-Answered
Resolution-By-Design
Resolution-Duplicate
Resolution-External
Resolution-Fix-Available
Resolution-Fix-Committed
Resolution-No-Repro
Resolution-Won't-Fix
Severity-Blocking
Severity-Crash
Severity-DataLoss
spam
this-will-be-a-breaking-change
Tracking-External
WindowsTerminal_Win32
Work-Item
zAskModeBug
zInbox-Bug
No Label Area-Input Issue-Bug Priority-1 Product-Terminal Resolution-Duplicate
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
claunia
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/terminal#8471
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?