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

Installing Windows Terminal changes the behavior of Start menu #9928

New Issue
Closed
opened 2026-01-31 02:07:40 +00:00 by claunia · 29 comments
claunia commented 2026-01-31 02:07:40 +00:00
Owner
Copy Link

Originally created by @oruponu on GitHub (Jul 30, 2020).

Environment

Windows build number: 10.0.19041.0
Windows Terminal version (if applicable): 1.1.2021.0

Steps to reproduce

  1. Open Start menu.
  2. Click on pinned folder tile or click on folder icon in the bottom left corner (Documents, Pictures, etc.) to open it.
    Settings icon in the bottom left corner and Application tiles are not affected.

Expected behavior

Start menu will automatically close and Explorer will open.

Actual behavior

Start menu will remain open and Explorer will open.

I uninstall Windows Terminal and confirmed that Start menu works as expected.
I also confirmed that the same issue occurs on other computers.

Originally created by @oruponu on GitHub (Jul 30, 2020). # Environment ```none Windows build number: 10.0.19041.0 Windows Terminal version (if applicable): 1.1.2021.0 ``` # Steps to reproduce 1. Open Start menu. 2. Click on pinned folder tile or click on folder icon in the bottom left corner (Documents, Pictures, etc.) to open it. Settings icon in the bottom left corner and Application tiles are not affected. # Expected behavior Start menu will automatically close and Explorer will open. # Actual behavior Start menu will remain open and Explorer will open. *** I uninstall Windows Terminal and confirmed that Start menu works as expected. I also confirmed that the same issue occurs on other computers.
claunia commented 2026-01-31 02:07:41 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Jul 31, 2020):

Well that's totally crazy. I don't have the faintest idea why that might happen. I also can't repro this locally, so I can't really investigate this further. Did this happen with previous version of the Terminal? Or only after upgrading to 1.1?

@zadjii-msft commented on GitHub (Jul 31, 2020): Well that's totally crazy. I don't have the faintest idea why that might happen. I also can't repro this locally, so I can't really investigate this further. Did this happen with previous version of the Terminal? Or only after upgrading to 1.1?
claunia commented 2026-01-31 02:07:41 +00:00
Author
Owner
Copy Link

@fran-f commented on GitHub (Jul 31, 2020):

I can see this on two different PCs. I think both are running Windows 10.0.18363.959.

The issue appears with Terminal 1.1, installed from store or package, but not with 1.0 (at least installed with package). It presents itself immediately after installation, no need to launch Terminal once.

(Unfortunately I also discovered that if you uninstall Terminal your configuration is deleted...)

@fran-f commented on GitHub (Jul 31, 2020): I can see this on two different PCs. I think both are running Windows 10.0.18363.959. The issue appears with Terminal 1.1, installed from store or package, but not with 1.0 (at least installed with package). It presents itself immediately after installation, no need to launch Terminal once. (Unfortunately I also discovered that if you uninstall Terminal your configuration is deleted...)
claunia commented 2026-01-31 02:07:41 +00:00
Author
Owner
Copy Link

@DHowett commented on GitHub (Jul 31, 2020):

This is wild. I can reproduce this! As stated, it only repros with 1.1+, and I have the sneaking suspicion that it's related to the shell extension.

Seems like a platform issue. I'll see if I can set up a minimal repro.

@DHowett commented on GitHub (Jul 31, 2020): This is wild. I can reproduce this! As stated, it only repros with 1.1+, and I have the sneaking suspicion that it's related to the shell extension. Seems like a platform issue. I'll see if I can set up a minimal repro.
claunia commented 2026-01-31 02:07:41 +00:00
Author
Owner
Copy Link

@fran-f commented on GitHub (Jul 31, 2020):

Is the shell extension enabled by default? I don't see an entry in the context menu.

@fran-f commented on GitHub (Jul 31, 2020): Is the shell extension enabled by default? I don't see an entry in the context menu.
claunia commented 2026-01-31 02:07:42 +00:00
Author
Owner
Copy Link

