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

Windows Terminal refusing to open with no visual feedback #20769

New Issue
Closed
opened 2026-01-31 07:23:29 +00:00 by claunia · 5 comments
claunia commented 2026-01-31 07:23:29 +00:00
Owner
Copy Link

Originally created by @RVFET on GitHub (Nov 5, 2023).

Windows Terminal version

1.18.2822.0

Windows build number

10.0.22000.1848

Other Software

No response

Steps to reproduce

I downloaded it through winget (using CMD). Command I ran : winget install Microsoft.WindowsTerminal

Expected Behavior

Run with no issues, open normally

Actual Behavior

Not opening, not saying anything at all, no error popups, no confirmation dialogs, not "opening and closing immediately". Just does not do anything at all.
When I checked "Windows Event Logs" I could see the cause, the log looks as follows:

Faulting application name: WindowsTerminal.exe, version: 1.18.2310.9002, time stamp: 0x65248b0f
Faulting module name: dcomp.dll, version: 10.0.22621.1778, time stamp: 0x830223ed
Exception code: 0xc0000005
Fault offset: 0x0000000000092244
Faulting process id: 0x0x250C
Faulting application start time: 0x0x1DA0FFE088FD00A
Faulting application path: C:\Program Files\WindowsApps\Microsoft.WindowsTerminal_1.18.2822.0_x64__8wekyb3d8bbwe\WindowsTerminal.exe
Faulting module path: C:\Windows\System32\dcomp.dll
Report Id: 7b41473e-1bfe-40d5-bde1-c837d3335246
Faulting package full name: Microsoft.WindowsTerminal_1.18.2822.0_x64__8wekyb3d8bbwe
Faulting package-relative application ID: APP
Originally created by @RVFET on GitHub (Nov 5, 2023). ### Windows Terminal version 1.18.2822.0 ### Windows build number 10.0.22000.1848 ### Other Software _No response_ ### Steps to reproduce I downloaded it through winget (using CMD). Command I ran : `winget install Microsoft.WindowsTerminal` ### Expected Behavior Run with no issues, open normally ### Actual Behavior Not opening, not saying anything at all, no error popups, no confirmation dialogs, not "opening and closing immediately". Just does not do anything at all. When I checked "Windows Event Logs" I could see the cause, the log looks as follows: ``` Faulting application name: WindowsTerminal.exe, version: 1.18.2310.9002, time stamp: 0x65248b0f Faulting module name: dcomp.dll, version: 10.0.22621.1778, time stamp: 0x830223ed Exception code: 0xc0000005 Fault offset: 0x0000000000092244 Faulting process id: 0x0x250C Faulting application start time: 0x0x1DA0FFE088FD00A Faulting application path: C:\Program Files\WindowsApps\Microsoft.WindowsTerminal_1.18.2822.0_x64__8wekyb3d8bbwe\WindowsTerminal.exe Faulting module path: C:\Windows\System32\dcomp.dll Report Id: 7b41473e-1bfe-40d5-bde1-c837d3335246 Faulting package full name: Microsoft.WindowsTerminal_1.18.2822.0_x64__8wekyb3d8bbwe Faulting package-relative application ID: APP ```
claunia added the Needs-TriageIssue-BugNeeds-Author-FeedbackNo-Recent-Activity labels 2026-01-31 07:23:30 +00:00
claunia commented 2026-01-31 07:23:31 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Nov 6, 2023):

Can you try to get this repro'd with the Feedback Hub taking a recording? Alas, I can't find your dump on the backend from what you've shared, but the feedback hub link should help.

/feedback

FWIW there is a dcomp.dll crash tracked in MSFT:40378391. That one was fixed in 2022, but all the details in there are very Xbox specific. Maybe this is a fresh crash bucket in the Terminal that is wrongly getting bucketed to that bug.
(MSFT:19185190 also looks sus, and probably more relevant in this case. It got duped to the other bug, but I bet that's incorrect)

@zadjii-msft commented on GitHub (Nov 6, 2023): Can you try to get this repro'd with the Feedback Hub taking a recording? Alas, I can't find your dump on the backend from what you've shared, but the feedback hub link should help. /feedback FWIW there is a `dcomp.dll` crash tracked in MSFT:40378391. That one was fixed in 2022, but all the details in there are _very_ Xbox specific. Maybe this is a fresh crash bucket in the Terminal that is wrongly getting bucketed to that bug. (MSFT:19185190 also looks sus, and probably more relevant in this case. It got duped to the other bug, but I bet that's incorrect)
claunia commented 2026-01-31 07:23:31 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Nov 6, 2023):

