-
Notifications
You must be signed in to change notification settings - Fork 8.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Continued issues with the shell extension #14185
Comments
@xenobytezero are you using any other shell extensions, explorer hooks, taskbar replacements etc. that you can think of? |
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. |
Ah, thanks. And just to confirm, you really are running 20H1 (build number |
I'm running 20H2, version 19042.508. |
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 :) |
Updating to 1.15.2874.0 does not appear to have fixed the issue, presenting the same as above. |
@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 |
Reasonably sure I had restarted multiple times, but will confirm at the start of the week when I am back in the office. |
Can confirm that multiple restarts does not fix the issue. |
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.
|
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 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. |
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. |
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 |
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. |
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 |
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) |
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. |
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. |
@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? |
Exactly my point. There should be option to add/remove |
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. |
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 that1. 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. Footnotes
|
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. |
@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 did you submit only issue or solution via registry 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, got it, thanks.
(Icon taken from Any way @zadjii-msft could help a bit, perhaps? |
This should work as intended using For simplicity, you can also set the icon to |
@jackthepanisher, hi. Thanks for trying to help! What works:
But when I write
|
@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 |
Windows 10 IoT Enterprise LTSC no context menu option when I right click a background :( but there is when I right-click a folder |
OK, keep the feature! |
I have updated to Terminal Preview 1.16.2641.0 and am still not seeing "Open in Terminal Preview" anywhere except when RMBing on a folder. Does not appear when clicking in the background of a folder, or on the desktop, which both should theoretically be fixed according to the commit
From Win10 20H2
Originally posted by @xenobytezero in #13977 (comment)
The text was updated successfully, but these errors were encountered: