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

Explorer context-menu is missing when Windows Terminal is installed side-by-side with Windows Terminal Preview #12890

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

Originally created by @conioh on GitHub (Mar 6, 2021).

Environment

Windows build number: 19042
Windows Terminal version (if applicable): 1.6.10571.0

Any other software?
Windows Terminal Preview 1.7.572.0

Steps to reproduce

  1. Install Windows Terminal from the Microsoft Store.
  2. Install Windows Terminal Preview from the Microsoft Store.
  3. Open a folder in Windows Explorer, for example C:\.
  4. Right click.

Expected behavior

Two distinct options: Open in Windows Terminal and Open in Windows Terminal Preview.

Windows Terminal and Windows Terminal Preview are distinct packages. They have distinct package names and AUMIDs. They can be installed independently. They can run independently. They have distinct configurations in separate directories.

I expect to be able to run both of them (or at least the one of my choosing!) from Windows Explorer.

Actual behavior

Note the icon is for Windows Terminal Preview and indeed it opens the Preview.

image

Possible implementation

I suspect using distinct CLSIDs for the two packages would suffice.

If you can have different strings, icons, etc. having different CLSIDs shouldn't be that hard.

image

Originally created by @conioh on GitHub (Mar 6, 2021). <!-- 🚨🚨🚨🚨🚨🚨🚨🚨🚨🚨 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: 19042 Windows Terminal version (if applicable): 1.6.10571.0 Any other software? Windows Terminal Preview 1.7.572.0 ``` # Steps to reproduce 1. Install Windows Terminal from the Microsoft Store. 2. Install Windows Terminal Preview from the Microsoft Store. 3. Open a folder in Windows Explorer, for example `C:\`. 4. Right click. # Expected behavior Two distinct options: _Open in Windows Terminal_ and _Open in Windows Terminal Preview_. Windows Terminal and Windows Terminal Preview are distinct packages. They have distinct package names and AUMIDs. They can be installed independently. They can run independently. They have distinct configurations in separate directories. I expect to be able to run both of them (or at least the one of my choosing!) from Windows Explorer. # Actual behavior Note the icon is for Windows Terminal _Preview_ and indeed it opens the Preview. ![image](https://user-images.githubusercontent.com/10606081/110220480-a2863800-7ece-11eb-88fc-818401e5ab43.png) # Possible implementation I suspect using distinct CLSIDs for the two packages would suffice. If you can have different strings, icons, etc. having different CLSIDs shouldn't be that hard. ![image](https://user-images.githubusercontent.com/10606081/110245912-f85ded00-7f6d-11eb-9fa5-785e7baa10de.png)
claunia added the Resolution-Duplicate label 2026-01-31 03:28:12 +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 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#12890
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?