@DHowett commented on GitHub (Jul 31, 2020):

@fran-f yes, but due to a Windows issue it's not available if you right-click in the empty space in a directory window. Until that bug is fixed, it's only available if you actually right-click on a directory.

@DHowett commented on GitHub (Jul 31, 2020): @fran-f yes, but due to a Windows issue it's not available if you right-click in the empty space in a directory window. Until that bug is fixed, it's only available if you actually right-click _on a directory_.
claunia commented 2026-01-31 02:07:42 +00:00
Author
Owner
Copy Link

@fran-f commented on GitHub (Jul 31, 2020):

I see! Then it's active, I can see the entry right-clicking on directories. However I can't find it in ShellExView, so I can't try to disable it.

@fran-f commented on GitHub (Jul 31, 2020): I see! Then it's active, I can see the entry right-clicking on directories. However I can't find it in [ShellExView](http://www.nirsoft.net/utils/shexview.html), so I can't try to disable it.
claunia commented 2026-01-31 02:07:42 +00:00
Author
Owner
Copy Link

@DHowett commented on GitHub (Jul 31, 2020):

Yeah, packaged shell extensions are (we're learning!) very unusual. Somebody suggested a workaround (to disable it) here: https://github.com/microsoft/terminal/issues/7008#issuecomment-662621638. You'll almost certainly need to restart Explorer.

@DHowett commented on GitHub (Jul 31, 2020): Yeah, packaged shell extensions are (we're learning!) very unusual. Somebody suggested a workaround (to disable it) here: https://github.com/microsoft/terminal/issues/7008#issuecomment-662621638. You'll almost certainly need to restart Explorer.
claunia commented 2026-01-31 02:07:42 +00:00
Author
Owner
Copy Link

@fran-f commented on GitHub (Jul 31, 2020):

Following that workaround caused a curious restart loop in Explorer, but after a logout the extension is disabled, and the issue with the start menu is gone.

@fran-f commented on GitHub (Jul 31, 2020): Following that workaround caused a curious restart loop in Explorer, but after a logout the extension is disabled, and the issue with the start menu is gone.
claunia commented 2026-01-31 02:07:42 +00:00
Author
Owner
Copy Link

@DHowett commented on GitHub (Jul 31, 2020):

Thanks for confirming!

@DHowett commented on GitHub (Jul 31, 2020): Thanks for confirming!
claunia commented 2026-01-31 02:07:43 +00:00
Author
Owner
Copy Link

@oruponu commented on GitHub (Aug 1, 2020):

Thank you.
I have also confirmed that the Start menu works as expected with that workaround.

@oruponu commented on GitHub (Aug 1, 2020): Thank you. I have also confirmed that the Start menu works as expected with that workaround.
claunia commented 2026-01-31 02:07:43 +00:00
Author
Owner
Copy Link

@fran-f commented on GitHub (Aug 29, 2020):

As a shortcut to enable or disable the shell extension, one can use a .reg file. I can't upload them to GitHub, but I'll dump them here if anyone needs them. Create the file you need and run it to apply the changes to the Registry.

disable-windows-terminal-shell-extension.reg

Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Shell Extensions\Blocked]
"{9F156763-7844-4DC4-B2B1-901F640F5155}"="WindowsTerminal"

re-enable-windows-terminal-shell-extension.reg

Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Shell Extensions\Blocked]
"{9F156763-7844-4DC4-B2B1-901F640F5155}"=-
@fran-f commented on GitHub (Aug 29, 2020): As a shortcut to enable or disable the shell extension, one can use a `.reg` file. I can't upload them to GitHub, but I'll dump them here if anyone needs them. Create the file you need and run it to apply the changes to the Registry. `disable-windows-terminal-shell-extension.reg` ``` Windows Registry Editor Version 5.00 [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Shell Extensions\Blocked] "{9F156763-7844-4DC4-B2B1-901F640F5155}"="WindowsTerminal" ``` `re-enable-windows-terminal-shell-extension.reg` ``` Windows Registry Editor Version 5.00 [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Shell Extensions\Blocked] "{9F156763-7844-4DC4-B2B1-901F640F5155}"=- ```
claunia commented 2026-01-31 02:07:43 +00:00
Author
Owner
Copy Link

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

Just linking this to the internal thread: MSFT:32962688

@zadjii-msft commented on GitHub (Apr 29, 2021): Just linking this to the internal thread: MSFT:32962688
claunia commented 2026-01-31 02:07:44 +00:00
Author
Owner
Copy Link

@Ronald-G-Andrade commented on GitHub (Sep 30, 2021):

Hello dear friends, just a reminder that this bug is still present in the latest stable version (v1.10.2383.0).
Click to open a pinned folder in the start menu (also in full-screen mode) won't close it.
Thank you very much 👍🏻

@Ronald-G-Andrade commented on GitHub (Sep 30, 2021): Hello dear friends, just a reminder that this bug is still present in the latest stable version (v1.10.2383.0). Click to open a pinned folder in the start menu (also in full-screen mode) won't close it. Thank you very much 👍🏻
claunia commented 2026-01-31 02:07:44 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Sep 30, 2021):

