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 11 Win+X Terminal entries don't work with Terminal Preview #14442

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

Originally created by @obrobrio2000 on GitHub (Jul 9, 2021).

Originally assigned to: @DHowett on GitHub.

Windows Terminal version (or Windows build number)

10.0.22000.65 (happened also on 10.0.22000.51), 1.9.1523.0

Other Software

No response

Steps to reproduce

  1. Update to Windows 11 22000.65
  2. Uninstall Windows Terminal (stable) and install Windows Terminal Preview
  3. Use Win+X entries to open Terminal Preview.

Expected Behavior

If I have only Terminal Preview installed (and not stable Terminal) Win+X entries ("Windows Terminal" and "Windows Terminal (admin)") should detect that stable Terminal is not installed and open Terminal Preview.

Actual Behavior

If I have only Terminal Preview installed (and not stable Terminal) Win+X entries ("Windows Terminal" and "Windows Terminal (admin)") don't do nothing.
Feedback Hub link: https://aka.ms/AAd5bx7

Originally created by @obrobrio2000 on GitHub (Jul 9, 2021). Originally assigned to: @DHowett on GitHub. ### Windows Terminal version (or Windows build number) 10.0.22000.65 (happened also on 10.0.22000.51), 1.9.1523.0 ### Other Software _No response_ ### Steps to reproduce 1) Update to Windows 11 22000.65 2) Uninstall Windows Terminal (stable) and install Windows Terminal Preview 3) Use Win+X entries to open Terminal Preview. ### Expected Behavior If I have only Terminal Preview installed (and not stable Terminal) Win+X entries ("Windows Terminal" and "Windows Terminal (admin)") should detect that stable Terminal is not installed and open Terminal Preview. ### Actual Behavior If I have only Terminal Preview installed (and not stable Terminal) Win+X entries ("Windows Terminal" and "Windows Terminal (admin)") don't do nothing. Feedback Hub link: https://aka.ms/AAd5bx7
claunia commented 2026-01-31 04:10:32 +00:00
Author
Owner
Copy Link

@DHowett commented on GitHub (Jul 9, 2021):

We're already working this out with the team that owns Win+X 😄

Thanks!

@DHowett commented on GitHub (Jul 9, 2021): We're already working this out with the team that owns Win+X :smile: Thanks!
claunia commented 2026-01-31 04:10:32 +00:00
Author
Owner
Copy Link

@MartinGC94 commented on GitHub (Jul 11, 2021):

IMO they should bring back the cmd/powershell shortcuts and simply let the "Default terminal application" setting decide which terminal you would end up in. Or if we can dream a little bigger: Full customization of the Win+X shortcuts without third party programs.

@MartinGC94 commented on GitHub (Jul 11, 2021): IMO they should bring back the cmd/powershell shortcuts and simply let the "Default terminal application" setting decide which terminal you would end up in. Or if we can dream a little bigger: Full customization of the Win+X shortcuts without third party programs.
claunia commented 2026-01-31 04:10:33 +00:00
Author
Owner
Copy Link

@obrobrio2000 commented on GitHub (Jul 12, 2021):

IMO they should bring back the cmd/powershell shortcuts and simply let the "Default terminal application" setting decide which terminal you would end up in. Or if we can dream a little bigger: Full customization of the Win+X shortcuts without third party programs.

I completely agree with you, that would be a lot better. It can already be done manually with third-party tools (as you mentioned), in fact when I was on Windows 10 I had those two shortcuts (cmd and ps) customized to open the corresponding Windows Terminal profiles (wt.exe -p "Command Prompt" and wt.exe -p "Windows PowerShell"). Can be done also on Windows 11 but I don't want to waste time because every Win+X modification gets reset to default after every update.

However, words aside, I made a suggestion on Feedback Hub about this (hoping Microsoft will take this into consideration): https://aka.ms/AAd5o2p

@obrobrio2000 commented on GitHub (Jul 12, 2021): > IMO they should bring back the cmd/powershell shortcuts and simply let the "Default terminal application" setting decide which terminal you would end up in. Or if we can dream a little bigger: Full customization of the Win+X shortcuts without third party programs. I completely agree with you, that would be a lot better. It can already be done manually with third-party tools (as you mentioned), in fact when I was on Windows 10 I had those two shortcuts (cmd and ps) customized to open the corresponding Windows Terminal profiles (wt.exe -p "Command Prompt" and wt.exe -p "Windows PowerShell"). Can be done also on Windows 11 but I don't want to waste time because every Win+X modification gets reset to default after every update. However, words aside, I made a suggestion on Feedback Hub about this (hoping Microsoft will take this into consideration): https://aka.ms/AAd5o2p
claunia commented 2026-01-31 04:10:33 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Aug 10, 2021):

this might be MSFT:34139006 internally, though there's still discussion about if that's really the right thread or not.

@zadjii-msft commented on GitHub (Aug 10, 2021): this might be MSFT:34139006 internally, though there's still discussion about if that's really the right thread or not.
claunia commented 2026-01-31 04:10:34 +00:00
Author
Owner
Copy Link

