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

Windows 11 context menu #17998

New Issue
Closed
opened 2026-01-31 06:00:46 +00:00 by claunia · 8 comments
claunia commented 2026-01-31 06:00:46 +00:00
Owner
Copy Link

Originally created by @MuhammetEminCakir on GitHub (Jul 21, 2022).

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)

https://user-images.githubusercontent.com/64583157/180315031-39a122ac-6d06-4ee3-a741-928f5e75c970.mp4

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

Originally created by @MuhammetEminCakir on GitHub (Jul 21, 2022). ### 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) https://user-images.githubusercontent.com/64583157/180315031-39a122ac-6d06-4ee3-a741-928f5e75c970.mp4 (Blue mean: right click/ Yellow mean: left click)
claunia commented 2026-01-31 06:00:48 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Jul 21, 2022):

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

@zadjii-msft commented on GitHub (Jul 21, 2022): I'm guessing you have PowerToys installed? Which PowerToys version?
claunia commented 2026-01-31 06:00:48 +00:00
Author
Owner
Copy Link

@MuhammetEminCakir commented on GitHub (Jul 21, 2022):

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

Latest version 0.60.1

@MuhammetEminCakir commented on GitHub (Jul 21, 2022): > I'm guessing you have PowerToys installed? Which PowerToys version? Latest version 0.60.1
claunia commented 2026-01-31 06:00:48 +00:00
Author
Owner
Copy Link

@BTCHSXR commented on GitHub (Jul 22, 2022):

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.
GIF 2022-7-22 15-37-05

  • 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
@BTCHSXR commented on GitHub (Jul 22, 2022): 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. ![GIF 2022-7-22 15-37-05](https://user-images.githubusercontent.com/20433038/180390166-ba9b32b9-dbe1-4aab-bcb9-d824dbd252e2.gif) + 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
claunia commented 2026-01-31 06:00:48 +00:00
Author
Owner
Copy Link

@huohaodong commented on GitHub (Jul 22, 2022):

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
@huohaodong commented on GitHub (Jul 22, 2022): I saw a [previous discussion](https://github.com/microsoft/terminal/issues/13523) about this problem, it seems like this problem is caused by some new features of the latest [PowerToys](https://github.com/microsoft/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
claunia commented 2026-01-31 06:00:49 +00:00
Author
Owner
Copy Link

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

Yea ultimately, I suspect this is either:

  • #13523 for the powertoys related issue
  • #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.

image

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!

@zadjii-msft commented on GitHub (Jul 22, 2022): Yea ultimately, I suspect this is either: * #13523 for the powertoys related issue * #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. ![image](https://user-images.githubusercontent.com/18356694/179498580-8c24c5bf-b740-4bab-943a-a88ca40ffbfa.png) 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!
claunia commented 2026-01-31 06:00:49 +00:00
Author
Owner
Copy Link

@jasonkrasavage commented on GitHub (Feb 6, 2023):

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?

@jasonkrasavage commented on GitHub (Feb 6, 2023): I'm confused why all of the issues (this one, [#11839](https://github.com/microsoft/terminal/issues/11839) , [#13523](https://github.com/microsoft/terminal/issues/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?
claunia commented 2026-01-31 06:00:49 +00:00
Author
Owner
Copy Link

@icedterminal commented on GitHub (Apr 9, 2023):

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.

image

@icedterminal commented on GitHub (Apr 9, 2023): 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](https://community.amd.com/t5/drivers-software/remove-amd-software-from-right-click-context-menu/td-p/535537). I figured this would solve the problem. It does not. Blocking AMDs shell extension again takes Terminal with it. [Example clip](https://streamable.com/yhlixw). 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. ![image](https://user-images.githubusercontent.com/4755734/230767116-54bcd358-9555-4d9c-9a71-51db5ef0c616.png)
claunia commented 2026-01-31 06:00:49 +00:00
Author
Owner
Copy Link

@guzelonur commented on GitHub (Jan 23, 2024):

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.

@guzelonur commented on GitHub (Jan 23, 2024): 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.
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 Issue-Bug Needs-Attention Needs-Tag-Fix Needs-Triage Resolution-External
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#17998
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?