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

Bug Report - Application error : (0Xc0000142) Help-Wanted #1365

New Issue
Closed
opened 2026-01-30 22:23:45 +00:00 by claunia · 6 comments
claunia commented 2026-01-30 22:23:45 +00:00
Owner
Copy Link

Originally created by @CaptainMorgans on GitHub (May 25, 2019).

Environment

Windows 10 Home

Windows build number: [run "ver" at a command prompt]
Windows Terminal version (if applicable):
Microsoft Windows [Version 10.0.18362.145]
(c) 2019 Microsoft Corporation. All rights reserved.

Any other software?

Steps to reproduce

Expected behavior

Expected to see the terminal open into the Linux bash. Trying to open the cmd.exe produces the same error.

Actual behavior

Terminal window opens with a message cmd.exe - Application Error - "The application was unable to start correctly (0xc0000142). Click OK to close the application"

Help-Wanted

Originally created by @CaptainMorgans on GitHub (May 25, 2019). <!-- This bug tracker is monitored by Windows Terminal development team and other technical folks. **Important: When reporting BSODs or security issues, DO NOT attach memory dumps, logs, or traces to Github issues**. Instead, send dumps/traces to secure@microsoft.com, referencing this GitHub issue. Please use this form and describe your issue, concisely but precisely, with as much detail as possible. --> # Environment Windows 10 Home ```none Windows build number: [run "ver" at a command prompt] Windows Terminal version (if applicable): Microsoft Windows [Version 10.0.18362.145] (c) 2019 Microsoft Corporation. All rights reserved. Any other software? ``` # Steps to reproduce <!-- A description of how to trigger this bug. --> # Expected behavior Expected to see the terminal open into the Linux bash. Trying to open the cmd.exe produces the same error. <!-- A description of what you're expecting, possibly containing screenshots or reference material. --> # Actual behavior Terminal window opens with a message cmd.exe - Application Error - "The application was unable to start correctly (0xc0000142). Click OK to close the application" <!-- What's actually happening? --> # Help-Wanted
claunia added the Product-ConhostIssue-BugNeeds-AttentionArea-Server labels 2026-01-30 22:23:45 +00:00
claunia commented 2026-01-30 22:23:46 +00:00
Author
Owner
Copy Link

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

Are you launching the built-in cmd.exe/powershell.exe/wsl.exe/conhost.exe, or are you trying to launch OpenConsole.exe/Windows Terminal built from source in this repo?

What architecture is your machine, and if you're building from source, what platform are you targeting?

@zadjii-msft commented on GitHub (May 28, 2019): Are you launching the built-in cmd.exe/powershell.exe/wsl.exe/conhost.exe, or are you trying to launch OpenConsole.exe/Windows Terminal built from source in this repo? What architecture is your machine, and if you're building from source, what platform are you targeting?
claunia commented 2026-01-30 22:23:46 +00:00
Author
Owner
Copy Link

@CaptainMorgans commented on GitHub (May 31, 2019):

Hi,

What architecture is your machine X64 , and if you're building from source Yes from the GitHub repo, what platform are toy targeting wsl.exe?
I can open wsl.exe , cmd.exe, and even OpenConsole.exe , which results in a single terminal window which is not the new terminal application in appearance.

See the screenshot below. The second screenshot shows the error I am getting with the dev build terminal.

[cid:image001.png@01D516F1.044640A0]

[cid:image002.png@01D516F1.10249520]

Kind Regards,
Stephen

