"Open in Windows Terminal" of WT Preview disappears if WT is not installed #13490

Open
opened 2026-01-31 03:44:06 +00:00 by claunia · 10 comments
Owner

Originally created by @Henry-ZHR on GitHub (Apr 16, 2021).

Windows Terminal version (or Windows build number)

Windows 10.0.21354.0

Windows Terminal Preview v1.8.1032.0

Other Software

No response

Steps to reproduce

Uninstall Windows Terminal

Expected Behavior

Only "Open in Windows Terminal" of WT disappears

Actual Behavior

"Open in Windows Terminal" of both WT and WT Preview disappear

Originally created by @Henry-ZHR on GitHub (Apr 16, 2021). ### Windows Terminal version (or Windows build number) Windows 10.0.21354.0 Windows Terminal Preview v1.8.1032.0 ### Other Software _No response_ ### Steps to reproduce Uninstall Windows Terminal ### Expected Behavior Only "Open in Windows Terminal" of WT disappears ### Actual Behavior "Open in Windows Terminal" of both WT and WT Preview disappear
claunia added the Issue-BugPriority-3Product-TerminalArea-ShellExtension labels 2026-01-31 03:44:07 +00:00
Author
Owner

@zadjii-msft commented on GitHub (Apr 16, 2021):

  • What versions of the Terminal did you have installed? 1.6...? 1.7...?
  • Have you rebooted since installing/uninstalling? explorer.exe is notoriously aggressive about caching context menu entries.
@zadjii-msft commented on GitHub (Apr 16, 2021): * What versions of the Terminal did you have installed? 1.6...? 1.7...? * Have you rebooted since installing/uninstalling? `explorer.exe` is notoriously aggressive about caching context menu entries.
Author
Owner

@Henry-ZHR commented on GitHub (Apr 16, 2021):

@zadjii-msft Rebooting doesn't help

Just install Windows Terminal can get them back, but I just want to see the one of WT Preview

@Henry-ZHR commented on GitHub (Apr 16, 2021): @zadjii-msft Rebooting doesn't help Just install Windows Terminal can get them back, but I just want to see the one of WT Preview
Author
Owner

@zadjii-msft commented on GitHub (Apr 16, 2021):

Again, which version of Windows Terminal Preview, release, do you have installed? We just changed how those dialogs are registered, but the Store isn't always the best at rolling out updates. This might be a weird interaction between the 1.8 preview and the 1.7 stable, but I'll need some version numbers to be sure

@zadjii-msft commented on GitHub (Apr 16, 2021): Again, which version of Windows Terminal Preview, release, do you have installed? We _just_ changed how those dialogs are registered, but the Store isn't always the best at rolling out updates. This might be a weird interaction between the 1.8 preview and the 1.7 stable, but I'll need some version numbers to be sure
Author
Owner

@Henry-ZHR commented on GitHub (Apr 16, 2021):

Windows Terminal Preview v1.8.1032.0

