starred/terminal
1
0
Fork 0
mirror of https://github.com/microsoft/terminal.git synced 2026-02-04 05:35:20 +00:00
Code Issues 19.0k Packages Projects Releases 20 Wiki Activity

Explorer background context menu option missing #13833

New Issue
Open
opened 2026-01-31 03:53:26 +00:00 by claunia · 29 comments
claunia commented 2026-01-31 03:53:26 +00:00
Owner
Copy Link

Originally created by @JonathanLydall on GitHub (May 18, 2021).

Windows Terminal version (or Windows build number)

1.7.1033.0

Other Software

Windows 10, 20H2 (19042.985)

Steps to reproduce

Right-click on background of folder in Windows Explorer.

Expected Behavior

An Open in Windows Terminal option to be available, like on other computers:

image

Actual Behavior

Missing option to Open in Windows Terminal:

image

I DO however get the context menu option when right-clicking on a folder:

image

I have tried uninstalling and re-installing the app from the Microsoft Store and while it will remove and re-add the folder context-menu, the background context-menu does not get added.

Originally created by @JonathanLydall on GitHub (May 18, 2021). ### Windows Terminal version (or Windows build number) 1.7.1033.0 ### Other Software Windows 10, 20H2 (19042.985) ### Steps to reproduce Right-click on background of folder in Windows Explorer. ### Expected Behavior An _Open in Windows Terminal_ option to be available, like on other computers: ![image](https://user-images.githubusercontent.com/1290262/118640317-1ef39c00-b7d9-11eb-96ee-812aeed62ec9.png) ### Actual Behavior Missing option to _Open in Windows Terminal_: ![image](https://user-images.githubusercontent.com/1290262/118640429-3f235b00-b7d9-11eb-885e-1340ce4dc1ba.png) I _DO_ however get the context menu option when right-clicking on a folder: ![image](https://user-images.githubusercontent.com/1290262/118640623-798cf800-b7d9-11eb-81dd-c8dfd638b51d.png) I have tried uninstalling and re-installing the app from the Microsoft Store and while it will remove and re-add the folder context-menu, the background context-menu does not get added.
claunia commented 2026-01-31 03:53:27 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (May 18, 2021):

well that's weird, I could have sworn this was added in #8638, in 1.6. Judging by the comments in that thread, and in #8977, we even backported that feature to 1.5, so it should definitely be working...

@zadjii-msft commented on GitHub (May 18, 2021): well that's weird, I could have sworn this was added in #8638, in 1.6. Judging by the comments in that thread, and in #8977, we even backported that feature to 1.5, so it should definitely be working...
claunia commented 2026-01-31 03:53:28 +00:00
Author
Owner
Copy Link

@DHowett commented on GitHub (May 18, 2021):

How did you install Terminal?

@DHowett commented on GitHub (May 18, 2021): How did you install Terminal?
claunia commented 2026-01-31 03:53:28 +00:00
Author
Owner
Copy Link

@JonathanLydall commented on GitHub (May 18, 2021):

How did you install Terminal?

I installed it through the Microsoft Store app.

well that's weird, I could have sworn this was added in #8638, in 1.6. Judging by the comments in that thread, and in #8977, we even backported that feature to 1.5, so it should definitely be working...

Yep, seems weird to me too 🙂. I only knew about this as I saw the option on a different machine, then before logging the ticket, I installed it on a clean virtual machine to compare the behaviour and that works fine.

On the machine on which it's not working, I've tried uninstalling and re-installing the app and it unfortunately doesn't help.

I logged this issue because I don't know how to troubleshoot this further.

@JonathanLydall commented on GitHub (May 18, 2021): > How did you install Terminal? I installed it through the Microsoft Store app. > well that's weird, I could have sworn this was added in #8638, in 1.6. Judging by the comments in that thread, and in #8977, we even backported that feature to 1.5, so it should definitely be working... Yep, seems weird to me too 🙂. I only knew about this as I saw the option on a different machine, then before logging the ticket, I installed it on a clean virtual machine to compare the behaviour and that works fine. On the machine on which it's not working, I've tried uninstalling and re-installing the app and it unfortunately doesn't help. I logged this issue because I don't know how to troubleshoot this further.
claunia commented 2026-01-31 03:53:28 +00:00
Author
Owner
Copy Link