Yep. There's nothing the Terminal can do about this, it's a Start Menu bug. We'll make sure to update this thread when there is anything to share. The internal bug is still open, but this also doesn't repro on Windows 11 anymore, so I'd bet that this isn't something that ends up getting serviced back to Windows 10.

@zadjii-msft commented on GitHub (Sep 30, 2021): Yep. There's nothing the Terminal can do about this, it's a Start Menu bug. We'll make sure to update this thread when there is anything to share. The internal bug is still open, but this also doesn't repro on Windows 11 anymore, so I'd bet that this isn't something that ends up getting serviced back to Windows 10.
claunia commented 2026-01-31 02:07:44 +00:00
Author
Owner
Copy Link

@stjpInd commented on GitHub (Nov 26, 2021):

I haven't done any extensive testing, but it looks like the issue might be fixed now!
I'm currently on Windows 10 build 19044.1387 with Terminal 1.11.2921.0 installed (no registry workaround) and I don't see the broken Start menu behavior anymore. Pinned folders and search both work as expected.
My suspicion is that Microsoft may have fixed the bug around the same time they rolled out the new search with dark mode, but I couldn't say for certain.

@stjpInd commented on GitHub (Nov 26, 2021): I haven't done any extensive testing, but it looks like the issue might be fixed now! I'm currently on Windows 10 build 19044.1387 with Terminal 1.11.2921.0 installed (no registry workaround) and I don't see the broken Start menu behavior anymore. Pinned folders and search both work as expected. My suspicion is that Microsoft may have fixed the bug around the same time they rolled out the new search with dark mode, but I couldn't say for certain.
claunia commented 2026-01-31 02:07:44 +00:00
Author
Owner
Copy Link

@Ronald-G-Andrade commented on GitHub (Nov 26, 2021):

I haven't done any extensive testing, but it looks like the issue might be fixed now! I'm currently on Windows 10 build 19044.1387 with Terminal 1.11.2921.0 installed (no registry workaround) and I don't see the broken Start menu behavior anymore. Pinned folders and search both work as expected. My suspicion is that Microsoft may have fixed the bug around the same time they rolled out the new search with dark mode, but I couldn't say for certain.

It's true dear brother. I tested it and now it's working properly on Windows, either an app or folder, it opens normally by closing the start menu / start screen.

Now, I really hope that Microsoft won't mess up again, later we would fix it and say: ""A new feature"" jajaja

@Ronald-G-Andrade commented on GitHub (Nov 26, 2021): > I haven't done any extensive testing, but it looks like the issue might be fixed now! I'm currently on Windows 10 build 19044.1387 with Terminal 1.11.2921.0 installed (no registry workaround) and I don't see the broken Start menu behavior anymore. Pinned folders and search both work as expected. My suspicion is that Microsoft may have fixed the bug around the same time they rolled out the new search with dark mode, but I couldn't say for certain. It's true dear brother. I tested it and now it's working properly on Windows, either an app or folder, it opens normally by closing the start menu / start screen. Now, I really hope that Microsoft won't mess up again, later we would fix it and say: ""A new feature"" jajaja
claunia commented 2026-01-31 02:07:45 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Apr 5, 2022):

