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

Terminal takes a trip upstate when DWM crashes #3839

New Issue
Open
opened 2026-01-30 23:31:13 +00:00 by claunia · 0 comments
claunia commented 2026-01-30 23:31:13 +00:00
Owner
Copy Link

Originally created by @JeremyTBradshaw on GitHub (Sep 12, 2019).

Originally assigned to: @DHowett-MSFT, @zadjii-msft on GitHub.

Environment

Windows build number: Microsoft Windows NT 10.0.18362.0
Windows Terminal version (if applicable): Windows Terminal (Preview), Version: 0.4.2382.0


Any other software? No

Steps to reproduce

  1. Open Windows Terminal.
  2. Let the computer go into screen-locked status.
  3. Unlocked the computer.
  4. Notice Windows Terminal has been closed.
  5. Proceed to Event Viewer -> Application Log and look for event 1000's showing Desktop Windows Manager and Windows Terminal applications both crashing/faulting.

Source: Application Error / ID: 1000
Faulting application name: WindowsTerminal.exe, version: 1.0.1908.26002, time stamp: 0x5d641823
Faulting module name: ucrtbase.dll, version: 10.0.18362.267, time stamp: 0x080a13f7
Exception code: 0xc0000409
Fault offset: 0x000000000006d33e
Faulting process id: 0x30050
Faulting application start time: 0x01d5695cb9dc2e1e
Faulting application path: C:\Program Files\WindowsApps\Microsoft.WindowsTerminal_0.4.2382.0_x64__8wekyb3d8bbwe\WindowsTerminal.exe
Faulting module path: C:\WINDOWS\System32\ucrtbase.dll
Report Id: e93be2a0-375b-409c-a1e8-8df49489c81e
Faulting package full name: Microsoft.WindowsTerminal_0.4.2382.0_x64__8wekyb3d8bbwe
Faulting package-relative application ID: App

Source: Application Error / ID: 1000
Faulting application name: dwm.exe, version: 10.0.18362.267, time stamp: 0x6468b8f9
Faulting module name: ntdll.dll, version: 10.0.18362.267, time stamp: 0xc00f8a30
Exception code: 0xc000000d
Fault offset: 0x000000000010f220
Faulting process id: 0x2cec0
Faulting application start time: 0x01d5696eb2d23787
Faulting application path: C:\WINDOWS\System32\dwm.exe
Faulting module path: C:\WINDOWS\SYSTEM32\ntdll.dll
Report Id: cd25779a-d818-438f-b423-2ddebb809148
Faulting package full name:
Faulting package-relative application ID:

Source: Dwminit / ID: 0
The Desktop Window Manager process has exited. (Process exit code: 0x000000ff, Restart count: 2, Primary display device ID: AMD Radeon(TM) Vega 8 Graphics)

Expected behavior

Windows Terminal should stay open until it is closed like any other program.

Actual behavior

Windows Terminal closes/crashes/faults unexpectedly.

Originally created by @JeremyTBradshaw on GitHub (Sep 12, 2019). Originally assigned to: @DHowett-MSFT, @zadjii-msft on GitHub. <!-- 🚨🚨🚨🚨🚨🚨🚨🚨🚨🚨 I ACKNOWLEDGE THE FOLLOWING BEFORE PROCEEDING: 1. If I delete this entire template and go my own path, the core team may close my issue without further explanation or engagement. 2. If I list multiple bugs/concerns in this one issue, the core team may close my issue without further explanation or engagement. 3. If I write an issue that has many duplicates, the core team may close my issue without further explanation or engagement (and without necessarily spending time to find the exact duplicate ID number). 4. If I leave the title incomplete when filing the issue, the core team may close my issue without further explanation or engagement. 5. If I file something completely blank in the body, the core team may close my issue without further explanation or engagement. All good? Then proceed! --> <!-- 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. If this is an application crash, please also provide a Feedback Hub submission link so we can find your diagnostic data on the backend. Use the category "Apps > Windows Terminal (Preview)" and choose "Share My Feedback" after submission to get the link. Please use this form and describe your issue, concisely but precisely, with as much detail as possible. --> # Environment ```none Windows build number: Microsoft Windows NT 10.0.18362.0 Windows Terminal version (if applicable): Windows Terminal (Preview), Version: 0.4.2382.0 Any other software? No ``` # Steps to reproduce <!-- A description of how to trigger this bug. --> 1. Open Windows Terminal. 2. Let the computer go into screen-locked status. 3. Unlocked the computer. 4. Notice Windows Terminal has been closed. 5. Proceed to Event Viewer -> Application Log and look for event 1000's showing Desktop Windows Manager and Windows Terminal applications both crashing/faulting. > **Source: Application Error / ID: 1000** > Faulting application name: WindowsTerminal.exe, version: 1.0.1908.26002, time stamp: 0x5d641823 > Faulting module name: ucrtbase.dll, version: 10.0.18362.267, time stamp: 0x080a13f7 > Exception code: 0xc0000409 > Fault offset: 0x000000000006d33e > Faulting process id: 0x30050 > Faulting application start time: 0x01d5695cb9dc2e1e > Faulting application path: C:\Program Files\WindowsApps\Microsoft.WindowsTerminal_0.4.2382.0_x64__8wekyb3d8bbwe\WindowsTerminal.exe > Faulting module path: C:\WINDOWS\System32\ucrtbase.dll > Report Id: e93be2a0-375b-409c-a1e8-8df49489c81e > Faulting package full name: Microsoft.WindowsTerminal_0.4.2382.0_x64__8wekyb3d8bbwe > Faulting package-relative application ID: App > **Source: Application Error / ID: 1000** > Faulting application name: dwm.exe, version: 10.0.18362.267, time stamp: 0x6468b8f9 > Faulting module name: ntdll.dll, version: 10.0.18362.267, time stamp: 0xc00f8a30 > Exception code: 0xc000000d > Fault offset: 0x000000000010f220 > Faulting process id: 0x2cec0 > Faulting application start time: 0x01d5696eb2d23787 > Faulting application path: C:\WINDOWS\System32\dwm.exe > Faulting module path: C:\WINDOWS\SYSTEM32\ntdll.dll > Report Id: cd25779a-d818-438f-b423-2ddebb809148 > Faulting package full name: > Faulting package-relative application ID: > **Source: Dwminit / ID: 0** > The Desktop Window Manager process has exited. (Process exit code: 0x000000ff, Restart count: 2, Primary display device ID: AMD Radeon(TM) Vega 8 Graphics) # Expected behavior <!-- A description of what you're expecting, possibly containing screenshots or reference material. --> Windows Terminal should stay open until it is closed like any other program. # Actual behavior <!-- What's actually happening? --> Windows Terminal closes/crashes/faults unexpectedly.
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-Rendering Issue-Bug Needs-Tag-Fix Product-Terminal Resolution-Fix-Committed Severity-Crash
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#3839
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?