@pointydev commented on GitHub (May 29, 2021):

I'm having a similar issue with 1.9.1445.0 (pre) on Windows 21390 (also present on 21387, don't remember past that). The context menu entry won't show at all, even if right clicking directly on a folder, however it works fine if I have the stable build installed SXS. This is the case with both Store and MSIX install methods.

@pointydev commented on GitHub (May 29, 2021): I'm having a similar issue with 1.9.1445.0 (pre) on Windows 21390 (also present on 21387, don't remember past that). The context menu entry won't show at all, even if right clicking directly on a folder, however it works fine if I have the stable build installed SXS. This is the case with both Store and MSIX install methods.
claunia commented 2026-01-31 03:53:28 +00:00
Author
Owner
Copy Link

@rejhgadellaabsl commented on GitHub (Oct 8, 2021):

I can confirm that this still seems to be an issue on 1.10.2714.0 (stable), just installed WT and no "Open here..." context menu when I click inside a folder. I do get the option when I click on a folder entry.

@rejhgadellaabsl commented on GitHub (Oct 8, 2021): I can confirm that this still seems to be an issue on 1.10.2714.0 (stable), just installed WT and no "Open here..." context menu when I click inside a folder. I do get the option when I click on a folder entry.
claunia commented 2026-01-31 03:53:29 +00:00
Author
Owner
Copy Link

@JonathanLydall commented on GitHub (Oct 9, 2021):

It happens on my company computer, but not my personal. I can only think that maybe there is some policy applied by IT which is the cause of the issue.

Fortunately this is less of an issue since a recent set of updates to the company computer which fixed the folder context menu to pop up pretty much instantly whereas before it would take a couple of seconds.

@JonathanLydall commented on GitHub (Oct 9, 2021): It happens on my company computer, but not my personal. I can only think that maybe there is some policy applied by IT which is the cause of the issue. Fortunately this is less of an issue since a recent set of updates to the company computer which fixed the folder context menu to pop up pretty much instantly whereas before it would take a couple of seconds.
claunia commented 2026-01-31 03:53:29 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Dec 13, 2021):

Sorry to let this one hang on the backlog so long - @JonathanLydall, what version of the OS is your work machine running, still 19042.985? I think there were some OS-side changes that might have fixed this, but I don't recall what version they landed in.

@zadjii-msft commented on GitHub (Dec 13, 2021): Sorry to let this one hang on the backlog so long - @JonathanLydall, what version of the OS is your work machine running, still 19042.985? I think there were some OS-side changes that might have fixed this, but I don't recall what version they landed in.
claunia commented 2026-01-31 03:53:29 +00:00
Author
Owner
Copy Link

@JonathanLydall commented on GitHub (Dec 14, 2021):

Unfortunately my contract with that company has since ended so I don't have access to the computer any more. I can't recall the exact version it was running when I left (and it still had the issue), I think 20H2, but might have been 20H1.

@JonathanLydall commented on GitHub (Dec 14, 2021): Unfortunately my contract with that company has since ended so I don't have access to the computer any more. I can't recall the exact version it was running when I left (and it still had the issue), I think 20H2, but might have been 20H1.
claunia commented 2026-01-31 03:53:29 +00:00
Author
Owner
Copy Link

@mickedefault commented on GitHub (Dec 14, 2021):

@zadjii-msft I have the same issue. Running version 21H1 (19043.1348) at the moment. Let me know if I can help in verifying anything for you!

@mickedefault commented on GitHub (Dec 14, 2021): @zadjii-msft I have the same issue. Running version 21H1 (19043.1348) at the moment. Let me know if I can help in verifying anything for you!
claunia commented 2026-01-31 03:53:29 +00:00
Author
Owner
Copy Link

@lursyy commented on GitHub (Apr 22, 2022):

Same here. Unfortunately I cannot remember, but I think I originally installed WT via chocolatey, and then decided to uninstall and use the Store version instead, without any effect. I am using WT 1.12.10982.0 on Windows 10.0.19043 and happy to provide more info!

@lursyy commented on GitHub (Apr 22, 2022): Same here. Unfortunately I cannot remember, but I think I originally installed WT via chocolatey, and then decided to uninstall and use the Store version instead, without any effect. I am using WT 1.12.10982.0 on Windows 10.0.19043 and happy to provide more info!
claunia commented 2026-01-31 03:53:30 +00:00
Author
Owner
Copy Link

