starred/terminal
1
0
Fork 0
mirror of https://github.com/microsoft/terminal.git synced 2026-02-03 21:25:34 +00:00
Code Issues 19.0k Packages Projects Releases 20 Wiki Activity

"open in terminal" context menu shows in "This PC" and does nothing #17032

New Issue
Closed
opened 2026-01-31 05:30:20 +00:00 by claunia · 3 comments
claunia commented 2026-01-31 05:30:20 +00:00
Owner
Copy Link

Originally created by @bzzrak on GitHub (Mar 18, 2022).

Windows Terminal version

1.12.10393.0

Windows build number

10.0.22000.588

Other Software

No response

Steps to reproduce

Open this PC, right click the empty space

Expected Behavior

No "open in terminal" button since This PC isn't a file folder

Actual Behavior

"Open in terminal" option present, clicking it does nothing
image

Originally created by @bzzrak on GitHub (Mar 18, 2022). ### Windows Terminal version 1.12.10393.0 ### Windows build number 10.0.22000.588 ### Other Software _No response_ ### Steps to reproduce Open this PC, right click the empty space ### Expected Behavior No "open in terminal" button since This PC isn't a file folder ### Actual Behavior "Open in terminal" option present, clicking it does nothing ![image](https://user-images.githubusercontent.com/77467869/158968476-ed7ccade-3179-400e-bd70-2b45e71e8a8d.png)
claunia added the Issue-BugResolution-Duplicate labels 2026-01-31 05:30:21 +00:00
claunia commented 2026-01-31 05:30:22 +00:00
Author
Owner
Copy Link

@Nazar78 commented on GitHub (Mar 18, 2022):

I have a slightly similar problem. From the context menu it works, launching directly from the menu also works. But on the latest Windows 11 it doesn't work: Start -> right-click -> Windows Terminal or with Admin.

In app log:

Faulting application name: WindowsTerminal.exe, version: 1.11.2112.13011, time stamp: 0x61b80d0f
Faulting module name: ucrtbase.dll, version: 10.0.22000.1, time stamp: 0x00e78ce9
Exception code: 0xc0000409
Fault offset: 0x000000000007dd7e
Faulting process id: 0x1254
Faulting application start time: 0x01d83ac5748f887a
Faulting application path: C:\Program Files\WindowsApps\Microsoft.WindowsTerminal_1.11.3471.0_x64__8wekyb3d8bbwe\WindowsTerminal.exe
Faulting module path: C:\WINDOWS\System32\ucrtbase.dll
Report Id: 21cedaa7-4728-41fa-bc59-cc7472a07b08
Faulting package full name:
Faulting package-relative application ID:

Fault bucket 1680181983093725199, type 5
Event Name: BEX64
Response: Not available
Cab Id: 0

Problem signature:
P1: WindowsTerminal.exe
P2: 1.11.2112.13011
P3: 61b80d0f
P4: ucrtbase.dll
P5: 10.0.22000.1
P6: 00e78ce9
P7: 000000000007dd7e
P8: c0000409
P9: 0000000000000007
P10:

@Nazar78 commented on GitHub (Mar 18, 2022): I have a slightly similar problem. From the context menu it works, launching directly from the menu also works. But on the latest Windows 11 it doesn't work: Start -> right-click -> Windows Terminal or with Admin. In app log: > Faulting application name: WindowsTerminal.exe, version: 1.11.2112.13011, time stamp: 0x61b80d0f > Faulting module name: ucrtbase.dll, version: 10.0.22000.1, time stamp: 0x00e78ce9 > Exception code: 0xc0000409 > Fault offset: 0x000000000007dd7e > Faulting process id: 0x1254 > Faulting application start time: 0x01d83ac5748f887a > Faulting application path: C:\Program Files\WindowsApps\Microsoft.WindowsTerminal_1.11.3471.0_x64__8wekyb3d8bbwe\WindowsTerminal.exe > Faulting module path: C:\WINDOWS\System32\ucrtbase.dll > Report Id: 21cedaa7-4728-41fa-bc59-cc7472a07b08 > Faulting package full name: > Faulting package-relative application ID: > Fault bucket 1680181983093725199, type 5 > Event Name: BEX64 > Response: Not available > Cab Id: 0 > > Problem signature: > P1: WindowsTerminal.exe > P2: 1.11.2112.13011 > P3: 61b80d0f > P4: ucrtbase.dll > P5: 10.0.22000.1 > P6: 00e78ce9 > P7: 000000000007dd7e > P8: c0000409 > P9: 0000000000000007 > P10:
claunia commented 2026-01-31 05:30:22 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Mar 18, 2022):

@Nazar78 that's a totally different issue, you should file a new issue rather than dillute this one with multiple problems.

@bzzrak Thanks for the report! Pretty sure this should be covered by /dup #12578

@zadjii-msft commented on GitHub (Mar 18, 2022): @Nazar78 that's a totally different issue, you should file a new issue rather than dillute this one with multiple problems. @bzzrak Thanks for the report! Pretty sure this should be covered by /dup #12578
claunia commented 2026-01-31 05:30:22 +00:00
Author
Owner
Copy Link

@ghost commented on GitHub (Mar 18, 2022):

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!

@ghost commented on GitHub (Mar 18, 2022): 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!
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 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#17032
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?