Alrighty folks, looks like the explorer team looked into this and found that it doesn't repro on Windows 11, so it must have been fixed as part of the Start Menu rejuvenation. Impossible to say which changelist as a part of that would have fixed this, so it's not gonna be possible to service that fix to Windows 10. Sorry about that.

If folks are seeing this on Windows 11 builds, ping us here on this thread and I can reopen the investigation with the explorer folks.

Thanks!

@zadjii-msft commented on GitHub (Apr 5, 2022): Alrighty folks, looks like the explorer team looked into this and found that it doesn't repro on Windows 11, so it must have been fixed as part of the Start Menu rejuvenation. Impossible to say which changelist as a part of that would have fixed this, so it's not gonna be possible to service that fix to Windows 10. Sorry about that. If folks are seeing this on Windows 11 builds, ping us here on this thread and I can reopen the investigation with the explorer folks. Thanks!
claunia commented 2026-01-31 02:07:45 +00:00
Author
Owner
Copy Link

@pgorod commented on GitHub (Apr 5, 2022):

Microsoft will continue to support at least one Windows 10 release until October 14, 2025.

... plus the usual years-long delays.

Is this really proper to just ditch Windows 10 bugs as "won't fix" at the current time? Isn't it too early for that?

This saddens me, this bug is really annoying, and it's not even something that only happens inside Windows Terminal, it affects the general OS experience. I am enjoying Terminal but this is making me seriously consider uninstalling it. Please reconsider.

@pgorod commented on GitHub (Apr 5, 2022): > Microsoft will continue to support at least one Windows 10 release until October 14, 2025. ... plus the usual years-long delays. Is this really proper to just ditch Windows 10 bugs as "won't fix" at the current time? Isn't it too early for that? This saddens me, this bug is really annoying, and it's not even something that only happens inside Windows Terminal, it affects the general OS experience. I am enjoying Terminal but this is making me seriously consider uninstalling it. Please reconsider.
claunia commented 2026-01-31 02:07:45 +00:00
Author
Owner
Copy Link

@DHowett commented on GitHub (Apr 5, 2022):

Please reconsider.

Unfortunately, it's just not our call. We only own the Terminal, the console subsystem, and the console driver... not parts of explorer or the start menu or the taskbar. We only have so much power over our peers. 😄

@DHowett commented on GitHub (Apr 5, 2022): > Please reconsider. Unfortunately, it's just not our call. We only own the Terminal, the console subsystem, and the console driver... not parts of explorer or the start menu or the taskbar. We only have so much power over our peers. :smile:
claunia commented 2026-01-31 02:07:45 +00:00
Author
Owner
Copy Link

@pgorod commented on GitHub (Apr 5, 2022):

Ok, fair enough, at least you can try telling them "people are complaining that there are still years of support for Windows 10 to exhaust before you get a right to start dropping bugs"

Windows 10 is not open-source and free, it's a commercial product that we paid for.

@pgorod commented on GitHub (Apr 5, 2022): Ok, fair enough, at least you can try telling them "people are complaining that there are still years of support for Windows 10 to exhaust before you get a right to start dropping bugs" Windows 10 is not open-source and free, it's a commercial product that we paid for.
claunia commented 2026-01-31 02:07:45 +00:00
Author
Owner
Copy Link

@merrickjeff commented on GitHub (Apr 5, 2022):

Microsoft will continue to support at least one Windows 10 release until October 14, 2025.

... plus the usual years-long delays.

Is this really proper to just ditch Windows 10 bugs as "won't fix" at the current time? Isn't it too early for that?

