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

"Open in Terminal" option in the Desktop context menu not visible on Windows 10 LTSC 2021 #21143

New Issue
Closed
opened 2026-01-31 07:34:23 +00:00 by claunia · 6 comments
claunia commented 2026-01-31 07:34:23 +00:00
Owner
Copy Link

Originally created by @SkewelVsAll on GitHub (Jan 26, 2024).

Originally assigned to: @DHowett on GitHub.

Windows Terminal version

1.18.3181.0

Windows build number

19044.3930

Other Software

No response

Steps to reproduce

Install Windows 10 LTSC 2021

Get MS Store and install Windows Terminal from there

Restart the PC or restart explorer.exe from the taskbar for everything to load up as an extra measure

Right click on the desktop and you'll notice there's no "Open in Terminal" option but if you right click on a folder on the desktop or in Explorer then the option is visible.

Expected Behavior

How-to-Restore-the-Old-Windows-10-Context-Menu-in-Windows-11-Step-by-step-Guide

Actual Behavior

explorer_Wu61TIhZlk

Originally created by @SkewelVsAll on GitHub (Jan 26, 2024). Originally assigned to: @DHowett on GitHub. ### Windows Terminal version 1.18.3181.0 ### Windows build number 19044.3930 ### Other Software _No response_ ### Steps to reproduce Install Windows 10 LTSC 2021 Get MS Store and install Windows Terminal from there Restart the PC or restart explorer.exe from the taskbar for everything to load up as an extra measure Right click on the desktop and you'll notice there's no "Open in Terminal" option but if you right click on a folder on the desktop or in Explorer then the option is visible. ### Expected Behavior ![How-to-Restore-the-Old-Windows-10-Context-Menu-in-Windows-11-Step-by-step-Guide](https://github.com/microsoft/terminal/assets/94841287/27d1042d-29aa-41c2-9d88-f1a47e35977e) ### Actual Behavior ![explorer_Wu61TIhZlk](https://github.com/microsoft/terminal/assets/94841287/3eb3dd22-f6c1-4f7d-8bab-bca51ce85b11)
claunia added the Issue-BugNeeds-Tag-FixResolution-Duplicate labels 2026-01-31 07:34:23 +00:00
claunia commented 2026-01-31 07:34:24 +00:00
Author
Owner
Copy Link

@github-actions[bot] commented on GitHub (Jan 26, 2024):

Hi I'm an AI powered bot that finds similar issues based off the issue title.

Please view the issues below to see if they solve your problem, and if the issue describes your problem please consider closing this one and thumbs upping the other issue to help us prioritize it. Thank you!

Closed similar issues:

Note: You can give me feedback by thumbs upping or thumbs downing this comment.

@github-actions[bot] commented on GitHub (Jan 26, 2024): Hi I'm an AI powered bot that finds similar issues based off the issue title. Please view the issues below to see if they solve your problem, and if the issue describes your problem please consider closing this one and thumbs upping the other issue to help us prioritize it. Thank you! ### Closed similar issues: - ["Open with Windows Terminal" context menu option not available (#11638)](https://github.com/microsoft/terminal/issues/11638), similarity score: 0.85 - ['Open in Terminal' not appearing in Windows Explorer context menu (#16236)](https://github.com/microsoft/terminal/issues/16236), similarity score: 0.80 - ["Open Windows Terminal Here" in the context menu is missing (#9626)](https://github.com/microsoft/terminal/issues/9626), similarity score: 0.80 - ["Open with Windows Terminal" context menu not display on desktop (or right click without selected folder) (#11839)](https://github.com/microsoft/terminal/issues/11839), similarity score: 0.80 - ["Open in Windows Terminal" and "Windows Terminal" context menu is gone in Windows 11 22000.348 (#11840)](https://github.com/microsoft/terminal/issues/11840), similarity score: 0.77 > Note: You can give me feedback by thumbs upping or thumbs downing this comment.
claunia commented 2026-01-31 07:34:24 +00:00
Author
Owner
Copy Link

@lhecker commented on GitHub (Jan 26, 2024):

