Windows 11 context menu

[MuhammetEminCakir]

Windows Terminal version

1.15.2002.0

Windows build number

10.0.22622.436

Other Software

No response

Steps to reproduce

1.First time right click to desktop

Expected Behavior

Terminal option always visible in Windows 11 context menu

Actual Behavior

When it is opened for the first time,
Terminal option does not visible in Windows 11 context menu for dektop (it works properly for folders)

PowerToys_YrY5Cg2d39.mp4

(Blue mean: right click/ Yellow mean: left click)

[zadjii-msft]

I'm guessing you have PowerToys installed? Which PowerToys version?

[MuhammetEminCakir]

I'm guessing you have PowerToys installed? Which PowerToys version?

Latest version 0.60.1

[BTCHSXR]

I have a similar problem. When I right-click to desktop, the terminal option is always invisible in Windows 11 context menu and it works in anywhere but desktop.

It looks like this.

• The problem seems to happen after installing Windows update KB5015732.
• This bug may not be caused by Windows Terminal because I'm using an elder version 1.14.1963.0
• Windows 11 Build 22000.832

[huohaodong]

I saw a previous discussion about this problem, it seems like this problem is caused by some new features of the latest PowerToys. However, I encountered the same problem without powertoys been installed.

Windows Terminal does not appear in the context menu when I right click on the desktop for the first time, it will appear in the next few right clicks. However, after just a few seconds without right clicking the desktop, the 'Open in Terminal' option disappeared. This problem only occurs when the context menu is opened on the desktop.

• Windows 11 Build 22621.232
• Window Terminal Version 1.14.1862.0

[zadjii-msft]

Yea ultimately, I suspect this is either:

• Windows Terminal not 100% shown in context menu #13523 for the powertoys related issue
• "Open with Windows Terminal" context menu not display on desktop (or right click without selected folder) #11839 which was tracking an internal issue about context menu not always working for the desktop background. If you don't have PowerToys installed, then I suspect you're hitting a variant of this one. That was supposed to be fixed in OS builds >22598.200, but you never know.

If you are hitting this, I'd recommend filing feedback using the Feedback Hub, under the "Desktop Environment > Right Click Context Menu" area.

I'm not sure there's much we can do to investigate here, but getting this to the team that owns the context menus might help the investigation. If you "Share" the aka.ms link to that feedback here, I can make sure to follow the internal bug that gets generated. Thanks!

[jasonkrasavage]

I'm confused why all of the issues (this one, #11839 , #13523 have been closed regarding this problem since it still seems to persist for many. Did this problem move internally, I think maybe I saw a note about that?

I've already submitted feedback for this. I have this issue with and without PowerToys and/or OneDrive installed etc. The problem is not intermittent and it's very repeatable. Fresh install of Windows OS Build 22000.1455 and Windows Terminal. You have to right click directly ON a folder to get the context menu to show, in Win10, we can enter a folder, and click anywhere in the background of that folder to see the "Open in Terminal" context menu. What actually is the expected behavior here?

[icedterminal]

Edit:

Spoke too soon. I continued to go through a list of everything that adds shell extensions. It's back after reinstalling AMD graphics drivers. It is known that AMDs shell extension can cause delay on right click (several second wait/busy cursor), or crash itself (the icon disappears from the taskbar). When the context menu does open, there is a chance the shell extension just bugs out and doesn't display again. In some cases it will appear again after time has passed. AMD does not offer a way to remove the shell extension natively like Nvidia does. It seems when the AMD shell extension bugs out, it takes Terminal with it. Reinstalling graphics drivers brought both back.

If you want to remove the AMD shell extension you can. I found a method to do so on the AMD forums. I figured this would solve the problem. It does not. Blocking AMDs shell extension again takes Terminal with it. Example clip. Why does this happen? These are completely unrelated software. That makes OneDrive, PowerToys, AMD, and Terminal itself all potential causes for the context menu to not work as expected.

Original comment is left below.

---

Yeah this is still an issue. These shouldn't be closed or resolved.

I purchased a new motherboard and needed to reinstall Windows. Have lost access to Terminal from right clicking anywhere. It randomly disappeared. I have tried removing and reinstalling OneDrive, Terminal and PowerToys to no avail.

[guzelonur]

I don't know if this is irrelevant but, I noticed when I right click to show context menu for the first time, AMD Adrenalin Software entry is not shown. However if I right click again (second time), AMD Adrenalin Software appears within desktop context menu on this next click.

The behaviour is similar to Terminal issue in this thread, so it must be something related to Windows context menu initialization or timing does matter?

Very strange.