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

Crash On Startup #14954

New Issue
Closed
opened 2026-01-31 04:24:09 +00:00 by claunia · 9 comments
claunia commented 2026-01-31 04:24:09 +00:00
Owner
Copy Link

Originally created by @hoo29 on GitHub (Aug 24, 2021).

Windows Terminal version (or Windows build number)

1.9.2107.13002

Other Software

ubuntu 20.04 LTS on WSL2
nvidia 471.68 drivers
windows 10 education 21h1

Steps to reproduce

Open Windows Terminal

Expected Behavior

It Opens

Actual Behavior

A window very briefly appears (but doesn't seem to render) and then it crashes. The following is in the event log

Faulting application name: WindowsTerminal.exe, version: 1.9.2107.13002, time stamp: 0x60edf3e3
Faulting module name: KERNELBASE.dll, version: 10.0.19041.1151, time stamp: 0x891df6d3
Exception code: 0xc000027b
Fault offset: 0x000000000010bd3e
Faulting process ID: 0xed0
Faulting application start time: 0x01d798dffb5a7eb6
Faulting application path: C:\Program Files\WindowsApps\Microsoft.WindowsTerminal_1.9.1942.0_x64__8wekyb3d8bbwe\WindowsTerminal.exe
Faulting module path: C:\Windows\System32\KERNELBASE.dll
Report ID: ac419911-ee2b-4ffe-a588-009d02877944
Faulting package full name: Microsoft.WindowsTerminal_1.9.1942.0_x64__8wekyb3d8bbwe
Faulting package-relative application ID: App

I have tried:

  • Uninstall and reinstall
  • Deleting settings.json
  • Repair and Reset
  • Setting default font to consolas
  • everyone's favourite sfc /scannow

Other issues I have found suggest it's a problem with systems that have integrated and nvidia GPUs but I only have a dedicated NVIDIA GPU, no integrated graphics.

This has been a problem for months but never got round to creating an issue!

Windows feedback link https://aka.ms/AAdl7c0

Originally created by @hoo29 on GitHub (Aug 24, 2021). ### Windows Terminal version (or Windows build number) 1.9.2107.13002 ### Other Software ubuntu 20.04 LTS on WSL2 nvidia 471.68 drivers windows 10 education 21h1 ### Steps to reproduce Open Windows Terminal ### Expected Behavior It Opens ### Actual Behavior A window very briefly appears (but doesn't seem to render) and then it crashes. The following is in the event log ``` Faulting application name: WindowsTerminal.exe, version: 1.9.2107.13002, time stamp: 0x60edf3e3 Faulting module name: KERNELBASE.dll, version: 10.0.19041.1151, time stamp: 0x891df6d3 Exception code: 0xc000027b Fault offset: 0x000000000010bd3e Faulting process ID: 0xed0 Faulting application start time: 0x01d798dffb5a7eb6 Faulting application path: C:\Program Files\WindowsApps\Microsoft.WindowsTerminal_1.9.1942.0_x64__8wekyb3d8bbwe\WindowsTerminal.exe Faulting module path: C:\Windows\System32\KERNELBASE.dll Report ID: ac419911-ee2b-4ffe-a588-009d02877944 Faulting package full name: Microsoft.WindowsTerminal_1.9.1942.0_x64__8wekyb3d8bbwe Faulting package-relative application ID: App ``` I have tried: * Uninstall and reinstall * Deleting settings.json * Repair and Reset * Setting default font to consolas * everyone's favourite sfc /scannow Other issues I have found suggest it's a problem with systems that have integrated and nvidia GPUs but I only have a dedicated NVIDIA GPU, no integrated graphics. This has been a problem for months but never got round to creating an issue! Windows feedback link https://aka.ms/AAdl7c0
claunia added the Resolution-ExternalNeeds-Tag-Fix labels 2026-01-31 04:24:09 +00:00
claunia commented 2026-01-31 04:24:10 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Aug 24, 2021):

Windows Terminal version: 1.9.2107.13002

Faulting application path: C:\Program Files\WindowsApps\Microsoft.WindowsTerminal_1.9.1942.0_x64__8wekyb3d8bbwe\WindowsTerminal.exe

Huh, one of these things is not like the other! What's the output of wt -v? It should look like
image
(more or less)

Curiously, the feedback hub dumps also show dumps from a 1.8.1521.0 version of conhost, but no windowsterminal.exe dumps, which is kinda useless.

I'm thinking that this is a variant of "the app state got torn by the Store" issue. You might have some luck downloading a Preview build off of our Github Releases page. Since you've got the Stable version installed, and that's the one that's seemingly corrupted, then I'd guess that the Preview version wouldn't have the same issue.