This saddens me, this bug is really annoying, and it's not even something that only happens inside Windows Terminal, it affects the general OS experience. I am enjoying Terminal but this is making me seriously consider uninstalling it. Please reconsider.

@pgorod Either of these fixes should work unless you really need that context menu:
https://github.com/microsoft/terminal/issues/7008#issuecomment-662621638
https://github.com/microsoft/terminal/issues/7122#issuecomment-683299285

@merrickjeff commented on GitHub (Apr 5, 2022): > > Microsoft will continue to support at least one Windows 10 release until October 14, 2025. > > ... plus the usual years-long delays. > > Is this really proper to just ditch Windows 10 bugs as "won't fix" at the current time? Isn't it too early for that? > > This saddens me, this bug is really annoying, and it's not even something that only happens inside Windows Terminal, it affects the general OS experience. I am enjoying Terminal but this is making me seriously consider uninstalling it. Please reconsider. @pgorod Either of these fixes should work unless you really need that context menu: https://github.com/microsoft/terminal/issues/7008#issuecomment-662621638 https://github.com/microsoft/terminal/issues/7122#issuecomment-683299285
claunia commented 2026-01-31 02:07:46 +00:00
Author
Owner
Copy Link

@hello-smile6 commented on GitHub (Apr 5, 2022):

Microsoft will continue to support at least one Windows 10 release until October 14, 2025.

... plus the usual years-long delays.
Is this really proper to just ditch Windows 10 bugs as "won't fix" at the current time? Isn't it too early for that?
This saddens me, this bug is really annoying, and it's not even something that only happens inside Windows Terminal, it affects the general OS experience. I am enjoying Terminal but this is making me seriously consider uninstalling it. Please reconsider.

@pgorod Either of these fixes should work unless you really need that context menu: #7008 (comment) #7122 (comment)

Any workarounds that don't require TPM 2.0?

