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

Error launching wt.exe from Explorer Run dialog #14006

New Issue
Closed
opened 2026-01-31 03:58:14 +00:00 by claunia · 6 comments
claunia commented 2026-01-31 03:58:14 +00:00
Owner
Copy Link

Originally created by @AustinWise on GitHub (May 28, 2021).

Windows Terminal version (or Windows build number)

1.8.1444.0, 10.0.19043.1023

Other Software

No response

Steps to reproduce

  1. Open the Run dialog in Windows Explorer. This can be accomplished by holding the Windows key and pushing R.
  2. Type wt
  3. Push enter

Expected Behavior

Expecting Windows Terminal to open.

Actual Behavior

The following dialog is displayed by Explorer:

[Window Title]
C:\Program Files\WindowsApps\Microsoft.WindowsTerminal_1.7.1033.0_x64__8wekyb3d8bbwe\wt.exe

[Content]
Windows cannot access the specified device, path, or file. You may not have the appropriate permissions to access the item.

[OK]

Note that running wt.exe from a command prompt or launching Windows Terminal from the start menu does work as expected.

Originally created by @AustinWise on GitHub (May 28, 2021). ### Windows Terminal version (or Windows build number) 1.8.1444.0, 10.0.19043.1023 ### Other Software _No response_ ### Steps to reproduce 1. Open the Run dialog in Windows Explorer. This can be accomplished by holding the Windows key and pushing R. 2. Type `wt` 3. Push enter ### Expected Behavior Expecting Windows Terminal to open. ### Actual Behavior The following dialog is displayed by Explorer: ``` [Window Title] C:\Program Files\WindowsApps\Microsoft.WindowsTerminal_1.7.1033.0_x64__8wekyb3d8bbwe\wt.exe [Content] Windows cannot access the specified device, path, or file. You may not have the appropriate permissions to access the item. [OK] ``` Note that running `wt.exe` from a command prompt or launching Windows Terminal from the start menu does work as expected.
claunia added the Resolution-DuplicateCulprit-Centennial labels 2026-01-31 03:58:15 +00:00
claunia commented 2026-01-31 03:58:16 +00:00
Author
Owner
Copy Link

@AustinWise commented on GitHub (May 28, 2021):

Interestingly, I was experiance a crash of WindowsTerminal.exe before. Turning the "app execution aliases" off and on again as suggested in #10167 made that crash go away. The details of that crash in case it is interesting:

Faulting application name: WindowsTerminal.exe, version: 1.7.2104.13003, time stamp: 0x60761d23
Faulting module name: TerminalApp.dll, version: 1.8.2105.24004, time stamp: 0x60ac2df2
Exception code: 0xc0000005
Fault offset: 0x0000000000019d52
Faulting process id: 0x4f2c
Faulting application start time: 0x01d753711f6db509
Faulting application path: C:\Program Files\WindowsApps\Microsoft.WindowsTerminal_1.7.1033.0_x64__8wekyb3d8bbwe\WindowsTerminal.exe
Faulting module path: C:\Program Files\WindowsApps\Microsoft.WindowsTerminal_1.8.1444.0_x64__8wekyb3d8bbwe\TerminalApp.dll
Report Id: edf473d4-ff78-4445-8f56-732623a9b4d3
Faulting package full name: Microsoft.WindowsTerminal_1.8.1444.0_x64__8wekyb3d8bbwe
Faulting package-relative application ID: App

That was with Windows 10.0.19043.985.

@AustinWise commented on GitHub (May 28, 2021): Interestingly, I was experiance a crash of WindowsTerminal.exe before. Turning the "app execution aliases" off and on again as suggested in #10167 made that crash go away. The details of that crash in case it is interesting: ``` Faulting application name: WindowsTerminal.exe, version: 1.7.2104.13003, time stamp: 0x60761d23 Faulting module name: TerminalApp.dll, version: 1.8.2105.24004, time stamp: 0x60ac2df2 Exception code: 0xc0000005 Fault offset: 0x0000000000019d52 Faulting process id: 0x4f2c Faulting application start time: 0x01d753711f6db509 Faulting application path: C:\Program Files\WindowsApps\Microsoft.WindowsTerminal_1.7.1033.0_x64__8wekyb3d8bbwe\WindowsTerminal.exe Faulting module path: C:\Program Files\WindowsApps\Microsoft.WindowsTerminal_1.8.1444.0_x64__8wekyb3d8bbwe\TerminalApp.dll Report Id: edf473d4-ff78-4445-8f56-732623a9b4d3 Faulting package full name: Microsoft.WindowsTerminal_1.8.1444.0_x64__8wekyb3d8bbwe Faulting package-relative application ID: App ``` That was with Windows 10.0.19043.985.
claunia commented 2026-01-31 03:58:16 +00:00
Author
Owner
Copy Link

@AustinWise commented on GitHub (May 28, 2021):

I used Procmon and filtered on unsuccessful operations involving paths containing "wt" or "terminal":

image

I do see some failure operations, but I'm not sure they are relevant. I can send the whole Procmon capture if that would be useful

@AustinWise commented on GitHub (May 28, 2021): I used Procmon and filtered on unsuccessful operations involving paths containing "wt" or "terminal": ![image](https://user-images.githubusercontent.com/7751/119930449-4f071180-bf34-11eb-84a3-97d480055697.png) I do see some failure operations, but I'm not sure they are relevant. I can send the whole Procmon capture if that would be useful
claunia commented 2026-01-31 03:58:16 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (May 28, 2021):

Faulting application path: C:\Program Files\WindowsApps\Microsoft.WindowsTerminal_1.7.1033.0_x64__8wekyb3d8bbwe\WindowsTerminal.exe
Faulting module path: C:\Program Files\WindowsApps\Microsoft.WindowsTerminal_1.8.1444.0_x64__8wekyb3d8bbwe\TerminalApp.dll

This is another one of the "torn application state" crashes. @DHowett as an fyi. I think we've got a bucket somewhere around here for "MSIX can be bodgy sometimes"

@zadjii-msft commented on GitHub (May 28, 2021): > > Faulting application path: C:\Program Files\WindowsApps\Microsoft.WindowsTerminal\_**1.7.1033.0**\_x64\_\_8wekyb3d8bbwe\WindowsTerminal.exe > Faulting module path: C:\Program Files\WindowsApps\Microsoft.WindowsTerminal\_**1.8.1444.0**\_x64\_\_8wekyb3d8bbwe\TerminalApp.dll This is another one of the "torn application state" crashes. @DHowett as an fyi. I think we've got a bucket somewhere around here for "MSIX can be bodgy sometimes"
claunia commented 2026-01-31 03:58:16 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (May 28, 2021):

Actually looks like we're tracking this one in /dup #10243

@zadjii-msft commented on GitHub (May 28, 2021): Actually looks like we're tracking this one in /dup #10243
claunia commented 2026-01-31 03:58:16 +00:00
Author
Owner
Copy Link

@ghost commented on GitHub (May 28, 2021):

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 (May 28, 2021): 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!
claunia commented 2026-01-31 03:58:17 +00:00
Author
Owner
Copy Link

@AustinWise commented on GitHub (May 28, 2021):

Awesome, thanks for finding the issue. I worked around it by uninstalling and reinstalling Windows Terminal. I had to reboot in between for some reason, as the reinstall was failing.

@AustinWise commented on GitHub (May 28, 2021): Awesome, thanks for finding the issue. I worked around it by uninstalling and reinstalling Windows Terminal. I had to reboot in between for some reason, as the reinstall was failing.
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 Culprit-Centennial 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#14006
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?