Skip to content
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

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

Closed
SkewelVsAll opened this issue Jan 26, 2024 · 6 comments
Assignees
Labels
Issue-Bug It either shouldn't be doing this or needs an investigation. Needs-Tag-Fix Doesn't match tag requirements Resolution-Duplicate There's another issue on the tracker that's pretty much the same thing.

Comments

@SkewelVsAll
Copy link

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

@SkewelVsAll SkewelVsAll added Issue-Bug It either shouldn't be doing this or needs an investigation. Needs-Triage It's a new issue that the core contributor team needs to triage at the next triage meeting labels Jan 26, 2024
Copy link

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.

@lhecker
Copy link
Member

lhecker commented 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?

@SkewelVsAll
Copy link
Author

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.

@the9655a
Copy link

the9655a commented 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.

@zadjii-msft
Copy link
Member

I'm pretty sure this just goes over with the rest of the fire in #14185 (comment). 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 zadjii-msft closed this as not planned Won't fix, can't repro, duplicate, stale Feb 6, 2024
Copy link
Contributor

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 microsoft-github-policy-service bot added Resolution-Duplicate There's another issue on the tracker that's pretty much the same thing. Needs-Tag-Fix Doesn't match tag requirements and removed Needs-Triage It's a new issue that the core contributor team needs to triage at the next triage meeting labels Feb 6, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Issue-Bug It either shouldn't be doing this or needs an investigation. Needs-Tag-Fix Doesn't match tag requirements Resolution-Duplicate There's another issue on the tracker that's pretty much the same thing.
Projects
None yet
Development

No branches or pull requests

5 participants