@hello-smile6 commented on GitHub (Apr 5, 2022): > > > Microsoft will continue to support at least one Windows 10 release until October 14, 2025. > > > > > > ... plus the usual years-long delays. > > Is this really proper to just ditch Windows 10 bugs as "won't fix" at the current time? Isn't it too early for that? > > This saddens me, this bug is really annoying, and it's not even something that only happens inside Windows Terminal, it affects the general OS experience. I am enjoying Terminal but this is making me seriously consider uninstalling it. Please reconsider. > > @pgorod Either of these fixes should work unless you really need that context menu: [#7008 (comment)](https://github.com/microsoft/terminal/issues/7008#issuecomment-662621638) [#7122 (comment)](https://github.com/microsoft/terminal/issues/7122#issuecomment-683299285) Any workarounds that don't require TPM 2.0?
claunia commented 2026-01-31 02:07:46 +00:00
Author
Owner
Copy Link

@DHowett commented on GitHub (Apr 5, 2022):

Any workarounds that don't require TPM 2.0?

You literally quoted a message that called out two workarounds that don't require installing Windows 11.

@DHowett commented on GitHub (Apr 5, 2022): > Any workarounds that don't require TPM 2.0? You literally quoted a message that called out two workarounds that don't require _installing Windows 11._
claunia commented 2026-01-31 02:07:46 +00:00
Author
Owner
Copy Link

@DHowett commented on GitHub (Apr 5, 2022):

at least you can try telling them "people are complaining that there are still years of support for Windows 10 to exhaust before you get a right to start dropping bugs"

Sure can try!

@DHowett commented on GitHub (Apr 5, 2022): > at least you can try telling them "people are complaining that there are still years of support for Windows 10 to exhaust before you get a right to start dropping bugs" Sure can try!
claunia commented 2026-01-31 02:07:46 +00:00
Author
Owner
Copy Link

@hello-smile6 commented on GitHub (Apr 5, 2022):

Any workarounds that don't require TPM 2.0?

You literally quoted a message that called out two workarounds that don't require installing Windows 11.

Oh

@hello-smile6 commented on GitHub (Apr 5, 2022): > > Any workarounds that don't require TPM 2.0? > > You literally quoted a message that called out two workarounds that don't require _installing Windows 11._ Oh
claunia commented 2026-01-31 02:07:46 +00:00
Author
Owner
Copy Link

@dymanoid commented on GitHub (Apr 10, 2022):

Unfortunately, the suggested workarounds described above (disabling the wt shell extension) didn't work for me.
I can confirm there's no "Open in Windows Terminal" context menu item anymore, but the Start menu behavior is still broken (Windows 10 21H2 19044.1586).
I recently installed Visual Studio 2022 Community though, so there might be some other shell extensions causing this behavior. (It might be a coincidence, but I don't observe this behavior on another Windows 10 machine having Windows Terminal but no Visual Studio 2022 installed.)

@dymanoid commented on GitHub (Apr 10, 2022): Unfortunately, the suggested workarounds described above (disabling the wt shell extension) didn't work for me. I can confirm there's no "Open in Windows Terminal" context menu item anymore, but the Start menu behavior is still broken (Windows 10 21H2 19044.1586). I recently installed Visual Studio 2022 Community though, so there might be some other shell extensions causing this behavior. (It might be a coincidence, but I don't observe this behavior on another Windows 10 machine having Windows Terminal but no Visual Studio 2022 installed.)
claunia commented 2026-01-31 02:07:47 +00:00
Author
Owner
Copy Link

@FalconFour commented on GitHub (Sep 27, 2022):

I didn't even know there was a "open Terminal here" shell extension. I don't even use Windows Terminal - I just had it installed passively -- my habit is still to press the Windows key, type the letters "cmd", and hit Enter or Ctrl+Shift+Enter. Which, on random computers, for months now, had occasionally resulted in cmd (or any other application I open from the start menu) opening up, behind the start menu, leaving me to additionally close the start menu -- or worse, start interacting with the start menu with the keyboard instead of the application (I work very quickly sometimes - this usually happens in the span of 1 second or so).

So, Terminal was identified as the reason for this, eh? And the Terminal folks are like, "😊 haha well it's a Windows bug, we can't fix it"?

I had to become frustrated enough with this issue to even find a way to phrase it to search it - and then trust the absurd conclusion that an app I never use was causing it, and try uninstalling it (which fixed it, btw).

Thus, Terminal breaks Windows in a fairly ridiculous way, that makes it impossible to track down that it's the cause -- it makes a pretty serious case for "just don't use Terminal"! And I'm extremely happy to take that solution, since I didn't even use the software anyway!

What you DO have control over is not installing this "open terminal here" extension unless the user asks for it (I would absolutely not have wanted it), especially given the nature of this bug -- having been open for well over a year now, unmoved.

@FalconFour commented on GitHub (Sep 27, 2022): I didn't even know there was a "open Terminal here" shell extension. I don't even use Windows Terminal - I just had it installed passively -- my habit is still to press the Windows key, type the letters "cmd", and hit Enter or Ctrl+Shift+Enter. Which, on random computers, for months now, had occasionally resulted in cmd (or any other application I open from the start menu) opening up, behind the start menu, leaving me to additionally close the start menu -- or worse, start interacting with the start menu with the keyboard instead of the application (I work very quickly sometimes - this usually happens in the span of 1 second or so). So, Terminal was identified as the reason for this, eh? And the Terminal folks are like, "😊 haha well it's a Windows bug, we can't fix it"? I had to become frustrated enough with this issue to even find a way to phrase it to search it - and then trust the absurd conclusion that an app I never use was causing it, and try uninstalling it (which fixed it, btw). Thus, Terminal breaks Windows in a fairly ridiculous way, that makes it impossible to track down that it's the cause -- it makes a pretty serious case for "just don't use Terminal"! And I'm extremely happy to take that solution, since I didn't even use the software anyway! What you **DO** have control over is not installing this "open terminal here" extension unless the user asks for it (I would absolutely **not** have wanted it), especially given the nature of this bug -- having been open for well over a year now, unmoved.
claunia commented 2026-01-31 02:07:47 +00:00
Author
Owner
Copy Link

@michaelbunney commented on GitHub (Sep 30, 2022):

So the fix for the Windows 10 Start menu bug is to switch to Windows 11, which has stripped the Start menu of its most useful features? Guess I'll just live without Windows Terminal, because I can't live with Windows 11's version of the Start menu.

@michaelbunney commented on GitHub (Sep 30, 2022): So the fix for the Windows 10 Start menu bug is to switch to Windows 11, which has stripped the Start menu of its most useful features? Guess I'll just live without Windows Terminal, because I can't live with Windows 11's version of the Start menu.
claunia commented 2026-01-31 02:07:47 +00:00
Author
Owner
Copy Link

@WagnerGFX commented on GitHub (Sep 1, 2023):

Microsoft will continue to support at least one Windows 10 release until October 14, 2025.

... plus the usual years-long delays.
Is this really proper to just ditch Windows 10 bugs as "won't fix" at the current time? Isn't it too early for that?
This saddens me, this bug is really annoying, and it's not even something that only happens inside Windows Terminal, it affects the general OS experience. I am enjoying Terminal but this is making me seriously consider uninstalling it. Please reconsider.

@pgorod Either of these fixes should work unless you really need that context menu: #7008 (comment) #7122 (comment)

For those who really need the context menu (like me), I created a custom version in the registry that should do the same work, but without breaking the Start menu.

Just be mindful that this solution:

  1. Uses the Windows Powershell icon.
  2. Requires the "wt" alias, that only exist with the default Terminal installation.
  3. Will open in new tabs, whenever possible.

Customize as needed. Windows Terminal CLI arguments

Windows Terminal - Win10 Context Menu - Custom (Add).reg

Windows` Registry Editor Version 5.00

[HKEY_CLASSES_ROOT\Directory\Background\shell\WindowsTerminal]
@="Open Terminal here"
"Icon"="C:\\Windows\\System32\\WindowsPowerShell\\v1.0\\powershell.exe"

[HKEY_CLASSES_ROOT\Directory\Background\shell\WindowsTerminal\command]
@="wt -w 0 nt -d \"%v\""
@WagnerGFX commented on GitHub (Sep 1, 2023): > > > Microsoft will continue to support at least one Windows 10 release until October 14, 2025. > > > > > > ... plus the usual years-long delays. > > Is this really proper to just ditch Windows 10 bugs as "won't fix" at the current time? Isn't it too early for that? > > This saddens me, this bug is really annoying, and it's not even something that only happens inside Windows Terminal, it affects the general OS experience. I am enjoying Terminal but this is making me seriously consider uninstalling it. Please reconsider. > > @pgorod Either of these fixes should work unless you really need that context menu: [#7008 (comment)](https://github.com/microsoft/terminal/issues/7008#issuecomment-662621638) [#7122 (comment)](https://github.com/microsoft/terminal/issues/7122#issuecomment-683299285) For those who really need the context menu (like me), I created a custom version in the registry that should do the same work, but without breaking the Start menu. Just be mindful that this solution: 1) Uses the Windows Powershell icon. 2) Requires the "wt" alias, that only exist with the default Terminal installation. 3) Will open in new tabs, whenever possible. Customize as needed. [Windows Terminal CLI arguments](https://learn.microsoft.com/en-us/windows/terminal/command-line-arguments?tabs=windows) `Windows Terminal - Win10 Context Menu - Custom (Add).reg` ``` Windows` Registry Editor Version 5.00 [HKEY_CLASSES_ROOT\Directory\Background\shell\WindowsTerminal] @="Open Terminal here" "Icon"="C:\\Windows\\System32\\WindowsPowerShell\\v1.0\\powershell.exe" [HKEY_CLASSES_ROOT\Directory\Background\shell\WindowsTerminal\command] @="wt -w 0 nt -d \"%v\"" ```
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 Product-Terminal Resolution-Fix-Available Tracking-External
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#9928
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?