(looks like the bot's dead?)

Hi there!

Can you please send us feedback with the Feedback Hub with this issue? Make sure to click the "Start recording" button, then reproduce the issue before submitting the feedback. Once it's submitted, paste the link here so we can more easily find your crash information on the back end?

Thanks!

image

image

image

@zadjii-msft commented on GitHub (Nov 6, 2023): (looks like the bot's dead?) Hi there!<br><br>Can you please send us feedback with the [Feedback Hub](https://support.microsoft.com/en-us/windows/send-feedback-to-microsoft-with-the-feedback-hub-app-f59187f8-8739-22d6-ba93-f66612949332) with this issue? Make sure to click the "Start recording" button, then reproduce the issue before submitting the feedback. Once it's submitted, paste the link here so we can more easily find your crash information on the back end?<br><br>Thanks!<br><br>![image](https://user-images.githubusercontent.com/18356694/140811502-a068f78b-89d2-4587-925a-73e19652b830.png)<br><br>![image](https://user-images.githubusercontent.com/18356694/140811557-cdc22a0f-fa6a-4f6a-953e-73b51f5548a3.png)<br><br>![image](https://user-images.githubusercontent.com/18221333/62478649-6de55400-b760-11e9-806e-5aab7e085a9f.png)
claunia commented 2026-01-31 07:23:31 +00:00
Author
Owner
Copy Link

@Kristina-Pianykh commented on GitHub (Nov 7, 2023):

Confirming the issue.
When I try to open the Terminal from Power Shell by running wt, I get

PS C:\Users\pianykri> wt
Program 'wt.exe' failed to run: The file cannot be accessed by the systemAt line:1 char:1
+ wt
+ ~~.
At line:1 char:1
+ wt
+ ~~
    + CategoryInfo          : ResourceUnavailable: (:) [], ApplicationFailedException
    + FullyQualifiedErrorId : NativeCommandFailed

From the Run Window:
Screenshot 2023-11-07 214615

The wt.exe file is on my PATH (located at %USERPROFILE%\AppData\Local\Microsoft\WindowsApps)

@Kristina-Pianykh commented on GitHub (Nov 7, 2023): Confirming the issue. When I try to open the Terminal from Power Shell by running `wt`, I get ``` PS C:\Users\pianykri> wt Program 'wt.exe' failed to run: The file cannot be accessed by the systemAt line:1 char:1 + wt + ~~. At line:1 char:1 + wt + ~~ + CategoryInfo : ResourceUnavailable: (:) [], ApplicationFailedException + FullyQualifiedErrorId : NativeCommandFailed ``` From the Run Window: ![Screenshot 2023-11-07 214615](https://github.com/microsoft/terminal/assets/51445294/234828e9-f5dd-4067-9473-7406caa5ec68) The `wt.exe` file is on my PATH (located at `%USERPROFILE%\AppData\Local\Microsoft\WindowsApps`)
claunia commented 2026-01-31 07:23:31 +00:00
Author
Owner
Copy Link

@Kristina-Pianykh commented on GitHub (Nov 7, 2023):

The issues was resolved by reinstalling the Windows Terminal. The current version is 1.18.2822.0 and it opens as intended.

@Kristina-Pianykh commented on GitHub (Nov 7, 2023): The issues was resolved by reinstalling the Windows Terminal. The current version is `1.18.2822.0` and it opens as intended.
claunia commented 2026-01-31 07:23:32 +00:00
Author
Owner
Copy Link

@microsoft-github-policy-service[bot] commented on GitHub (Nov 11, 2023):

This issue has been automatically marked as stale because it has been marked as requiring author feedback but has not had any activity for 4 days. It will be closed if no further activity occurs within 3 days of this comment.

@microsoft-github-policy-service[bot] commented on GitHub (Nov 11, 2023): This issue has been automatically marked as stale because it has been marked as requiring author feedback but has not had any activity for **4 days**. It will be closed if no further activity occurs **within 3 days of this comment**. <!-- Policy app identification https://img.shields.io/static/v1?label=PullRequestIssueManagement. -->
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 Needs-Author-Feedback Needs-Triage No-Recent-Activity
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#20769
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?