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

Open in Windows Terminal not using app alias #13437

New Issue
Closed
opened 2026-01-31 03:42:42 +00:00 by claunia · 9 comments
claunia commented 2026-01-31 03:42:42 +00:00
Owner
Copy Link

Originally created by @vefatica on GitHub (Apr 14, 2021).

Windows Terminal version (or Windows build number)

Microsoft Windows 10 Pro for Workstations10.0.19042.928 (2009, 20H2)

Other Software

No response

Steps to reproduce

I just installed WindowsTerminal 1.7.1033.0 and 1.8.1033.0, the latter being the new preview. My app alias points to the preview. "Open in Windows Terminal" starts 1.7.1033.0. It may be that this behavior is not new and I'm noticing it for the first time. Is it as expected?

Expected Behavior

No response

Actual Behavior

See above.

Originally created by @vefatica on GitHub (Apr 14, 2021). ### Windows Terminal version (or Windows build number) Microsoft Windows 10 Pro for Workstations10.0.19042.928 (2009, 20H2) ### Other Software _No response_ ### Steps to reproduce I just installed WindowsTerminal 1.7.1033.0 and 1.8.1033.0, the latter being the new preview. My app alias points to the preview. "Open in Windows Terminal" starts 1.7.1033.0. It may be that this behavior is not new and I'm noticing it for the first time. Is it as expected? ### Expected Behavior _No response_ ### Actual Behavior See above.
claunia added the Needs-TriageNeeds-Tag-Fix labels 2026-01-31 03:42:42 +00:00
claunia commented 2026-01-31 03:42:43 +00:00
Author
Owner
Copy Link

@DHowett commented on GitHub (Apr 14, 2021):

The versioned shell extension launches the version of Terminal that it was packaged with. It does not launch your preferred version. You probably have one menu entry with the normal icon and one with the preview icon.

This is by design as of #9510.

@DHowett commented on GitHub (Apr 14, 2021): The versioned shell extension launches the version of Terminal that it was packaged with. It does not launch your preferred version. You probably have one menu entry with the normal icon and one with the preview icon. This is by design as of #9510.
claunia commented 2026-01-31 03:42:43 +00:00
Author
Owner
Copy Link

@vefatica commented on GitHub (Apr 14, 2021):

I don't quite understand. I uninstalled both and reinstalled only the preview. Now I don't have "Open in Windows Terminal". Is that expected?

@vefatica commented on GitHub (Apr 14, 2021): I don't quite understand. I uninstalled both and reinstalled only the preview. Now I don't have "Open in Windows Terminal". Is that expected?
claunia commented 2026-01-31 03:42:43 +00:00
Author
Owner
Copy Link

@DHowett commented on GitHub (Apr 14, 2021):

That's not expected, but also not something we can exactly help. Explorer has some cache that it uses for shell extension availability, and I suspect that when it gets rebuilt things will settle. Terminal only registers to say "I have a shell extension" and everything after that is up to the shell.

@DHowett commented on GitHub (Apr 14, 2021): That's not expected, but also not something we can exactly help. Explorer has some cache that it uses for shell extension availability, and I suspect that when it gets rebuilt things will settle. Terminal _only_ registers to say "I have a shell extension" and everything after that is up to the shell.
claunia commented 2026-01-31 03:42:44 +00:00
Author
Owner
Copy Link

@DHowett commented on GitHub (Apr 14, 2021):

(ugh. another MSIX issue. 😄)

@DHowett commented on GitHub (Apr 14, 2021): (ugh. another MSIX issue. :smile:)
claunia commented 2026-01-31 03:42:44 +00:00
Author
Owner
Copy Link

@vefatica commented on GitHub (Apr 14, 2021):

I uninstalled both and reinstalled only the preview. Now I don't have "Open in Windows Terminal".

And now, a couple hours later, I (re)installed 1.7.1033.0 and I have "Open in ..." again (while the alias still points to the preview). Does the Preview have a context menu handler and an installer for it?

@vefatica commented on GitHub (Apr 14, 2021): > I uninstalled both and reinstalled only the preview. Now I don't have "Open in Windows Terminal". And now, a couple hours later, I (re)installed 1.7.1033.0 and I have "Open in ..." again (while the alias still points to the preview). Does the Preview have a context menu handler and an installer for it?
claunia commented 2026-01-31 03:42:44 +00:00
Author
Owner
Copy Link

@DHowett commented on GitHub (Apr 14, 2021):

Yes, both have context menu handlers. Pre and Stable use the same mechanism--namely, the declarative app manifest--to announce their shell extensions. All of the processing for those registrations happens completely out of our control, as is intended.

FYI- With the three versions, my shell does show them all (it is rather a lot)

image

@DHowett commented on GitHub (Apr 14, 2021): Yes, both have context menu handlers. Pre and Stable use the same mechanism--namely, the declarative app manifest--to announce their shell extensions. All of the _processing_ for those registrations happens completely out of our control, as is intended. FYI- With the three versions, my shell does show them all (it is rather a lot) ![image](https://user-images.githubusercontent.com/189190/114778552-9d70a000-9d3a-11eb-9138-3c6116bd3be0.png)
claunia commented 2026-01-31 03:42:44 +00:00
Author
Owner
Copy Link

@vefatica commented on GitHub (Apr 14, 2021):

I went through the whole process again ... uninstalled both ... installed the preview ... no context menu ... installed the stable version ... context menu. To me, it doesn't look like the two behave the same.

Can anything be done about settings.json being deleted when you uninstall? I was lucky; I also had a settings.json for the un-packaged installation (in "C:\Users\vefatica\AppData\Local\Microsoft\Windows Terminal"). Without that I would have had to do quite a bit of work.

@vefatica commented on GitHub (Apr 14, 2021): I went through the whole process again ... uninstalled both ... installed the preview ... no context menu ... installed the stable version ... context menu. To me, it doesn't look like the two behave the same. Can anything be done about settings.json being deleted when you uninstall? I was lucky; I also had a settings.json for the un-packaged installation (in "C:\Users\vefatica\AppData\Local\Microsoft\Windows Terminal\"). Without that I would have had to do quite a bit of work.
claunia commented 2026-01-31 03:42:45 +00:00
Author
Owner
Copy Link

@vefatica commented on GitHub (Apr 14, 2021):

Hmmm! I've had both stable and preview installed for a long time (maybe a year or so). I have never seen multiple "Open in Windows Terminal" context menu items.

@vefatica commented on GitHub (Apr 14, 2021): Hmmm! I've had both stable and preview installed for a long time (maybe a year or so). I have never seen multiple "Open in Windows Terminal" context menu items.
claunia commented 2026-01-31 03:42:45 +00:00
Author
Owner
Copy Link

@DHowett commented on GitHub (Apr 15, 2021):

Can anything be done about settings.json being deleted when you uninstall?

I wish.

This is by design as of #9510.

9510 only shipped in 1.7.1033 and 1.8.1032.

@DHowett commented on GitHub (Apr 15, 2021): > Can anything be done about settings.json being deleted when you uninstall? I wish. > This is by design as of #9510. 9510 only shipped in 1.7.1033 and 1.8.1032.
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 Needs-Tag-Fix 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#13437
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?