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

Frequent crash in Microsoft.Terminal.Control.dll Exception code: 0xc0000409 #16783

New Issue
Open
opened 2026-01-31 05:22:42 +00:00 by claunia · 0 comments
claunia commented 2026-01-31 05:22:42 +00:00
Owner
Copy Link

Originally created by @halr9000 on GitHub (Feb 15, 2022).

Windows Terminal version

1.11.3471.0

Windows build number

10.0.22000.0

Other Software

Glassbrick, a vision assistive a11y software

Steps to reproduce

Three easily repeatable scenarios observed so far, same exact outcomes and fatal exception thrown. The easiest is as follows:

  1. Open terminal (default powershell)
  2. Paste anything multiple times until line length is exceeded, moving cursor to next line
  3. Backspace until it crashes

Fault also seen by running longer running processes, suspicion that it writes to the host in a way that might trigger some cursor movement bug, harder to expalin.

Expected Behavior

Not crash

Actual Behavior

Crash with the following in event log:

Log Name:      Application
Source:        Application Error
Date:          2/15/2022 7:37:19 AM
Event ID:      1000
Task Category: (100)
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      mando
Description:
Faulting application name: WindowsTerminal.exe, version: 1.11.2112.13011, time stamp: 0x61b80d0f
Faulting module name: Microsoft.Terminal.Control.dll, version: 1.11.2112.13011, time stamp: 0x61b80b7f
Exception code: 0xc0000409
Fault offset: 0x00000000000a92b9
Faulting process id: 0x37a8
Faulting application start time: 0x01d8226773f2ec80
Faulting application path: C:\Program Files\WindowsApps\Microsoft.WindowsTerminal_1.11.3471.0_x64__8wekyb3d8bbwe\WindowsTerminal.exe
Faulting module path: C:\Program Files\WindowsApps\Microsoft.WindowsTerminal_1.11.3471.0_x64__8wekyb3d8bbwe\Microsoft.Terminal.Control.dll
Report Id: 714421e2-7079-4166-b5cc-67340637d943
Faulting package full name: Microsoft.WindowsTerminal_1.11.3471.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>
    <Version>0</Version>
    <Level>2</Level>
    <Task>100</Task>
    <Opcode>0</Opcode>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2022-02-15T12:37:19.9783387Z" />
    <EventRecordID>16703</EventRecordID>
    <Correlation />
    <Execution ProcessID="21164" ThreadID="0" />
    <Channel>Application</Channel>
    <Computer>mando</Computer>
    <Security />
  </System>
  <EventData>
    <Data>WindowsTerminal.exe</Data>
    <Data>1.11.2112.13011</Data>
    <Data>61b80d0f</Data>
    <Data>Microsoft.Terminal.Control.dll</Data>
    <Data>1.11.2112.13011</Data>
    <Data>61b80b7f</Data>
    <Data>c0000409</Data>
    <Data>00000000000a92b9</Data>
    <Data>37a8</Data>
    <Data>01d8226773f2ec80</Data>
    <Data>C:\Program Files\WindowsApps\Microsoft.WindowsTerminal_1.11.3471.0_x64__8wekyb3d8bbwe\WindowsTerminal.exe</Data>
    <Data>C:\Program Files\WindowsApps\Microsoft.WindowsTerminal_1.11.3471.0_x64__8wekyb3d8bbwe\Microsoft.Terminal.Control.dll</Data>
    <Data>714421e2-7079-4166-b5cc-67340637d943</Data>
    <Data>Microsoft.WindowsTerminal_1.11.3471.0_x64__8wekyb3d8bbwe</Data>
    <Data>App</Data>
  </EventData>
</Event>
Originally created by @halr9000 on GitHub (Feb 15, 2022). ### Windows Terminal version 1.11.3471.0 ### Windows build number 10.0.22000.0 ### Other Software [Glassbrick](https://sierraasher.gumroad.com/l/glassbrick), a vision assistive a11y software ### Steps to reproduce Three easily repeatable scenarios observed so far, same exact outcomes and fatal exception thrown. The easiest is as follows: 1. Open terminal (default powershell) 2. Paste anything multiple times until line length is exceeded, moving cursor to next line 3. Backspace until it crashes Fault also seen by running longer running processes, suspicion that it writes to the host in a way that might trigger some cursor movement bug, harder to expalin. ### Expected Behavior Not crash ### Actual Behavior Crash with the following in event log: ``` Log Name: Application Source: Application Error Date: 2/15/2022 7:37:19 AM Event ID: 1000 Task Category: (100) Level: Error Keywords: Classic User: N/A Computer: mando Description: Faulting application name: WindowsTerminal.exe, version: 1.11.2112.13011, time stamp: 0x61b80d0f Faulting module name: Microsoft.Terminal.Control.dll, version: 1.11.2112.13011, time stamp: 0x61b80b7f Exception code: 0xc0000409 Fault offset: 0x00000000000a92b9 Faulting process id: 0x37a8 Faulting application start time: 0x01d8226773f2ec80 Faulting application path: C:\Program Files\WindowsApps\Microsoft.WindowsTerminal_1.11.3471.0_x64__8wekyb3d8bbwe\WindowsTerminal.exe Faulting module path: C:\Program Files\WindowsApps\Microsoft.WindowsTerminal_1.11.3471.0_x64__8wekyb3d8bbwe\Microsoft.Terminal.Control.dll Report Id: 714421e2-7079-4166-b5cc-67340637d943 Faulting package full name: Microsoft.WindowsTerminal_1.11.3471.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> <Version>0</Version> <Level>2</Level> <Task>100</Task> <Opcode>0</Opcode> <Keywords>0x80000000000000</Keywords> <TimeCreated SystemTime="2022-02-15T12:37:19.9783387Z" /> <EventRecordID>16703</EventRecordID> <Correlation /> <Execution ProcessID="21164" ThreadID="0" /> <Channel>Application</Channel> <Computer>mando</Computer> <Security /> </System> <EventData> <Data>WindowsTerminal.exe</Data> <Data>1.11.2112.13011</Data> <Data>61b80d0f</Data> <Data>Microsoft.Terminal.Control.dll</Data> <Data>1.11.2112.13011</Data> <Data>61b80b7f</Data> <Data>c0000409</Data> <Data>00000000000a92b9</Data> <Data>37a8</Data> <Data>01d8226773f2ec80</Data> <Data>C:\Program Files\WindowsApps\Microsoft.WindowsTerminal_1.11.3471.0_x64__8wekyb3d8bbwe\WindowsTerminal.exe</Data> <Data>C:\Program Files\WindowsApps\Microsoft.WindowsTerminal_1.11.3471.0_x64__8wekyb3d8bbwe\Microsoft.Terminal.Control.dll</Data> <Data>714421e2-7079-4166-b5cc-67340637d943</Data> <Data>Microsoft.WindowsTerminal_1.11.3471.0_x64__8wekyb3d8bbwe</Data> <Data>App</Data> </EventData> </Event> ```
claunia added the Needs-TriageIssue-BugNeeds-Tag-FixNeeds-Attention labels 2026-01-31 05:22:42 +00:00
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-Attention Needs-Tag-Fix Needs-Triage
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#16783
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?