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 with Windows Terminal" context menu not display on desktop (or right click without selected folder) #11839

Closed
ikas-mc opened this issue Nov 29, 2021 · 31 comments
Labels
Area-ShellExtension For issues related to the explorer right-click context menu Issue-Bug It either shouldn't be doing this or needs an investigation. Needs-Tag-Fix Doesn't match tag requirements Tracking-External This bug isn't resolved, but it's following an external workitem.

Comments

@ikas-mc
Copy link

ikas-mc commented Nov 29, 2021

Windows Terminal version

v1.11.2921.0

Windows build number

22000.384 and dev

Other Software

No response

Steps to reproduce

It is difficult to reproduce, until found the association with onedrive

clean install 22000.194 and delete onedrivesetup.exe before oobe
install Windows Terminal

Expected Behavior

"Open with Windows Terminal" context menu display

Actual Behavior

27

but after install onedrive , the menu working properly

test result is:
22000.194 without onedrive = ok
update to 384 without onedrive = not display
384 with onedrive installed= ok

29

@ghost ghost added Needs-Triage It's a new issue that the core contributor team needs to triage at the next triage meeting Needs-Tag-Fix Doesn't match tag requirements labels Nov 29, 2021
@EdiWang
Copy link

EdiWang commented Nov 29, 2021

I have OneDrive installed, and my context menu is gone, I believe it is a bug in KB5007262 update.

image

@ikas-mc
Copy link
Author

ikas-mc commented Nov 29, 2021

@EdiWang
my windows(dev) had this problem before, I uninstalled onedrive, installed the latest 64-bit version... and then fixed the problem

@zadjii-msft zadjii-msft added the Area-ShellExtension For issues related to the explorer right-click context menu label Nov 29, 2021
@zadjii-msft
Copy link
Member

@ikas-mc Wait, so, is this still an issue? If it is, I reached out to someone on the explorer team, and they told me how to get some advanced diagnostics that might help.

You should be able to take an advanced trace on in the Feedback Hub, on the bottom page:
image

then, file feedback on the File Explorer path as usual, and make sure to include the zip file from the advanced diagnostics trace. Add the "Share my feedback" link here, and I can make sure it gets promoted to the right folks.

Of course, if this isn't an issue anymore, we can just close this out without the trace ☺️

@zadjii-msft zadjii-msft added the Needs-Author-Feedback The original author of the issue/PR needs to come back and respond to something label Nov 29, 2021
@EdiWang
Copy link

EdiWang commented Nov 30, 2021

@ikas-mc

Thanks for the tip. But for me, uninstall and reinstall OneDrive didn't help. Sad...

@ikas-mc
Copy link
Author

ikas-mc commented Nov 30, 2021

@zadjii-msft
This is still an issue, we just happened to find that this problem can be reproduced with onedrive

If it is determined that it is a system problem(api), then it can be closed..

https://aka.ms/AAf04ox

@ghost ghost added Needs-Attention The core contributors need to come back around and look at this ASAP. and removed Needs-Author-Feedback The original author of the issue/PR needs to come back and respond to something labels Nov 30, 2021
@zadjii-msft
Copy link
Member

Okay great, this was promoted internally to MSFT:37214068. There's not much for us to do here - this seems like a bug firmly in the explorer team's codebase. So, I'm gonna close this one out for now. I'm following the internal bug, and I'll give you an update once there's something to share. Thanks!

@zadjii-msft zadjii-msft added the Tracking-External This bug isn't resolved, but it's following an external workitem. label Nov 30, 2021
@Yannik
Copy link

Yannik commented Dec 19, 2021

I can confirm that this bug occurs after removing the OneDriveSetup automatic startup from SOFTWARE\Microsoft\Windows\CurrentVersion\Run.

@danieldaeschle
Copy link

Is there at least a workaround?

@zadjii-msft
Copy link
Member

The File Explorer team hasn't provided one, unfortunately. @danieldaeschle do you also not have OneDrive installed? That might help narrow the problem space for the explorer team

@danieldaeschle
Copy link

I have Onedrive installed

@danieldaeschle
Copy link

But it also does not get displayed in context menu

@danieldaeschle
Copy link

@EdiWang my windows(dev) had this problem before, I uninstalled onedrive, installed the latest 64-bit version... and then fixed the problem

this helped for me

@eddiezato
Copy link

I can confirm. Installed OneDrive x64, restarted File Explorer, context menu entry returned, uninstalled OneDrive, menu entry still remained.

Win 22000.469, WT 1.13.10336.0

@EdiWang
Copy link

EdiWang commented Feb 9, 2022

@eddiezato

I uninstalled OneDrive, and install 64 bit version from https://oneclient.sfx.ms/Win/Insiders/21.139.0711.0001/amd64/OneDriveSetup.exe, restart my computer. It didn't work. Windows Terminal is still missing from context menu. Sad :(

image

image

However, I do have Windows Terminal menu if I right click on a folder instead of in a folder

image

I am also curios how can Windows Terminal menu be related to OneDrive, they seems to be two completely different things.