@zadjii-msft commented on GitHub (Aug 24, 2021): > Windows Terminal version: **1.9.2107.13002** > Faulting application path: C:\Program Files\WindowsApps\Microsoft.WindowsTerminal\_**1.9.1942.0**\_x64\_\_8wekyb3d8bbwe\WindowsTerminal.exe Huh, one of these things is not like the other! What's the output of `wt -v`? It should look like ![image](https://user-images.githubusercontent.com/18356694/130617550-6721afda-22f8-486c-9271-a467b1fe3d6b.png) (more or less) Curiously, the feedback hub dumps also show dumps from a **1.8.1521.0** version of _conhost_, but no `windowsterminal.exe` dumps, which is kinda useless. I'm thinking that this is a variant of "the app state got torn by the Store" issue. You might have some luck downloading a Preview build off of our Github Releases page. Since you've got the Stable version installed, and that's the one that's seemingly corrupted, then I'd guess that the Preview version wouldn't have the same issue.
claunia commented 2026-01-31 04:24:10 +00:00
Author
Owner
Copy Link

@hoo29 commented on GitHub (Aug 24, 2021):

I wasn't sure where to get my WT version from so copied it from the log, didn't notice the mismatch! wt -v gives
image

Uninstalled from the microsoft store and got the latest preview from github releases but it gives a similar log:

Faulting application name: WindowsTerminal.exe, version: 1.10.2107.12003, time stamp: 0x60ecd68c
Faulting module name: KERNELBASE.dll, version: 10.0.19041.1151, time stamp: 0x891df6d3
Exception code: 0xc000027b
Fault offset: 0x000000000010bd3e
Faulting process ID: 0x1604
Faulting application start time: 0x01d798e808b930ad
Faulting application path: C:\Program Files\WindowsApps\Microsoft.WindowsTerminalPreview_1.10.1933.0_x64__8wekyb3d8bbwe\WindowsTerminal.exe
Faulting module path: C:\Windows\System32\KERNELBASE.dll
Report ID: b52f59fc-263f-4b2a-8a0f-37358c88ffa4
Faulting package full name: Microsoft.WindowsTerminalPreview_1.10.1933.0_x64__8wekyb3d8bbwe
Faulting package-relative application ID: App

Is there something I can do differently to make the feedback dump more useful?

@hoo29 commented on GitHub (Aug 24, 2021): I wasn't sure where to get my WT version from so copied it from the log, didn't notice the mismatch! `wt -v` gives ![image](https://user-images.githubusercontent.com/15928164/130619827-72c15be4-634a-4d5f-b691-c5bea25fcc9e.png) Uninstalled from the microsoft store and got the latest preview from github releases but it gives a similar log: ``` Faulting application name: WindowsTerminal.exe, version: 1.10.2107.12003, time stamp: 0x60ecd68c Faulting module name: KERNELBASE.dll, version: 10.0.19041.1151, time stamp: 0x891df6d3 Exception code: 0xc000027b Fault offset: 0x000000000010bd3e Faulting process ID: 0x1604 Faulting application start time: 0x01d798e808b930ad Faulting application path: C:\Program Files\WindowsApps\Microsoft.WindowsTerminalPreview_1.10.1933.0_x64__8wekyb3d8bbwe\WindowsTerminal.exe Faulting module path: C:\Windows\System32\KERNELBASE.dll Report ID: b52f59fc-263f-4b2a-8a0f-37358c88ffa4 Faulting package full name: Microsoft.WindowsTerminalPreview_1.10.1933.0_x64__8wekyb3d8bbwe Faulting package-relative application ID: App ``` Is there something I can do differently to make the feedback dump more useful?
claunia commented 2026-01-31 04:24:10 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Aug 24, 2021):

Huh. Now that's even weirder. @DHowett any ideas?

@zadjii-msft commented on GitHub (Aug 24, 2021): Huh. Now that's even weirder. @DHowett any ideas?
claunia commented 2026-01-31 04:24:10 +00:00
Author
Owner
Copy Link

@hoo29 commented on GitHub (Aug 25, 2021):

Some further investigation, Microsoft PowerToys gives me the exact same error when I try to open the settings page

