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

The taskbar icon stuck on the primary monitor if the Terminal window is forced to open on a secondary monitor by other software #23457

New Issue
Closed
opened 2026-01-31 08:42:48 +00:00 by claunia · 1 comment
claunia commented 2026-01-31 08:42:48 +00:00
Owner
Copy Link

Originally created by @barretgoat on GitHub (Jul 19, 2025).

Windows Terminal version

1.22.11751.0

Windows build number

10.0.26100.0

Other Software

MS PowerToys' FancyZones (0.92.1)

Steps to reproduce

  1. Make sure the computer has at least two monitors connected.
  2. Go into Windows Settings > Personalization > Taskbar and make sure "show my taskbar on all displays" is turned on and "when using multiple displays, show my taskbar apps on" is set to "taskbar where window is open".
  3. Install Microsoft PowerToys.
  4. Activate FancyZones, optionally set up the zones for all monitors, then go into settings for the module and make sure that "Move newly created windows to their last known zone" option in the Windows section is enabled.
  5. Open a Terminal window, drag it to a secondary monitor and make sure it is snapped into one of the FancyZones' zones.
  6. Close the window and launch Terminal again.

Expected Behavior

The taskbar icon should appear on the monitor that the window launches on.

Actual Behavior

The taskbar icon appears on the primary monitor even though the window is opened on the secondary, and remains there until the window is manually dragged to the primary monitor and then back to the secondary.

Video of the issue:

https://github.com/user-attachments/assets/443da590-5bf9-4d83-baf6-a8a5178a5561

Originally created by @barretgoat on GitHub (Jul 19, 2025). ### Windows Terminal version 1.22.11751.0 ### Windows build number 10.0.26100.0 ### Other Software MS PowerToys' FancyZones (0.92.1) ### Steps to reproduce 1. Make sure the computer has at least two monitors connected. 2. Go into Windows Settings > Personalization > Taskbar and make sure "show my taskbar on all displays" is turned on and "when using multiple displays, show my taskbar apps on" is set to "taskbar where window is open". 3. Install Microsoft PowerToys. 4. Activate FancyZones, optionally set up the zones for all monitors, then go into settings for the module and make sure that "Move newly created windows to their last known zone" option in the Windows section is enabled. 5. Open a Terminal window, drag it to a secondary monitor and make sure it is snapped into one of the FancyZones' zones. 6. Close the window and launch Terminal again. ### Expected Behavior The taskbar icon should appear on the monitor that the window launches on. ### Actual Behavior The taskbar icon appears on the primary monitor even though the window is opened on the secondary, and remains there until the window is manually dragged to the primary monitor and then back to the secondary. Video of the issue: https://github.com/user-attachments/assets/443da590-5bf9-4d83-baf6-a8a5178a5561
claunia added the Needs-TriageIssue-Bug labels 2026-01-31 08:42:49 +00:00
claunia commented 2026-01-31 08:42:50 +00:00
Author
Owner
Copy Link

@DHowett commented on GitHub (Jul 30, 2025):

I think this is a Windows bug. We actually don't control anything about our taskbar icon except what it looks like. Would you mind filing an issue in Feedback Hub?

@DHowett commented on GitHub (Jul 30, 2025): I think this is a Windows bug. We actually don't control anything about our taskbar icon except what it looks like. Would you mind filing an issue in Feedback Hub?
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 Issue-Bug Needs-Triage
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#23457
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?