Hey! I believe #14979 is very similar to what you're describing and was closed as a duplicate of #10694, #10496 and #10119. I think we should close this issue as a duplicate as well then. @zadjii-msft Would you agree?

@lhecker commented on GitHub (Jan 26, 2024): Hey! I believe #14979 is very similar to what you're describing and was closed as a duplicate of #10694, #10496 and #10119. I think we should close this issue as a duplicate as well then. @zadjii-msft Would you agree?
claunia commented 2026-01-31 07:34:24 +00:00
Author
Owner
Copy Link

@SkewelVsAll commented on GitHub (Jan 26, 2024):

Hey! I believe #14979 is very similar to what you're describing and was closed as a duplicate of #10694, #10496 and #10119. I think we should close this issue as a duplicate as well then. @zadjii-msft Would you agree?

Yes, I've seen them before and I still went ahead and made another one thinking their issues are probably fixed by now because 1) These issues were posted a few years ago and a lot of variables come into play such as a software update to the application itself, maybe even an OS update or to top it off maybe even an OS reinstall might have fixed it and 2) They were using the consumer edition of Windows and I'm not.

Adding to that all these issues just seem to have someone providing a workaround and not an actual fix, I was hoping to get something concrete that'll work, maybe reverse engineering the scoop .reg file of adding and removing the Windows Terminal context menu and modifying it to work with the one from Microsoft Store might do the trick? I don't know.

@SkewelVsAll commented on GitHub (Jan 26, 2024): > Hey! I believe #14979 is very similar to what you're describing and was closed as a duplicate of #10694, #10496 and #10119. I think we should close this issue as a duplicate as well then. @zadjii-msft Would you agree? Yes, I've seen them before and I still went ahead and made another one thinking their issues are probably fixed by now because 1) These issues were posted a few years ago and a lot of variables come into play such as a software update to the application itself, maybe even an OS update or to top it off maybe even an OS reinstall might have fixed it and 2) They were using the consumer edition of Windows and I'm not. Adding to that all these issues just seem to have someone providing a workaround and not an actual fix, I was hoping to get something concrete that'll work, maybe reverse engineering the scoop .reg file of adding and removing the Windows Terminal context menu and modifying it to work with the one from Microsoft Store might do the trick? I don't know.
claunia commented 2026-01-31 07:34:25 +00:00
Author
Owner
Copy Link

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

I am also having this issue on LTSC, 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.

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.

@hugo9655 commented on GitHub (Feb 4, 2024): I am also having this issue on LTSC, 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. 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.
claunia commented 2026-01-31 07:34:25 +00:00
Author
Owner
Copy Link

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

I'm pretty sure this just goes over with the rest of the fire in https://github.com/microsoft/terminal/issues/14185#issuecomment-1324144884. There's definitely known issues in Windows 10 with the "packaged" context menu entries. Issues that we suspect were fixed in Windows 11, but without necessarily being backported to Windows 10 😕

/dup #14185

@zadjii-msft commented on GitHub (Feb 6, 2024): I'm pretty sure this just goes over with the rest of the fire in https://github.com/microsoft/terminal/issues/14185#issuecomment-1324144884. There's definitely known issues in Windows 10 with the "packaged" context menu entries. Issues that we suspect were fixed in Windows 11, but without necessarily being backported to Windows 10 😕 /dup #14185
claunia commented 2026-01-31 07:34:25 +00:00
Author
Owner
Copy Link

@microsoft-github-policy-service[bot] commented on GitHub (Feb 6, 2024):

Hi! We've identified this issue as a duplicate of another one that already exists on this Issue Tracker. This specific instance is being closed in favor of tracking the concern over on the referenced thread. Thanks for your report!

@microsoft-github-policy-service[bot] commented on GitHub (Feb 6, 2024): Hi! We've identified this issue as a duplicate of another one that already exists on this Issue Tracker. This specific instance is being closed in favor of tracking the concern over on the referenced thread. Thanks for your report! <!-- Policy app identification https://img.shields.io/static/v1?label=PullRequestIssueManagement. -->
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 Issue-Bug Needs-Tag-Fix Resolution-Duplicate
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#21143
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?