Faulting application name: PowerToys.Settings.exe, version: 0.43.0.0, time stamp: 0x5e222541
Faulting module name: KERNELBASE.dll, version: 10.0.19041.1151, time stamp: 0x891df6d3
Exception code: 0xc000027b
Fault offset: 0x000000000010bd3e
Faulting process ID: 0xdbc
Faulting application start time: 0x01d799b68eb0cd0d
Faulting application path: C:\Program Files\PowerToys\Settings\PowerToys.Settings.exe
Faulting module path: C:\Windows\System32\KERNELBASE.dll
Report ID: c419a60a-bf62-47c4-b429-801ff1665c6b
Faulting package full name: 
Faulting package-relative application ID:

It runs happily in the background and only produces an error when I try to open settings. Other UWP like Microsoft Store, Mail, and Calculator all work fine though. I did a repair install of .NET Core 3.1 Desktop Runtime (v3.1.15) - Windows x64 just in case but no difference.

Appreciate this now seems more like a system problem than a Windows Terminal issue but would welcome any suggestions.

@hoo29 commented on GitHub (Aug 25, 2021): Some further investigation, Microsoft PowerToys gives me the exact same error when I try to open the settings page ``` Faulting application name: PowerToys.Settings.exe, version: 0.43.0.0, time stamp: 0x5e222541 Faulting module name: KERNELBASE.dll, version: 10.0.19041.1151, time stamp: 0x891df6d3 Exception code: 0xc000027b Fault offset: 0x000000000010bd3e Faulting process ID: 0xdbc Faulting application start time: 0x01d799b68eb0cd0d Faulting application path: C:\Program Files\PowerToys\Settings\PowerToys.Settings.exe Faulting module path: C:\Windows\System32\KERNELBASE.dll Report ID: c419a60a-bf62-47c4-b429-801ff1665c6b Faulting package full name: Faulting package-relative application ID: ``` It runs happily in the background and only produces an error when I try to open settings. Other UWP like Microsoft Store, Mail, and Calculator all work fine though. I did a repair install of `.NET Core 3.1 Desktop Runtime (v3.1.15) - Windows x64` just in case but no difference. Appreciate this now seems more like a system problem than a Windows Terminal issue but would welcome any suggestions.
claunia commented 2026-01-31 04:24:11 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Aug 25, 2021):

Oh if this happens the same way with PowerToys Settings then this is almost certainly a Xaml Islands issue! That's a great observation!

Would you mind filing an issue on https://github.com/microsoft/microsoft-ui-xaml/? They're the team that owns XAML Islands, and they'd be much better equipped to help get to the root cause here.

@zadjii-msft commented on GitHub (Aug 25, 2021): Oh if this happens the same way with PowerToys Settings then this is _almost certainly_ a Xaml Islands issue! That's a _great_ observation! Would you mind filing an issue on https://github.com/microsoft/microsoft-ui-xaml/? They're the team that owns XAML Islands, and they'd be much better equipped to help get to the root cause here.
claunia commented 2026-01-31 04:24:11 +00:00
Author
Owner
Copy Link

@hoo29 commented on GitHub (Aug 25, 2021):

Shall do - hopefully they respond!

@hoo29 commented on GitHub (Aug 25, 2021): Shall do - hopefully they respond!
claunia commented 2026-01-31 04:24:11 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Aug 25, 2021):

Thanks for filing that! I'm gonna close this one out and use the upstream thread to follow this issue. We can always reopen if needed.
/dup https://github.com/microsoft/microsoft-ui-xaml/issues/5766

@zadjii-msft commented on GitHub (Aug 25, 2021): Thanks for filing that! I'm gonna close this one out and use the upstream thread to follow this issue. We can always reopen if needed. /dup https://github.com/microsoft/microsoft-ui-xaml/issues/5766
claunia commented 2026-01-31 04:24:11 +00:00
Author
Owner
Copy Link

@ghost commented on GitHub (Aug 25, 2021):

Hi! We've identified this issue as a duplicate of one that exists on somebody else's Issue Tracker. Please make sure you subscribe to the referenced external issue for future updates. Thanks for your report!

@ghost commented on GitHub (Aug 25, 2021): Hi! We've identified this issue as a duplicate of one that exists on somebody else's Issue Tracker. Please make sure you subscribe to the referenced external issue for future updates. Thanks for your report!
claunia commented 2026-01-31 04:24:11 +00:00
Author
Owner
Copy Link

@MrM40 commented on GitHub (Aug 14, 2022):

You might try to Windows 11 version of Window Terminal on Windows 10!
See https://github.com/microsoft/microsoft-ui-xaml/issues/5766

@MrM40 commented on GitHub (Aug 14, 2022): You might try to Windows 11 version of Window Terminal on Windows 10! See https://github.com/microsoft/microsoft-ui-xaml/issues/5766
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 Needs-Tag-Fix Resolution-External
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#14954
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?