@dylumian commented on GitHub (Oct 5, 2021):

The matter is still unresolved

@dylumian commented on GitHub (Oct 5, 2021): The matter is still unresolved
claunia commented 2026-01-31 04:10:34 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Oct 5, 2021):

Yep. We'll make sure to update this thread when there is. In the meantime, might I recommend the Subscribe button?
image
That way you'll be notified of any updates to this thread, without needlessly pinging everyone on this thread ☺️

Internally I think this was fixed in a recent PR, but I don't believe that'll be in the version of Windows 11 shipping today. I honestly have no idea what the ship cadence is like for Windows 11, so it should be out "eventually". 10.0.22469 does seem like it has the fix.

@zadjii-msft commented on GitHub (Oct 5, 2021): Yep. We'll make sure to update this thread when there is. In the meantime, might I recommend the Subscribe button? ![image](https://user-images.githubusercontent.com/18356694/91237459-5cbb0c80-e700-11ea-9347-b9b1ec2813b1.png) That way you'll be notified of any updates to this thread, without needlessly pinging everyone on this thread ☺️ Internally I think this was fixed in a recent PR, but I don't believe that'll be in the version of Windows 11 shipping today. I honestly have no idea what the ship cadence is like for Windows 11, so it should be out "eventually". `10.0.22469` does seem like it has the fix.
claunia commented 2026-01-31 04:10:34 +00:00
Author
Owner
Copy Link

@Dhyfer1 commented on GitHub (Nov 6, 2021):

is there any progress with this issue? I have the same problem and need to know if there is any other way to launch Windows Terminal Preview as administrator in Windows 11?

@Dhyfer1 commented on GitHub (Nov 6, 2021): is there any progress with this issue? I have the same problem and need to know if there is any other way to launch Windows Terminal Preview as administrator in Windows 11?
claunia commented 2026-01-31 04:10:34 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Nov 8, 2021):

@Dhyfer1 Yea, this is actually fixed on internal builds. Not sure if that's flowed out to an Insider's release yet.

@zadjii-msft commented on GitHub (Nov 8, 2021): @Dhyfer1 Yea, this is actually fixed on internal builds. Not sure if that's flowed out to an Insider's release yet.
claunia commented 2026-01-31 04:10:35 +00:00
Author
Owner
Copy Link

@Dhyfer1 commented on GitHub (Nov 10, 2021):

@zadjii-msft Yea, this is actually fixed on internal builds. Not sure if that's flowed out to an Insider's release yet.

Are you saying that Win+X is already working correctly with Windows Terminal Preview? and that we don't know in which Windows Insider channel it is working that way?

@Dhyfer1 commented on GitHub (Nov 10, 2021): > @zadjii-msft Yea, this is actually fixed on internal builds. Not sure if that's flowed out to an Insider's release yet. Are you saying that Win+X is already working correctly with Windows Terminal Preview? and that we don't know in which Windows Insider channel it is working that way?
claunia commented 2026-01-31 04:10:35 +00:00
Author
Owner
Copy Link

@maicol07 commented on GitHub (Nov 10, 2021):

@Dhyfer1 I confirm it works in the Insider channel. Don't know in other ones

@maicol07 commented on GitHub (Nov 10, 2021): @Dhyfer1 I confirm it works in the Insider channel. Don't know in other ones
claunia commented 2026-01-31 04:10:35 +00:00
Author
Owner
Copy Link

@Dhyfer1 commented on GitHub (Nov 10, 2021):

@maicol07 I confirm it works in the Insider channel. Don't know in other ones

Thank you for your response. I didn't think the preview version of Windows Terminal would release updates the way Windows does (dev and beta channel users first).
Then I will have to keep waiting for the Windows+X feature to come to the stable channel.

@Dhyfer1 commented on GitHub (Nov 10, 2021): > @maicol07 I confirm it works in the Insider channel. Don't know in other ones Thank you for your response. I didn't think the preview version of Windows Terminal would release updates the way Windows does (dev and beta channel users first). Then I will have to keep waiting for the Windows+X feature to come to the stable channel.
claunia commented 2026-01-31 04:10:35 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Nov 10, 2021):

Yep. FWIW, this was an OS-side fix, not something we could fix in the Terminal itself. Hence why the fix is tied to the OS versions and the OS Insiders channels.

I'm gonna close this one out, since we've got confirmation that the fix is available in at least some external builds now. Thanks all!

@zadjii-msft commented on GitHub (Nov 10, 2021): Yep. FWIW, this was an OS-side fix, not something we could fix in the Terminal itself. Hence why the fix is tied to the OS versions and the OS Insiders channels. I'm gonna close this one out, since we've got confirmation that the fix is available in at least some external builds now. Thanks all!
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-Tag-Fix Product-Terminal Resolution-External Resolution-Fix-Available Tracking-External
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#14442
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?