(I added them to the issue description just now

@Henry-ZHR commented on GitHub (Apr 16, 2021): Windows Terminal Preview v1.8.1032.0 (I added them to the issue description just now
Author
Owner

@Henry-ZHR commented on GitHub (Apr 16, 2021):

I think I had Windows Terminal v1.7.1033.0 installed but I'm not sure since I can't install it from Microsoft Store now

Windows Terminal Preview installed by msixbundle from GitHub Release

@Henry-ZHR commented on GitHub (Apr 16, 2021): I think I had Windows Terminal v1.7.1033.0 installed but I'm not sure since I can't install it from Microsoft Store now Windows Terminal Preview installed by msixbundle from GitHub Release
Author
Owner

@seritools commented on GitHub (Apr 25, 2021):

Can confirm - clean install of Insider build 21364, Terminal Preview 1.8.1032.0.

If the non-preview version is not installed, the context menu entry does not appear. If I install it, both regular and preview entries appear.

@seritools commented on GitHub (Apr 25, 2021): Can confirm - clean install of Insider build 21364, Terminal Preview 1.8.1032.0. If the non-preview version is not installed, the context menu entry does not appear. If I install it, *both* regular and preview entries appear.
Author
Owner

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

I can repro this also. I have 1.7.1091.0 and 1.8.1092.0 both installed using bundles from GitHub. With this

image

uninstalling 1.7.1091 removes both context menu items. Reinstalling 1.7.1091 brings both back.

@vefatica commented on GitHub (Apr 26, 2021): I can repro this also. I have 1.7.1091.0 and 1.8.1092.0 both installed using bundles from GitHub. With this ![image](https://user-images.githubusercontent.com/61856645/116138257-95055700-a6a2-11eb-9617-550790782259.png) uninstalling 1.7.1091 removes both context menu items. Reinstalling 1.7.1091 brings both back.
Author
Owner

@TBBle commented on GitHub (May 3, 2021):

I hit this problem the other day, both versions installed from the store, same Preview version as the original bug report, but I didn't notice the non-preview version number before I uninstalled it. This is Windows 10 20H2 (19042.928).

After a reboot or two after uninstalling the non-Preview version (and the last reboot was a system-crash, so know it was a clean boot), I happened to notice that my "Open in Windows Terminal" option is back, just for the Preview version (the only one I have installed), so I assume this symptom can be triggered by Explorer caching stuff. In that session I was also removing "X here" registry keys for things like Git Bash or MSYS (since I want to run those in Terminal, not conhost) and it was taking effect immediately, but I assume things registered by CLSID rather than a 'shell' registry key are more likely to be cached until reboot.

Not that useful for @Henry-ZHR, but for anyone else who finds this ticket with the same symptoms, check again after next system startup.

@TBBle commented on GitHub (May 3, 2021): I hit this problem the other day, both versions installed from the store, same Preview version as the original bug report, but I didn't notice the non-preview version number before I uninstalled it. This is Windows 10 20H2 (19042.928). After a reboot or two after uninstalling the non-Preview version (and the last reboot was a system-crash, so _know_ it was a clean boot), I happened to notice that my "Open in Windows Terminal" option is back, just for the Preview version (the only one I have installed), so I assume this symptom _can_ be triggered by Explorer caching stuff. In that session I was also removing "X here" registry keys for things like Git Bash or MSYS (since I want to run those in Terminal, not conhost) and it was taking effect immediately, but I assume things registered by CLSID rather than a 'shell' registry key are more likely to be cached until reboot. Not that useful for @Henry-ZHR, but for anyone else who finds this ticket with the same symptoms, check again after next system startup.
Author
Owner

@gbr000 commented on GitHub (Feb 13, 2023):

What can we do until then? Please provide a .reg file or PowerShell command to fix that!

@gbr000 commented on GitHub (Feb 13, 2023): What can we do until then? Please provide a .reg file or PowerShell command to fix that!
Author
Owner

@vefatica commented on GitHub (Feb 13, 2023):

My home-brewed solution works. I have an unzip-only installation of WT. I use this this with similar entries in HKEY_CLASSES_ROOT\Directory\Background, HKEY_CLASSES_ROOT\Drive, and HKEY_CLASSES_ROOT\Folder. I reckon you'll have to (at least) use the path to your preferred shell, change the "*cdd" command to something appropriate, and duplicate this for the other three keys. If WT has a command line option for start-up directory, and you don't mind getting the default start-up shell and directory, you might be able to omit the shell and its command. I don't know if that will work; I haven't tried it.

An entry in "...\Background" lets you start WT from the right-click context menu for the background in an Explorer window and on the desktop itself (which is a directory background).

Windows Registry Editor Version 5.00

[HKEY_CLASSES_ROOT\Directory\shell\WT]
@="WTHere"

[HKEY_CLASSES_ROOT\Directory\shell\WT\command]
@="wt.exe nt d:\\tc28\\tcc.exe *cdd \"%V\""

I also have this, which makes life nice. Without this you might (above) have to supply a path to windowsterminal.exe.

Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\App Paths\wt.exe]
@="d:\\wt\\exe\\windowsterminal.exe"
"Path"=" d:\\wt\\exe"

@vefatica commented on GitHub (Feb 13, 2023): My home-brewed solution works. I have an unzip-only installation of WT. I use this this with similar entries in HKEY_CLASSES_ROOT\Directory\Background, HKEY_CLASSES_ROOT\Drive, and HKEY_CLASSES_ROOT\Folder. I reckon you'll have to (at least) use the path to your preferred shell, change the "*cdd" command to something appropriate, and duplicate this for the other three keys. If WT has a command line option for start-up directory, and you don't mind getting the default start-up shell and directory, you might be able to omit the shell and its command. I don't know if that will work; I haven't tried it. An entry in "...\Background" lets you start WT from the right-click context menu for the background in an Explorer window and on the desktop itself (which is a directory background). ``` Windows Registry Editor Version 5.00 [HKEY_CLASSES_ROOT\Directory\shell\WT] @="WTHere" [HKEY_CLASSES_ROOT\Directory\shell\WT\command] @="wt.exe nt d:\\tc28\\tcc.exe *cdd \"%V\"" ``` I also have this, which makes life nice. Without this you might (above) have to supply a path to windowsterminal.exe. ``` Windows Registry Editor Version 5.00 [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\App Paths\wt.exe] @="d:\\wt\\exe\\windowsterminal.exe" "Path"=" d:\\wt\\exe" ```
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/terminal#13490