@lursyy commented on GitHub (Apr 22, 2022):

(How) does this relate to #11839?

@lursyy commented on GitHub (Apr 22, 2022): (How) does this relate to #11839?
claunia commented 2026-01-31 03:53:30 +00:00
Author
Owner
Copy Link

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

We suspect this may have gotten better with #14048 and #14211, in v1.15.2874. Then again, we are still seeing some reports of this in #14185. If this isn't happening any more for folks in this thread, we may want to close in favor of the new thread, to track any remaining issues with the new implementation. Sound good/?

@zadjii-msft commented on GitHub (Nov 22, 2022): We suspect this may have gotten better with #14048 and #14211, in v1.15.2874. Then again, we are still seeing some reports of this in #14185. If this isn't happening any more for folks in this thread, we may want to close in favor of the new thread, to track any remaining issues with the new implementation. Sound good/?
claunia commented 2026-01-31 03:53:30 +00:00
Author
Owner
Copy Link

@JonathanLydall commented on GitHub (Nov 23, 2022):

No concerns with closing from my side. Since I moved on from the company with the computer with the issue, I haven't encountered it on my new work or my personal computer.

@JonathanLydall commented on GitHub (Nov 23, 2022): No concerns with closing from my side. Since I moved on from the company with the computer with the issue, I haven't encountered it on my new work or my personal computer.
claunia commented 2026-01-31 03:53:30 +00:00
Author
Owner
Copy Link

@lesleyrs commented on GitHub (Apr 26, 2023):

I just had this happen to me after running winget uninstall Microsoft.PowerToys.

I'm not sure uninstalling powertoys is what caused it, but it seems likely. Windows 10.

