Continued issues with the shell extension #18650

@xenobytezero commented on GitHub (Oct 12, 2022):

I actually only noticed this when setting up a new clean work machine, so the amount of customisation is minimal.

The only thing I run of that type is 7+ Taskbar Tweaker, but afaik that doesn't touch the context menu at all.

@xenobytezero commented on GitHub (Oct 12, 2022): I actually only noticed this when setting up a new clean work machine, so the amount of customisation is minimal. The only thing I run of that type is [7+ Taskbar Tweaker](https://ramensoftware.com/7-taskbar-tweaker), but afaik that doesn't touch the context menu at all.

claunia commented

@DHowett commented on GitHub (Oct 13, 2022):

Ah, thanks. And just to confirm, you really are running 20H1 (build number 19041) and not a newer version?

@DHowett commented on GitHub (Oct 13, 2022): Ah, thanks. And just to confirm, you really are running _20H1_ (build number `19041`) and not a newer version?

claunia commented

@xenobytezero commented on GitHub (Oct 14, 2022):

I'm running 20H2, version 19042.508.

@xenobytezero commented on GitHub (Oct 14, 2022): I'm running 20H2, version 19042.508.

claunia commented

@DHowett commented on GitHub (Oct 17, 2022):

Update 1.15.2874/2875 is rolling out to the store right now; we included a quick fix for a crash in the shell extension that might be causing some trouble. I'm wondering if it helps you too :)

@DHowett commented on GitHub (Oct 17, 2022): Update 1.15.2874/2875 is rolling out to the store right now; we included a quick fix for a _crash_ in the shell extension that might be causing some trouble. I'm wondering if it helps you too :)

claunia commented

@xenobytezero commented on GitHub (Oct 19, 2022):

Updating to 1.15.2874.0 does not appear to have fixed the issue, presenting the same as above.

@xenobytezero commented on GitHub (Oct 19, 2022): Updating to 1.15.2874.0 does not appear to have fixed the issue, presenting the same as above.

claunia commented

@zadjii-msft commented on GitHub (Oct 26, 2022):

@xenobytezero Just to be sure, have you restarted the machine (more specifically, restarted explorer.exe) since the update? Explorer's been known to cache these sorts of things until a restart

@zadjii-msft commented on GitHub (Oct 26, 2022): @xenobytezero Just to be sure, have you restarted the machine (more specifically, restarted explorer.exe) since the update? Explorer's been known to cache these sorts of things until a restart

claunia commented

@xenobytezero commented on GitHub (Oct 28, 2022):

Reasonably sure I had restarted multiple times, but will confirm at the start of the week when I am back in the office.

@xenobytezero commented on GitHub (Oct 28, 2022): Reasonably sure I had restarted multiple times, but will confirm at the start of the week when I am back in the office.

claunia commented

@xenobytezero commented on GitHub (Nov 1, 2022):

Can confirm that multiple restarts does not fix the issue.

@xenobytezero commented on GitHub (Nov 1, 2022): Can confirm that multiple restarts does not fix the issue.

claunia commented

@vladhietala commented on GitHub (Nov 22, 2022):

I also have this issue, fresh install of windows, connected through azure AD and Intune, heavily limited. I installed Windows Terminal via Winget (because the company limits which apps can be installed via the Windows Store) using both Msstore and Winget sources.

Edition	Windows 10 Enterprise
Version	21H2
Installed on	‎13/‎10/‎2022
OS build	19044.2130
Experience	Windows Feature Experience Pack 120.2212.4180.0

Windows Terminal Preview
Version: 1.16.2641.0

Windows Terminal
Version: 1.15.2874.0

On background:

On folder:

@vladhietala commented on GitHub (Nov 22, 2022): I also have this issue, fresh install of windows, connected through azure AD and Intune, heavily limited. I installed Windows Terminal via Winget (because the company limits which apps can be installed via the Windows Store) using both Msstore and Winget sources. ``` Edition Windows 10 Enterprise Version 21H2 Installed on ‎13/‎10/‎2022 OS build 19044.2130 Experience Windows Feature Experience Pack 120.2212.4180.0 ``` ``` Windows Terminal Preview Version: 1.16.2641.0 ``` ``` Windows Terminal Version: 1.15.2874.0 ``` On background: ![image](https://user-images.githubusercontent.com/3045903/203400992-5d349351-4dfb-478c-88a0-ec41c1a5d8e4.png) On folder: ![image](https://user-images.githubusercontent.com/3045903/203401153-e83e2930-5191-44d5-b8a2-ceaeb6dfaf63.png)

claunia commented

@zadjii-msft commented on GitHub (Nov 22, 2022):

Related threads:

We may want to just de-dupe all these

edit: addenda

MSFT:24623699
MSFT:29893761
MSFT:28916295

@zadjii-msft commented on GitHub (Nov 22, 2022): Related threads: * #10694 * #10496 * #10119 * #16605 We may want to just de-dupe all these ----- edit: addenda * MSFT:24623699 * MSFT:29893761 * MSFT:28916295

claunia commented

@vladhietala commented on GitHub (Nov 22, 2022):

Tested on another company laptop (W10 Pro 21H2 19044.2251), connected through AD domain, old Windows installation. I installed Terminal from the store and "Open in Terminal" appears OK both in backgound and folder when RMBing.

@vladhietala commented on GitHub (Nov 22, 2022): Tested on another company laptop (W10 Pro 21H2 19044.2251), connected through AD domain, old Windows installation. I installed Terminal from the store and "Open in Terminal" appears OK both in backgound and folder when RMBing.

claunia commented

@zadjii-msft commented on GitHub (Nov 22, 2022):

@vladhietala weird question, are both machines using the same language settings?

@zadjii-msft commented on GitHub (Nov 22, 2022): @vladhietala weird question, are both machines using the same language settings?

claunia commented

@vladhietala commented on GitHub (Nov 22, 2022):

@vladhietala weird question, are both machines using the same language settings?

Both are in English with some regional settings in Brazilian Portuguese. I'm not sure, but I think the original language of W10Enterprise was Brazilian Portuguese and I change to English in intial configuration. In other hand W10Pro was installed initially in English, because I installed and this was my old working laptop.

@vladhietala commented on GitHub (Nov 22, 2022): > @vladhietala weird question, are both machines using the same language settings? Both are in English with some regional settings in Brazilian Portuguese. I'm not sure, but I think the original language of W10Enterprise was Brazilian Portuguese and I change to English in intial configuration. In other hand W10Pro was installed initially in English, because I installed and this was my old working laptop.

claunia commented

@jackthepanisher commented on GitHub (Dec 18, 2022):

I have the same issue on a new notebook with a fresh Windows 10 installation. RMB on a folder works but RMB on just the background doesn't show "Open in Terminal". The initial installation was 21H2 but I upgraded to 22H2 recently. Version of Windows Terminal is 1.15.3465.0 but I tried different older versions as well. I use plenty of other systems (VM/non-VM) where it works correctly but I can't find any hint why this does not work on that particular system.

I tried to debug the problem using WinDbg and break into when WindowsTerminalShellExt.dll is loaded from the dllhost process (COM surrogate) created by svchost. All I can observe is that there is no dllhost process created with RMB on the background at the problematic system while on a working system it is created. This can already be seen by just watching all dllhost processes with Process Explorer.

@jackthepanisher commented on GitHub (Dec 18, 2022): I have the same issue on a new notebook with a fresh Windows 10 installation. RMB on a folder works but RMB on just the background doesn't show "Open in Terminal". The initial installation was 21H2 but I upgraded to 22H2 recently. Version of Windows Terminal is 1.15.3465.0 but I tried different older versions as well. I use plenty of other systems (VM/non-VM) where it works correctly but I can't find any hint why this does not work on that particular system. I tried to debug the problem using WinDbg and break into when WindowsTerminalShellExt.dll is loaded from the dllhost process (COM surrogate) created by svchost. All I can observe is that there is no dllhost process created with RMB on the background at the problematic system while on a working system it is created. This can already be seen by just watching all dllhost processes with Process Explorer.

claunia commented

@piomis commented on GitHub (Jan 26, 2023):

Same effect on my side (RMB on folder works, RMB on background does not). I have some other extensions install (see screen shot).

OS Name: Windows 10 Enterprise
Version: 10.0.19045

Windows Terminal Preview Version: 1.17.1023

@piomis commented on GitHub (Jan 26, 2023): Same effect on my side (RMB on folder works, RMB on background does not). I have some other extensions install (see screen shot). ![image](https://user-images.githubusercontent.com/29480839/214785936-9ddf8240-54f2-4436-8210-e32acd49a878.png) OS Name: Windows 10 Enterprise Version: 10.0.19045 Windows Terminal Preview Version: 1.17.1023

claunia commented

@matthuisman commented on GitHub (Jan 31, 2023):

also seeing same issue

22H2
terminal version 1.15.3465.0

right click on a folder OK
right click in empty space of a folder = no option

@matthuisman commented on GitHub (Jan 31, 2023): also seeing same issue 22H2 terminal version 1.15.3465.0 right click on a folder OK right click in empty space of a folder = no option

claunia commented

@htcfreek commented on GitHub (Feb 7, 2023):

I have the same after installing wt on my new work computer and a new vm. I installed v1.15 as APPX provisioning package on W10 21H2.

Windows 10 21H2 German (with and without EN-US language pack).
WT 1.15.*
Istall method: As AppX provision package using the ofline install source.

@htcfreek commented on GitHub (Feb 7, 2023): I have the same after installing wt on my new work computer and a new vm. I installed v1.15 as APPX provisioning package on W10 21H2. - Windows 10 21H2 German (with and without EN-US language pack). - WT 1.15.* - Istall method: As AppX provision package using the ofline install source.

claunia commented

@auxym commented on GitHub (Feb 8, 2023):

Similar issue here. I get "open in terminal" option when right-clicking on a folder in Explorer, but not when right-clicking in an empty area within a folder, which would be useful.

Tried both Terminal and Terminal Preview (separately)
Installed from Windows Store
Windows 10 Education 22H2 19045.2486

@auxym commented on GitHub (Feb 8, 2023): Similar issue here. I get "open in terminal" option when right-clicking on a folder in Explorer, but *not* when right-clicking in an empty area within a folder, which would be useful. - Tried both Terminal and Terminal Preview (separately) - Installed from Windows Store - Windows 10 Education 22H2 19045.2486

claunia commented

@jfichtner commented on GitHub (Apr 5, 2023):

Are there any workarounds for this issue? I have been having it for months, and it frustrates me every multiple times a day! :-/

@jfichtner commented on GitHub (Apr 5, 2023): Are there any workarounds for this issue? I have been having it for months, and it frustrates me every multiple times a day! :-/

claunia commented

@Aetylus commented on GitHub (May 12, 2023):

Also having similar issues, where the context menu appears when right-clicking a folder but not anywhere else. I've attempted reinstalling Windows Terminal both through the Microsoft Store and winget as well as multiple restarts of the computer and Windows Explorer, to no avail. Currently on:

Windows Terminal 1.16.10261.0
Windows 10 Enterprise 22H2 (19045.2965)

However, I also tried Windows Terminal Preview 1.17.1023, which behaves the same in regards to the context menu issues.

@Aetylus commented on GitHub (May 12, 2023): Also having similar issues, where the context menu appears when right-clicking a folder but not anywhere else. I've attempted reinstalling Windows Terminal both through the Microsoft Store and `winget` as well as multiple restarts of the computer and Windows Explorer, to no avail. Currently on: * Windows Terminal 1.16.10261.0 * Windows 10 Enterprise 22H2 (19045.2965) However, I also tried Windows Terminal Preview 1.17.1023, which behaves the same in regards to the context menu issues.

claunia commented

@zadjii-msft commented on GitHub (May 12, 2023):

I'm almost certain that this is just something that was broken in the OS, and fixed in Windows 11. Like, the OS straight up refuses to load for Directory\Background entries. Someone'll need to do some digging through the history to confirm that.... MSFT:28916295 seems to suggest that this should have been fixed and backported though...

@zadjii-msft commented on GitHub (May 12, 2023): I'm almost certain that this is just something that was broken in the OS, and fixed in Windows 11. Like, the OS straight up refuses to load for `Directory\Background` entries. Someone'll need to do some digging through the history to confirm that.... MSFT:28916295 seems to suggest that this should have been fixed and backported though...

claunia commented

@jackthepanisher commented on GitHub (May 12, 2023):

Not so sure about that. I have multiple systems on Windows 10 that don't have this issue. Only one particular system has this problem.

@jackthepanisher commented on GitHub (May 12, 2023): Not so sure about that. I have multiple systems on Windows 10 that don't have this issue. Only one particular system has this problem.

claunia commented

@diripirate commented on GitHub (Feb 2, 2024):

Same problem with 1.19.10302.

When I first installed it, the right click was working ok, but I think that it disappeared after an update of powertoys... But I'm not 100% sure, I tried also uninstalling powertoys and reinstalling terminal but the context menu doesn't come back

@diripirate commented on GitHub (Feb 2, 2024): Same problem with 1.19.10302. When I first installed it, the right click was working ok, but I think that it disappeared after an update of powertoys... But I'm not 100% sure, I tried also uninstalling powertoys and reinstalling terminal but the context menu doesn't come back

claunia commented

@hugo9655 commented on GitHub (Feb 8, 2024):

I am also having this issue but on LTSC only, specifically Windows 10 IoT Enterprise LTSC 2021, though it might be an issue across all editions. Installing Terminal application should add "open in terminal" to the context menu but does not.

More info: after installing Terminal from MS Store, you have to restart explorer.exe for the context menu to update. After, you will notice the context menu item missing when trying to right click in the current working directory, like the desktop, or by opening a folder and right clicking in the empty space. However, when right clicking a folder, "Open in Terminal" appears.

(adding here since this is the main thread)

@hugo9655 commented on GitHub (Feb 8, 2024): I am also having this issue but on LTSC only, specifically Windows 10 IoT Enterprise LTSC 2021, though it might be an issue across all editions. Installing Terminal application should add "open in terminal" to the context menu but does not. More info: after installing Terminal from MS Store, you have to restart explorer.exe for the context menu to update. After, you will notice the context menu item missing when trying to right click in the current working directory, like the desktop, or by opening a folder and right clicking in the empty space. However, when right clicking a folder, "Open in Terminal" appears. (adding here since this is the main thread)

claunia commented

@jackthepanisher commented on GitHub (Feb 11, 2024):

I run out of patience and upgraded to Windows 11 on my particular system that had this issue. The right-click context menu is now working as expected. This was an in-line upgrade so nothing change regarding the installation of Windows Terminal. Also note that I use multiple other Windows 10 systems as well that don't show this problem.

@jackthepanisher commented on GitHub (Feb 11, 2024): I run out of patience and upgraded to Windows 11 on my particular system that had this issue. The right-click context menu is now working as expected. This was an in-line upgrade so nothing change regarding the installation of Windows Terminal. Also note that I use multiple other Windows 10 systems as well that don't show this problem.

claunia commented

@queenbiscuit311 commented on GitHub (Feb 20, 2024):

I am also having this issue but on LTSC only, specifically Windows 10 IoT Enterprise LTSC 2021, though it might be an issue across all editions. Installing Terminal application should add "open in terminal" to the context menu but does not.

More info: after installing Terminal from MS Store, you have to restart explorer.exe for the context menu to update. After, you will notice the context menu item missing when trying to right click in the current working directory, like the desktop, or by opening a folder and right clicking in the empty space. However, when right clicking a folder, "Open in Terminal" appears.

(adding here since this is the main thread)

exact same problem here on ltsc, havent seen this issue on windows 11 or normal windows 10, its just ltsc for me. wonder if its possible to make a workaround of some kind.

@queenbiscuit311 commented on GitHub (Feb 20, 2024): > I am also having this issue but on LTSC only, specifically Windows 10 IoT Enterprise LTSC 2021, though it might be an issue across all editions. Installing Terminal application should add "open in terminal" to the context menu but does not. > > More info: after installing Terminal from MS Store, you have to restart explorer.exe for the context menu to update. After, you will notice the context menu item missing when trying to right click in the current working directory, like the desktop, or by opening a folder and right clicking in the empty space. However, when right clicking a folder, "Open in Terminal" appears. > > (adding here since this is the main thread) exact same problem here on ltsc, havent seen this issue on windows 11 or normal windows 10, its just ltsc for me. wonder if its possible to make a workaround of some kind.

claunia commented

@hugo9655 commented on GitHub (Feb 20, 2024):

I am also having this issue but on LTSC only, specifically Windows 10 IoT Enterprise LTSC 2021, though it might be an issue across all editions. Installing Terminal application should add "open in terminal" to the context menu but does not.
More info: after installing Terminal from MS Store, you have to restart explorer.exe for the context menu to update. After, you will notice the context menu item missing when trying to right click in the current working directory, like the desktop, or by opening a folder and right clicking in the empty space. However, when right clicking a folder, "Open in Terminal" appears.
(adding here since this is the main thread)

exact same problem here on ltsc, havent seen this issue on windows 11 or normal windows 10, its just ltsc for me. wonder if its possible to make a workaround of some kind.

I'm curious to see if this will still be a problem on Win11 LTSC when that releases. I guess we will have to wait and see.

@hugo9655 commented on GitHub (Feb 20, 2024): > > I am also having this issue but on LTSC only, specifically Windows 10 IoT Enterprise LTSC 2021, though it might be an issue across all editions. Installing Terminal application should add "open in terminal" to the context menu but does not. > > More info: after installing Terminal from MS Store, you have to restart explorer.exe for the context menu to update. After, you will notice the context menu item missing when trying to right click in the current working directory, like the desktop, or by opening a folder and right clicking in the empty space. However, when right clicking a folder, "Open in Terminal" appears. > > (adding here since this is the main thread) > > exact same problem here on ltsc, havent seen this issue on windows 11 or normal windows 10, its just ltsc for me. wonder if its possible to make a workaround of some kind. I'm curious to see if this will still be a problem on Win11 LTSC when that releases. I guess we will have to wait and see.

claunia commented

@SkewelVsAll commented on GitHub (Feb 28, 2024):

@zadjii-msft I was wondeing - why can't you add a registry workaround for the context menu as an option to toggle on/off through Windows Terminal settings?

@SkewelVsAll commented on GitHub (Feb 28, 2024): @zadjii-msft I was wondeing - why can't you add a registry workaround for the context menu as an option to toggle on/off through Windows Terminal settings?

claunia commented

@Danipulok commented on GitHub (Feb 28, 2024):

@zadjii-msft I was wondering - why can't you add a registry workaround for the context menu as an option to toggle on/off through Windows Terminal settings?

Exactly my point. There should be option to add/remove Windows Terminal from context menu (via registry). I really wonder why it's still not done in 2 years, when it's such a simple option.

@Danipulok commented on GitHub (Feb 28, 2024): > @zadjii-msft I was wondering - why can't you add a registry workaround for the context menu as an option to toggle on/off through Windows Terminal settings? Exactly my point. There should be option to add/remove `Windows Terminal` from context menu (via registry). I really wonder why it's still not done in 2 years, when it's such a simple option.

claunia commented

@SkewelVsAll commented on GitHub (Feb 29, 2024):

@zadjii-msft I was wondering - why can't you add a registry workaround for the context menu as an option to toggle on/off through Windows Terminal settings?

Exactly my point. There should be option to add/remove Windows Terminal from context menu (via registry). I really wonder why it's still not done in 2 years, when it's such a simple option.

Yeah and also consider that there's just a year and a half worth of support remaining for Windows 10, either they'll do something to fix it on the Windows 10 context menu or solely focus on improving the application on Windows 11, so the registry workaround seems like a quick effortless one.

@SkewelVsAll commented on GitHub (Feb 29, 2024): > > @zadjii-msft I was wondering - why can't you add a registry workaround for the context menu as an option to toggle on/off through Windows Terminal settings? > > Exactly my point. There should be option to add/remove `Windows Terminal` from context menu (via registry). I really wonder why it's still not done in 2 years, when it's such a simple option. Yeah and also consider that there's just a year and a half worth of support remaining for Windows 10, either they'll do something to fix it on the Windows 10 context menu or solely focus on improving the application on Windows 11, so the registry workaround seems like a quick effortless one.

claunia commented

@zadjii-msft commented on GitHub (Feb 29, 2024):

you know what, having a manual escape hatch button isn't the worst idea. One that just yeets legacy style registrations into the registry. I don't hate that. I'm sure there'd be edge cases - namely, we can't really disable our manifested shell entries. So if you're getting those some of the time, and hit the "just give me the fucking context menu" button, then some of the time you'll see two entries for the Terminal. That's probably fine though - you knew what you were doing.

We discussed as a team yesterday and we're cool with that, if someone wanted to add that¹. Probably a toggle on the Interaction page of the settings? Hook it up to the registry instead of the settings model (ala, the default terminal dropdown). Presto, done.

given other team priorities, I'd guestimate that we wouldn't have time to get to this ourselves anytime soon ↩︎

@zadjii-msft commented on GitHub (Feb 29, 2024): ![ryan-point](https://github.com/microsoft/terminal/assets/18356694/4bee43df-79c8-47ae-af19-8ac2877ffb9e) you know what, having a manual escape hatch button isn't the worst idea. One that just yeets legacy style registrations into the registry. I don't hate that. I'm sure there'd be edge cases - namely, we can't really _disable_ our manifested shell entries. So if you're getting those _some of the time_, and hit the "just give me the fucking context menu" button, then _some of the time_ you'll see two entries for the Terminal. That's probably fine though - you knew what you were doing. We discussed as a team yesterday and we're cool with that, if someone wanted to add that[^1]. Probably a toggle on the Interaction page of the settings? Hook it up to the registry instead of the settings model (ala, the default terminal dropdown). Presto, done. [^1]: given other team priorities, I'd guestimate that we wouldn't have time to get to this ourselves anytime soon

claunia commented

@SkewelVsAll commented on GitHub (Mar 1, 2024):

you know what, having a manual escape hatch button isn't the worst idea. One that just yeets legacy style registrations into the registry. I don't hate that. I'm sure there'd be edge cases - namely, we can't really disable our manifested shell entries. So if you're getting those some of the time, and hit the "just give me the fucking context menu" button, then some of the time you'll see two entries for the Terminal. That's probably fine though - you knew what you were doing.

We discussed as a team yesterday and we're cool with that, if someone wanted to add that[^1]. Probably a toggle on the Interaction page of the settings? Hook it up to the registry instead of the settings model (ala, the default terminal dropdown). Presto, done.

That's alright with me, take your time and fix the issues slowly down the line, but I just hope it's fixed before Microsoft pulls the plug on Windows 10 in 2025.

@SkewelVsAll commented on GitHub (Mar 1, 2024): > ![ryan-point](https://github.com/microsoft/terminal/assets/18356694/4bee43df-79c8-47ae-af19-8ac2877ffb9e) > > > you know what, having a manual escape hatch button isn't the worst idea. One that just yeets legacy style registrations into the registry. I don't hate that. I'm sure there'd be edge cases - namely, we can't really _disable_ our manifested shell entries. So if you're getting those _some of the time_, and hit the "just give me the fucking context menu" button, then _some of the time_ you'll see two entries for the Terminal. That's probably fine though - you knew what you were doing. > > We discussed as a team yesterday and we're cool with that, if someone wanted to add that[^1]. Probably a toggle on the Interaction page of the settings? Hook it up to the registry instead of the settings model (ala, the default terminal dropdown). Presto, done. > That's alright with me, take your time and fix the issues slowly down the line, but I just hope it's fixed before Microsoft pulls the plug on Windows 10 in 2025.

claunia commented

@SkewelVsAll commented on GitHub (Mar 6, 2024):

@zadjii-msft Sorry for the inconvenience, but I submitted the Windows Terminal context menu issue through Feedback Hub on my copy of Windows 10 LTSC 2021, so just thought I'd inform you.

@SkewelVsAll commented on GitHub (Mar 6, 2024): @zadjii-msft Sorry for the inconvenience, but I submitted the Windows Terminal context menu issue through Feedback Hub on my copy of Windows 10 LTSC 2021, so just thought I'd inform you.

claunia commented

@Danipulok commented on GitHub (Mar 6, 2024):

@SkewelVsAll did you submit only issue or solution via registry too?
If it was solution, please share here too

@Danipulok commented on GitHub (Mar 6, 2024): @SkewelVsAll did you submit only issue or solution via registry too? If it was solution, please share here too

claunia commented

@SkewelVsAll commented on GitHub (Mar 6, 2024):

@SkewelVsAll did you submit only issue or solution via registry too?
If it was solution, please share here too

Nah, only an issue. Whatever registry workarounds I found so far seemed to be temporary and they seemed to have their own set of issues like the icon on the context menu disappearing etc.

If someone can provide a genuine reliable registry workaround it would be the WT team itself, because if you want to add registry entries on your own, it's gonna be a very long and unreliable process because Windows Terminal's installation path is heavily protected for some reason, so yeah the WT team might know why they did this, so it's better if they give us a registry workaround that complies with the same.

@SkewelVsAll commented on GitHub (Mar 6, 2024): > @SkewelVsAll did you submit only issue or solution via registry too? > If it was solution, please share here too Nah, only an issue. Whatever registry workarounds I found so far seemed to be temporary and they seemed to have their own set of issues like the icon on the context menu disappearing etc. If someone can provide a genuine reliable registry workaround it would be the WT team itself, because if you want to add registry entries on your own, it's gonna be a very long and unreliable process because Windows Terminal's installation path is heavily protected for some reason, so yeah the WT team might know why they did this, so it's better if they give us a registry workaround that complies with the same.

claunia commented

@Danipulok commented on GitHub (Mar 6, 2024):

@SkewelVsAll, got it, thanks.
So far I did this:

Windows Registry Editor Version 5.00

[HKEY_CLASSES_ROOT\Directory\Background\shell\wt]
@="Open in terminal Custom"
"_Icon"="%LOCALAPPDATA%\\Microsoft\\WindowsApps\\wt.ico"

[HKEY_CLASSES_ROOT\Directory\Background\shell\wt\command]
@="wt.exe -d ."

(Icon taken from https://raw.githubusercontent.com/microsoft/terminal/master/res/terminal.ico)
But for some reason it does nothing even with wt.exe command, even though cmd configured pretty similar (cmd.exe /s /k pushd "%V").
So if anyone knows what to put in the command there, please share, so at least people who found this issue know this fix.

Any way @zadjii-msft could help a bit, perhaps?

@Danipulok commented on GitHub (Mar 6, 2024): @SkewelVsAll, got it, thanks. So far I did this: ``` Windows Registry Editor Version 5.00 [HKEY_CLASSES_ROOT\Directory\Background\shell\wt] @="Open in terminal Custom" "_Icon"="%LOCALAPPDATA%\\Microsoft\\WindowsApps\\wt.ico" [HKEY_CLASSES_ROOT\Directory\Background\shell\wt\command] @="wt.exe -d ." ``` (Icon taken from `https://raw.githubusercontent.com/microsoft/terminal/master/res/terminal.ico`) But for some reason it does nothing even with `wt.exe` command, even though `cmd` configured pretty similar (`cmd.exe /s /k pushd "%V"`). So if anyone knows what to put in the command there, please share, so at least people who found this issue know this fix. Any way @zadjii-msft could help a bit, perhaps?

claunia commented

@jackthepanisher commented on GitHub (Mar 6, 2024):

@SkewelVsAll, got it, thanks. So far I did this:
...

This should work as intended using wt.exe -d .. Can you run the wt command normally?

For simplicity, you can also set the icon to C:\windows\system32\cmd.exe which would show the old cmd icon (using "Icon", not "_Icon").

@jackthepanisher commented on GitHub (Mar 6, 2024): > @SkewelVsAll, got it, thanks. So far I did this: > ... This should work as intended using `wt.exe -d .`. Can you run the `wt` command normally? For simplicity, you can also set the icon to `C:\windows\system32\cmd.exe` which would show the old cmd icon (using "Icon", not "_Icon").

claunia commented

@Danipulok commented on GitHub (Mar 11, 2024):

@jackthepanisher, hi. Thanks for trying to help!

What works:

cmd
cd /d D:\Temp
wt.exe -d . (works and opens current dir)
wt -d . (works and opens current dir)

But when I write wt into folder path (as usually done with cmd), it freezes too.
Here's what I mean.

cmd:

wt:

It changes wt to this immediately, changes cursor to processing (spinning blue circle), but after 5-10 seconds stops and does nothing...

@Danipulok commented on GitHub (Mar 11, 2024): @jackthepanisher, hi. Thanks for trying to help! What works: > `cmd` > `cd /d D:\Temp` > `wt.exe -d .` (works and opens current dir) > `wt -d .` (works and opens current dir) But when I write `wt` into folder path (as usually done with `cmd`), it freezes too. Here's what I mean. `cmd`: ![image](https://github.com/microsoft/terminal/assets/45077699/64f43030-f013-4aee-85a3-7f43777da245) ![image](https://github.com/microsoft/terminal/assets/45077699/043ce11e-7e32-4454-9d67-4f531b2ddf02) ![image](https://github.com/microsoft/terminal/assets/45077699/1f6053c3-eaf5-4054-8a3b-61ee28766aa1) `wt`: ![image](https://github.com/microsoft/terminal/assets/45077699/8f7195e4-a4f0-4403-aaa6-08a738b1d0ce) It changes `wt` to this immediately, changes cursor to `processing` (spinning blue circle), but after 5-10 seconds stops and does nothing...

claunia commented

@jackthepanisher commented on GitHub (Mar 11, 2024):

@Danipulok this looks like a different issue to me.

I have installed Win10 LTSC into a virtual environment, updated to build 19044.4046 and installed Windows Terminal 1.19.10573.0. The problem with the right-click menu was reproducible with this setup and I was able to work around it using the registry entry. Putting wt or cmd into the Explorer address bar works without problems there. For reference, $PSVersionTable shows version 5.1.19041.4046 for the Powershell on that system.

@jackthepanisher commented on GitHub (Mar 11, 2024): @Danipulok this looks like a different issue to me. I have installed Win10 LTSC into a virtual environment, updated to build 19044.4046 and installed Windows Terminal 1.19.10573.0. The problem with the right-click menu was reproducible with this setup and I was able to work around it using the registry entry. Putting `wt` or `cmd` into the Explorer address bar works without problems there. For reference, `$PSVersionTable` shows version 5.1.19041.4046 for the Powershell on that system.

claunia commented

@ledlamp commented on GitHub (Oct 8, 2024):

Windows 10 IoT Enterprise LTSC no context menu option when I right click a background :( but there is when I right-click a folder

@ledlamp commented on GitHub (Oct 8, 2024): Windows 10 IoT Enterprise LTSC no context menu option when I right click a background :( but there is when I right-click a folder

claunia commented