@iGattreX
Copy link

This issue seems to still exist as of today. It is observed that the "Open in Windows Terminal" menu appears on the Desktop Context Menu just by restarting the "Windows Explorer" from Task Manager. May be someone else can also confirm this behavior? This being the case, I am not sure if it is related to OneDrive. As mentioned earlier in this thread, it looks like a bug in the Windows Explorer code base. @zadjii-msft Did the Windows Explorer team acknowledge and any indication of what could be the potential fix?

It is still unclear why it happens only in some Windows machines and not all.

@zadjii-msft
Copy link
Member

They haven't been able to find a repro unfortunately. More "advanced traces" might be helpful here, if it's happening consistently for you.

@iGattreX
Copy link

Yes, it is happening consistently. While all seems okay when I restart my PC, the item from the "Open in Windows Terminal" Context Menu disappears every time I log off from my ID and login to Windows (using same ID or another ID). I have also observed that the context menu issue gets fixed when I restart the Windows Explorer task in Task Manager. I have reported the bug with Steps Recorder screenshots and diagnostics log in the Feedback App. Refer: https://aka.ms/AAfyhpg. Hope this helps @zadjii-msft.

@shashwata27
Copy link

shashwata27 commented Mar 12, 2022

I hate this, I reset my windows today using cloud restore. And my "open in windows terminal" option was gone. I tried editing the regedit to add it but there was no blocked folder inside it also.

image
image

@zadjii-msft zadjii-msft removed the Needs-Triage It's a new issue that the core contributor team needs to triage at the next triage meeting label Mar 14, 2022
@zadjii-msft zadjii-msft added Issue-Bug It either shouldn't be doing this or needs an investigation. and removed Needs-Attention The core contributors need to come back around and look at this ASAP. labels Mar 14, 2022
@zadjii-msft
Copy link
Member

I believe this was fixed last Friday and should be flowing out to Insiders builds soonTM

@iGattreX
Copy link

In which build is this issue expected to be fixed?

@ashfaqnisar
Copy link

Hey @iGattreX, it seems the issue was fixed in the 22598.200 build version

@CrypticCus
Copy link

Finally its been months

@omeilick
Copy link

omeilick commented May 14, 2022

I think I found the solution!!

So its an application called "terminal" created by Microsoft and can be found in the Microsoft Store. Re-downloaded the application and the right-click menu pops up with the "open in terminal" option. If anyone else could verify that this works that would be amazing.

Wish I took a screenshot before because it was 100% not there before I re-downloaded the application, but see pics below for the after screenshots where the options menu is working again.

open in terminal desktop

open in terminal explorer

open in terminal

Hope this helps! Happy coding 😄

@mndtr
Copy link

mndtr commented Aug 25, 2022

I'm found that the problem starts after installing the MS PowerToys. And it fixes after uninstalling the MS PowerToys and rebooting or log out your PC but I'm reinstalled Windows 11 because I'm polluted the registry while tried fix problem. Is anyone who ran into a problem has been installed MS PowerToys on their PC's?

@DannySauval
Copy link

I had PowerToys installed, I tried to remove it and reboot but it didn’t show me the Open In Terminal, even after reinstalling Windows Terminal. Too bad, as I used this shortcut a lot on Windows 10.

@zadjii-msft
Copy link
Member

There actually was a regression our side. The thread over at #13523 (comment) has the details. It was a combo of us changing a thing, and Windows 11 also changing a thing. There are more details in #12578 (comment) also.

@weiqi-chen
Copy link

Same Issue at Windows 10

Gif:
terminal_issue

Terminal version
image

Windows 10 version
image

@ghost
Copy link

ghost commented Dec 28, 2022

I have the same problem on Windows 10 too.

@4kliksAlex
Copy link

Same Issue at Windows 10

Gif: terminal_issue terminal_issue

Terminal version image

Windows 10 version image

I have the exact same issue.

@mangogeeks
Copy link

mangogeeks commented Jun 14, 2023

Hi @omeilick ,
I think the workaround works. Unfortunately I couldn't get the screenshot of earlier state but captured the workflow when it works. Thank you.
https://github.com/microsoft/terminal/assets/99791294/23ecde69-bd2b-4e7b-8450-37ab201977e7

@bmSgithub
Copy link

This issue seems to still exist as of today. It is observed that the "Open in Windows Terminal" menu appears on the Desktop Context Menu just by restarting the "Windows Explorer" from Task Manager. May be someone else can also confirm this behavior? This being the case, I am not sure if it is related to OneDrive. As mentioned earlier in this thread, it looks like a bug in the Windows Explorer code base. @zadjii-msft Did the Windows Explorer team acknowledge and any indication of what could be the potential fix?

It is still unclear why it happens only in some Windows machines and not all.

this worked for me

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Area-ShellExtension For issues related to the explorer right-click context menu Issue-Bug It either shouldn't be doing this or needs an investigation. Needs-Tag-Fix Doesn't match tag requirements Tracking-External This bug isn't resolved, but it's following an external workitem.
Projects
None yet
Development

No branches or pull requests