From: Mike Griese notifications@github.com
Sent: Tuesday, May 28, 2019 3:32 PM
To: microsoft/terminal terminal@noreply.github.com
Cc: Stephen Morgans | Code Craft stephen@codecraft.co.za; Author author@noreply.github.com
Subject: Re: [microsoft/terminal] Bug Report - Application error : (0Xc0000142) Help-Wanted (#1018)

Are you launching the built-in cmd.exe/powershell.exe/wsl.exe/conhost.exe, or are you trying to launch OpenConsole.exe/Windows Terminal built from source in this repo?

What architecture is your machine, and if you're building from source, what platform are toy targeting?

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://github.com/microsoft/terminal/issues/1018?email_source=notifications&email_token=AA22CZEMDT5M26LSZHWGPQLPXUX47A5CNFSM4HPVNLQKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODWMEBTI#issuecomment-496517325, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AA22CZGQAVUJ6R54BW5Y2GTPXUX47ANCNFSM4HPVNLQA.

@CaptainMorgans commented on GitHub (May 31, 2019): Hi, What architecture is your machine X64 , and if you're building from source Yes from the GitHub repo, what platform are toy targeting wsl.exe? I can open wsl.exe , cmd.exe, and even OpenConsole.exe , which results in a single terminal window which is not the new terminal application in appearance. See the screenshot below. The second screenshot shows the error I am getting with the dev build terminal. [cid:image001.png@01D516F1.044640A0] [cid:image002.png@01D516F1.10249520] Kind Regards, Stephen From: Mike Griese <notifications@github.com> Sent: Tuesday, May 28, 2019 3:32 PM To: microsoft/terminal <terminal@noreply.github.com> Cc: Stephen Morgans | Code Craft <stephen@codecraft.co.za>; Author <author@noreply.github.com> Subject: Re: [microsoft/terminal] Bug Report - Application error : (0Xc0000142) Help-Wanted (#1018) Are you launching the built-in cmd.exe/powershell.exe/wsl.exe/conhost.exe, or are you trying to launch OpenConsole.exe/Windows Terminal built from source in this repo? What architecture is your machine, and if you're building from source, what platform are toy targeting? — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub<https://github.com/microsoft/terminal/issues/1018?email_source=notifications&email_token=AA22CZEMDT5M26LSZHWGPQLPXUX47A5CNFSM4HPVNLQKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODWMEBTI#issuecomment-496517325>, or mute the thread<https://github.com/notifications/unsubscribe-auth/AA22CZGQAVUJ6R54BW5Y2GTPXUX47ANCNFSM4HPVNLQA>.
claunia commented 2026-01-30 22:23:46 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (May 31, 2019):

Hey for the record, your screenshots didn't work through email replying to github. You might have to respond on github for them to work.

When I ask about what platform you're targeting, I mean what's the Solution Platform set to in VS?
image

Here it's set to x64.

@zadjii-msft commented on GitHub (May 31, 2019): Hey for the record, your screenshots didn't work through email replying to github. You might have to respond on github for them to work. When I ask about what platform you're targeting, I mean what's the Solution Platform set to in VS? ![image](https://user-images.githubusercontent.com/18356694/58707428-890ba000-837a-11e9-92b0-4dc478612ab3.png) Here it's set to x64.
claunia commented 2026-01-30 22:23:46 +00:00
Author
Owner
Copy Link

@ghost commented on GitHub (Jun 4, 2019):

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.

@ghost commented on GitHub (Jun 4, 2019): 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**.
claunia commented 2026-01-30 22:23:46 +00:00
Author
Owner
Copy Link

@CaptainMorgans commented on GitHub (Jun 9, 2019):

This is the event viewer log created when I try to open the application.

The application was working 100%, but after a Windows update it broke.

Log Name: Application
Source: Application Error
Date: 2019/06/09 12:31:17 PM
Event ID: 1000
Task Category: (100)
Level: Error
Keywords: Classic
User: N/A
Computer: Dell2016
Description:
Faulting application name: WindowsTerminal.exe, version: 0.0.0.0, time stamp: 0x5ce9ca15
Faulting module name: Microsoft.UI.Xaml.Markup.dll, version: 0.0.0.0, time stamp: 0x5ce9c93c
Exception code: 0xc0000005
Fault offset: 0x000000000002decf
Faulting process id: 0x7748
Faulting application start time: 0x01d51eae6f1e2d27
Faulting application path: C:\Terminal\src\cascadia\CascadiaPackage\bin\x64\Debug\AppX\WindowsTerminal.exe
Faulting module path: C:\Terminal\src\cascadia\CascadiaPackage\bin\x64\Debug\AppX\Microsoft.UI.Xaml.Markup.dll
Report Id: 64717541-ed38-4710-a1c5-774f2b55f243
Faulting package full name: WindowsTerminalDev_0.0.1.0_x64__8wekyb3d8bbwe
Faulting package-relative application ID: App
Event Xml:



1000
2
100
0x80000000000000

27114
Application
Dell2016



WindowsTerminal.exe
0.0.0.0
5ce9ca15
Microsoft.UI.Xaml.Markup.dll
0.0.0.0
5ce9c93c
c0000005
000000000002decf
7748
01d51eae6f1e2d27
C:\Terminal\src\cascadia\CascadiaPackage\bin\x64\Debug\AppX\WindowsTerminal.exe
C:\Terminal\src\cascadia\CascadiaPackage\bin\x64\Debug\AppX\Microsoft.UI.Xaml.Markup.dll
64717541-ed38-4710-a1c5-774f2b55f243
WindowsTerminalDev_0.0.1.0_x64__8wekyb3d8bbwe
App

@CaptainMorgans commented on GitHub (Jun 9, 2019): This is the event viewer log created when I try to open the application. The application was working 100%, but after a Windows update it broke. Log Name: Application Source: Application Error Date: 2019/06/09 12:31:17 PM Event ID: 1000 Task Category: (100) Level: Error Keywords: Classic User: N/A Computer: Dell2016 Description: Faulting application name: WindowsTerminal.exe, version: 0.0.0.0, time stamp: 0x5ce9ca15 Faulting module name: Microsoft.UI.Xaml.Markup.dll, version: 0.0.0.0, time stamp: 0x5ce9c93c Exception code: 0xc0000005 Fault offset: 0x000000000002decf Faulting process id: 0x7748 Faulting application start time: 0x01d51eae6f1e2d27 Faulting application path: C:\Terminal\src\cascadia\CascadiaPackage\bin\x64\Debug\AppX\WindowsTerminal.exe Faulting module path: C:\Terminal\src\cascadia\CascadiaPackage\bin\x64\Debug\AppX\Microsoft.UI.Xaml.Markup.dll Report Id: 64717541-ed38-4710-a1c5-774f2b55f243 Faulting package full name: WindowsTerminalDev_0.0.1.0_x64__8wekyb3d8bbwe Faulting package-relative application ID: App Event Xml: <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event"> <System> <Provider Name="Application Error" /> <EventID Qualifiers="0">1000</EventID> <Level>2</Level> <Task>100</Task> <Keywords>0x80000000000000</Keywords> <TimeCreated SystemTime="2019-06-09T10:31:17.983412600Z" /> <EventRecordID>27114</EventRecordID> <Channel>Application</Channel> <Computer>Dell2016</Computer> <Security /> </System> <EventData> <Data>WindowsTerminal.exe</Data> <Data>0.0.0.0</Data> <Data>5ce9ca15</Data> <Data>Microsoft.UI.Xaml.Markup.dll</Data> <Data>0.0.0.0</Data> <Data>5ce9c93c</Data> <Data>c0000005</Data> <Data>000000000002decf</Data> <Data>7748</Data> <Data>01d51eae6f1e2d27</Data> <Data>C:\Terminal\src\cascadia\CascadiaPackage\bin\x64\Debug\AppX\WindowsTerminal.exe</Data> <Data>C:\Terminal\src\cascadia\CascadiaPackage\bin\x64\Debug\AppX\Microsoft.UI.Xaml.Markup.dll</Data> <Data>64717541-ed38-4710-a1c5-774f2b55f243</Data> <Data>WindowsTerminalDev_0.0.1.0_x64__8wekyb3d8bbwe</Data> <Data>App</Data> </EventData> </Event>
claunia commented 2026-01-30 22:23:46 +00:00
Author
Owner
Copy Link

@CaptainMorgans commented on GitHub (Jun 9, 2019):

Hey for the record, your screenshots didn't work through email replying to github. You might have to respond on github for them to work.

When I ask about what platform you're targeting, I mean what's the Solution Platform set to in VS?
image

Here it's set to x64.

I did compile it in x64 architecture not ARM64.

@CaptainMorgans commented on GitHub (Jun 9, 2019): > Hey for the record, your screenshots didn't work through email replying to github. You might have to respond on github for them to work. > > When I ask about what platform you're targeting, I mean what's the Solution Platform set to in VS? > ![image](https://user-images.githubusercontent.com/18356694/58707428-890ba000-837a-11e9-92b0-4dc478612ab3.png) > > Here it's set to x64. I did compile it in x64 architecture not ARM64.
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-Server Issue-Bug Needs-Attention Product-Conhost
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#1365
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?