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

Window controls and mouse stop working when moving the terminal to an external monitor #7912

New Issue
Closed
opened 2026-01-31 01:15:36 +00:00 by claunia · 7 comments
claunia commented 2026-01-31 01:15:36 +00:00
Owner
Copy Link

Originally created by @threkk on GitHub (May 3, 2020).

Environment

Windows build number: Win32NT 10.0.18363.0 Microsoft Windows NT 10.0.18363.0
Windows Terminal version (if applicable) :0.11.1191.0

Any other software?

Steps to reproduce

Open terminal or move an existing terminal window to an external monitor.

Expected behaviour vs actual behaviour

When I open the terminal in my laptop's screen, it works: I can click on minimise, maximise, new tab, etc. Once I move it to my external monitor, all the buttons become unresponsive. I cannot maximise, close, create a new tab, etc until I move it to my laptop's screen. However, key bindings, moving the window or resizing the window still works.

Originally created by @threkk on GitHub (May 3, 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: Win32NT 10.0.18363.0 Microsoft Windows NT 10.0.18363.0 Windows Terminal version (if applicable) :0.11.1191.0 Any other software? ``` # Steps to reproduce Open terminal or move an existing terminal window to an external monitor. <!-- A description of how to trigger this bug. --> # Expected behaviour vs actual behaviour When I open the terminal in my laptop's screen, it works: I can click on minimise, maximise, new tab, etc. Once I move it to my external monitor, all the buttons become unresponsive. I cannot maximise, close, create a new tab, etc until I move it to my laptop's screen. However, key bindings, moving the window or resizing the window still works. <!-- A description of what you're expecting, possibly containing screenshots or reference material. -->
claunia added the Resolution-Duplicate label 2026-01-31 01:15:36 +00:00
claunia commented 2026-01-31 01:15:37 +00:00
Author
Owner
Copy Link

@DHowett-MSFT commented on GitHub (May 3, 2020):

Are you using PowerToys?

@DHowett-MSFT commented on GitHub (May 3, 2020): Are you using PowerToys?
claunia commented 2026-01-31 01:15:37 +00:00
Author
Owner
Copy Link

@threkk commented on GitHub (May 3, 2020):

Yes! I forgot to mention it! I am running PowerToys 0.16.0 It has exactly the same issue as Terminal. Once I closed it, everything worked as expected. Should I report this bug on the Power Toys repository?

@threkk commented on GitHub (May 3, 2020): Yes! I forgot to mention it! I am running PowerToys 0.16.0 It has exactly the same issue as Terminal. Once I closed it, everything worked as expected. Should I report this bug on the Power Toys repository?
claunia commented 2026-01-31 01:15:37 +00:00
Author
Owner
Copy Link

@DHowett-MSFT commented on GitHub (May 3, 2020):

That would be great. We also have /dup #3325 on our side tracking this 😄

@DHowett-MSFT commented on GitHub (May 3, 2020): That would be great. We also have /dup #3325 on our side tracking this :smile:
claunia commented 2026-01-31 01:15:38 +00:00
Author
Owner
Copy Link

@ghost commented on GitHub (May 3, 2020):

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 (May 3, 2020): 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:15:38 +00:00
Author
Owner
Copy Link

@threkk commented on GitHub (May 3, 2020):

Update: this is not happening if I am running PowerToys 0.17.0 Whatever it was, on the latest version does not happen, so I guess everything is good :)

@threkk commented on GitHub (May 3, 2020): Update: this is not happening if I am running PowerToys 0.17.0 Whatever it was, on the latest version does not happen, so I guess everything is good :)
claunia commented 2026-01-31 01:15:38 +00:00
Author
Owner
Copy Link

@DHowett-MSFT commented on GitHub (May 3, 2020):

That's great!

@DHowett-MSFT commented on GitHub (May 3, 2020): That's great!
claunia commented 2026-01-31 01:15:38 +00:00
Author
Owner
Copy Link

@itsjef commented on GitHub (May 13, 2020):

Mine is exactly opposite! Window control and mouse only work in an external monitor. The issue disappeared after upgrading to PowerToys 0.17.0

@itsjef commented on GitHub (May 13, 2020): Mine is exactly opposite! Window control and mouse only work in an external monitor. The issue disappeared after upgrading to PowerToys 0.17.0
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 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#7912
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?