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

Can't reorder Windows Terminal tabs (W10 -> W11 regression?) #22682

New Issue
Open
opened 2026-01-31 08:20:28 +00:00 by claunia · 0 comments
claunia commented 2026-01-31 08:20:28 +00:00
Owner
Copy Link

Originally created by @mobeigi on GitHub (Dec 20, 2024).

Windows Terminal version

1.21.3231.0

Windows build number

10.0.26100.2605

Other Software

No response

Steps to reproduce

I have recently upgraded from W10 to W11.

My W10 setup was:

  • Run WT as elevated (administrator)
  • Default WT profile is an elevated tab
  • UAC disabled

With this setup, I was able to re-order all of my tabs without issues. I know this because I have screenshots / video recordings of me doing this, plus I was daily driving W10.

Now I am on W11, I have the same setup:

  • Run WT as elevated (administrator)
  • Default WT profile is an elevated tab
  • UAC disabled

However, I am unable to re-order my tabs.
I did discover other issues somewhat related to this #6661 (but discussion has been limited).

Other issues suggest that drag & drop is specifically disabled for elevated prompts, but how was I able to do this on W10 then? Does W11 act differently with regards to this behaviour?

Expected Behavior

I should be able to keep reorder tabs unless there is a difference between W10 and W11.

Actual Behavior

I am not able to reorder tabs if I spawn WT with a default profile that is elevated.
If I have non-elevated wt (with non-elevated profiles), it works.

Originally created by @mobeigi on GitHub (Dec 20, 2024). ### Windows Terminal version 1.21.3231.0 ### Windows build number 10.0.26100.2605 ### Other Software _No response_ ### Steps to reproduce I have recently upgraded from W10 to W11. My W10 setup was: - Run WT as elevated (administrator) - Default WT profile is an elevated tab - UAC disabled With this setup, I was able to re-order all of my tabs without issues. I know this because I have screenshots / video recordings of me doing this, plus I was daily driving W10. Now I am on W11, I have the same setup: - Run WT as elevated (administrator) - Default WT profile is an elevated tab - UAC disabled However, I am unable to re-order my tabs. I did discover other issues somewhat related to this #6661 (but discussion has been limited). Other issues suggest that drag & drop is specifically disabled for elevated prompts, but how was I able to do this on W10 then? Does W11 act differently with regards to this behaviour? ### Expected Behavior I should be able to keep reorder tabs unless there is a difference between W10 and W11. ### Actual Behavior I am not able to reorder tabs if I spawn WT with a default profile that is elevated. If I have non-elevated wt (with non-elevated profiles), it works.
claunia added the Issue-BugResolution-Duplicate labels 2026-01-31 08:20:28 +00:00
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 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#22682
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?