Edit: re-installing windows terminal did not give me the context menu back... :(

@lesleyrs commented on GitHub (Apr 26, 2023): I just had this happen to me after running `winget uninstall Microsoft.PowerToys`. I'm not sure uninstalling powertoys is what caused it, but it seems likely. Windows 10. Edit: re-installing windows terminal did not give me the context menu back... :(
claunia commented 2026-01-31 03:53:31 +00:00
Author
Owner
Copy Link

@Zainzzkk commented on GitHub (May 5, 2023):

I have the same. I cannot install from windows store so used Windows Package Manager CLI. I cannot see it in the context menu

@Zainzzkk commented on GitHub (May 5, 2023): I have the same. I cannot install from windows store so used Windows Package Manager CLI. I cannot see it in the context menu
claunia commented 2026-01-31 03:53:31 +00:00
Author
Owner
Copy Link

@ne0-wu commented on GitHub (Aug 30, 2023):

To me, the "Open in Windows Terminal" feature is only visible within the new context menu of Windows 11. It does not appear in the traditional context menu, regardless of whether I attempt to access it through the shift + right-click method or by disabling the new context menu to exclusively use the right-click approach.

@ne0-wu commented on GitHub (Aug 30, 2023): To me, the "Open in Windows Terminal" feature is only visible within the new context menu of Windows 11. It does not appear in the traditional context menu, regardless of whether I attempt to access it through the shift + right-click method or by disabling the new context menu to exclusively use the right-click approach.
claunia commented 2026-01-31 03:53:31 +00:00
Author
Owner
Copy Link

@ne0-wu commented on GitHub (Aug 30, 2023):

To me, the "Open in Windows Terminal" feature is only visible within the new context menu of Windows 11. It does not appear in the traditional context menu, regardless of whether I attempt to access it through the shift + right-click method or by disabling the new context menu to exclusively use the right-click approach.

Furthermore, the option only becomes visible in the new context menu after I perform a shift + right-click. However, it consistently disappears with every system reboot.

@ne0-wu commented on GitHub (Aug 30, 2023): > To me, the "Open in Windows Terminal" feature is only visible within the new context menu of Windows 11. It does not appear in the traditional context menu, regardless of whether I attempt to access it through the shift + right-click method or by disabling the new context menu to exclusively use the right-click approach. Furthermore, the option only becomes visible in the new context menu after I perform a shift + right-click. However, it consistently disappears with every system reboot.
claunia commented 2026-01-31 03:53:31 +00:00
Author
Owner
Copy Link

@xenobytezero commented on GitHub (Aug 30, 2023):

I have still been having this issue with Win10, the solution for me (from https://github.com/microsoft/terminal/issues/10496#issuecomment-1611918247) was to install with Scoop. Works for me there.

@xenobytezero commented on GitHub (Aug 30, 2023): I have still been having this issue with Win10, the solution for me (from https://github.com/microsoft/terminal/issues/10496#issuecomment-1611918247) was to install with Scoop. Works for me there.
claunia commented 2026-01-31 03:53:32 +00:00
Author
Owner
Copy Link

@rafalkk commented on GitHub (Nov 2, 2023):

I have exactly the same problem as described in the 1st post. I think it happened after running winget upgrade --all.

I also had Microsoft.PowerToys installed as someone mentioned earlier.

@rafalkk commented on GitHub (Nov 2, 2023): I have exactly the same problem as described in the 1st post. I think it happened after running `winget upgrade --all`. I also had Microsoft.PowerToys installed as someone mentioned earlier.
claunia commented 2026-01-31 03:53:32 +00:00
Author
Owner
Copy Link

@CodeGenStudio commented on GitHub (Dec 8, 2023):

I have exactly the same problem as described in the 1st post. I think it happened after running winget upgrade --all.

I also had Microsoft.PowerToys installed as someone mentioned earlier.

I have done exactly both of these in my case - although I did get rid of PowerToys a while back.

EDIT: I did NOT mean to re-open this issue, just wanted to get this mentioned. @zadjii-msft please close if you deem fit.

@CodeGenStudio commented on GitHub (Dec 8, 2023): > I have exactly the same problem as described in the 1st post. I think it happened after running `winget upgrade --all`. > > I also had Microsoft.PowerToys installed as someone mentioned earlier. I have done exactly both of these in my case - although I did get rid of PowerToys a while back. EDIT: I did NOT mean to re-open this issue, just wanted to get this mentioned. @zadjii-msft please close if you deem fit.
claunia commented 2026-01-31 03:53:32 +00:00
Author
Owner
Copy Link

@CodeGenStudio commented on GitHub (Dec 9, 2023):

please close if you deem fit

No. dont. as has been mentioned by me and others ad nauseam, this is a valid and ongoing issue.

This issue is already referenced in another more accurate in it's problem description, what's the point of two of the same issues.

@CodeGenStudio commented on GitHub (Dec 9, 2023): > > please close if you deem fit > > No. dont. as has been mentioned by me and others ad nauseam, this is a valid and ongoing issue. This issue is already referenced in another more accurate in it's problem description, what's the point of two of the same issues.
claunia commented 2026-01-31 03:53:32 +00:00
Author
Owner
Copy Link

@3052 commented on GitHub (Dec 9, 2023):

your issue was already closed in favor of this one, please stop adding noise to this thread.

@3052 commented on GitHub (Dec 9, 2023): your issue was already closed in favor of this one, please stop adding noise to this thread.
claunia commented 2026-01-31 03:53:33 +00:00
Author
Owner
Copy Link

@CodeGenStudio commented on GitHub (Dec 9, 2023):

your issue was already closed in favor of this one, please stop adding noise to this thread.

Oh my bad... I was typing on the wrong issue. Thought this was the one I started (came from gmail notification). Sincere apologies.

@CodeGenStudio commented on GitHub (Dec 9, 2023): > your issue was already closed in favor of this one, please stop adding noise to this thread. Oh my bad... I was typing on the wrong issue. Thought this was the one I started (came from gmail notification). Sincere apologies.
claunia commented 2026-01-31 03:53:33 +00:00
Author
Owner
Copy Link

@ghost commented on GitHub (Feb 4, 2024):

I have the exact same issue on my machine. I am running version 1.19.10302.0 of WT, which I installed by executing the msix package downloaded from the releases section. My Windows version is 10.0.19045.3930. I can see the option when I right click on a folder, but I don't see it when I right click on the folder background.

@ghost commented on GitHub (Feb 4, 2024): I have the exact same issue on my machine. I am running version 1.19.10302.0 of WT, which I installed by executing the msix package downloaded from the releases section. My Windows version is 10.0.19045.3930. I can see the option when I right click on a folder, but I don't see it when I right click on the folder background.
claunia commented 2026-01-31 03:53:34 +00:00
Author
Owner
Copy Link

@3052 commented on GitHub (Feb 4, 2024):

reposting my fix from the other issue. first DON'T download the MsixBundle. instead just get the dumb zip file, like this:

https://github.com/microsoft/terminal/releases/download/v1.18.2822.0/Microsoft.WindowsTerminal_1.18.2822.0_x64.zip

extract to wherever, for example:

C:\terminal-1.18.2822.0

then save the below as INSTALL.REG:

Windows Registry Editor Version 5.00
[HKEY_CLASSES_ROOT\Directory\background\shell\terminal\command]
@="C:\\terminal-1.18.2822.0\\WindowsTerminal.exe"

and you can fix the starting folder like this:

{
   "profiles": {
      "defaults": {"startingDirectory": ""}
   }
}

done.

@3052 commented on GitHub (Feb 4, 2024): reposting my fix from the other issue. first DON'T download the MsixBundle. instead just get the dumb zip file, like this: <https://github.com/microsoft/terminal/releases/download/v1.18.2822.0/Microsoft.WindowsTerminal_1.18.2822.0_x64.zip> extract to wherever, for example: ~~~ C:\terminal-1.18.2822.0 ~~~ then save the below as INSTALL.REG: ~~~ Windows Registry Editor Version 5.00 [HKEY_CLASSES_ROOT\Directory\background\shell\terminal\command] @="C:\\terminal-1.18.2822.0\\WindowsTerminal.exe" ~~~ and you can fix the starting folder like this: ~~~json { "profiles": { "defaults": {"startingDirectory": ""} } } ~~~ done.
claunia commented 2026-01-31 03:53:34 +00:00
Author
Owner
Copy Link

@onurusluca commented on GitHub (Mar 14, 2025):

Yep having this problem. I've tried everything I could find. Still same. Before, installing it manually, it asked if I wanted to add but no more with the new installer.

@onurusluca commented on GitHub (Mar 14, 2025): Yep having this problem. I've tried everything I could find. Still same. Before, installing it manually, it asked if I wanted to add but no more with the new installer.
claunia commented 2026-01-31 03:53:34 +00:00
Author
Owner
Copy Link

@alkaid616 commented on GitHub (Aug 4, 2025):

It may be a registry conflict caused by OneDrive, but after uninstalling and reinstalling OneDrive, the Explorer background context menu option were displayed normally.

@alkaid616 commented on GitHub (Aug 4, 2025): It may be a registry conflict caused by OneDrive, but after uninstalling and reinstalling OneDrive, the Explorer background context menu option were displayed normally.
claunia commented 2026-01-31 03:53:35 +00:00
Author
Owner
Copy Link

@jhmaster2000 commented on GitHub (Aug 5, 2025):

I can tell you this has most definitely nothing to do with OneDrive, as I have had this issue for a while now, and never had OneDrive installed on my PC (ripped it clean out of the install ISO itself).

@jhmaster2000 commented on GitHub (Aug 5, 2025): I can tell you this has most definitely nothing to do with OneDrive, as I have had this issue for a while now, and never had OneDrive installed on my PC (ripped it clean out of the install ISO itself).
claunia commented 2026-01-31 03:53:35 +00:00
Author
Owner
Copy Link

@rtm516 commented on GitHub (Aug 16, 2025):

Having the same issue after upgrading to Win11, it was fine to start with then after a few reboots and updates it broke and I only get 'Open in Terminal' when right clicking a folder and not the background of a directory.
Win 11 24H2 26100.4946
Happy to test any debug versions or make any OS changes to test

Troubleshooting tried:

  • Re-install via microsoft store
  • Checked and the shell extension {9f156763-7844-4dc4-b2b1-901f640f5155} isnt marked a blocked
@rtm516 commented on GitHub (Aug 16, 2025): Having the same issue after upgrading to Win11, it was fine to start with then after a few reboots and updates it broke and I only get 'Open in Terminal' when right clicking a folder and not the background of a directory. Win 11 24H2 26100.4946 Happy to test any debug versions or make any OS changes to test Troubleshooting tried: - Re-install via microsoft store - Checked and the shell extension `{9f156763-7844-4dc4-b2b1-901f640f5155}` isnt marked a blocked
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 Area-ShellExtension Help Wanted Issue-Bug Needs-Repro Product-Terminal
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#13833
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?