terminal: Windows terminal attempts to start but then crashes without showing main window.
Environment
Windows build number: 10.0.20226.0
Windows Terminal version (if applicable): 1.4.3243.0
Any other software? **please tell me how to gather that info and I'll send it to you**
Steps to reproduce
I’ve just noticed this today. Whenever I start terminal (either by gui or wt command line - admin or not) Terminal shows an icon in the taskbar but then crashes without showing window. I was able to use windows terminal earlier this week with no problem. The issue happened on the version v1.3.2651.0, which is where I noticed the error. I did an upgrade to the current version to ensure I had the latest binaries.
Expected behavior
Windows Terminal should start normally
Actual behavior
Terminal shows an icon in the taskbar but then crashes without showing window.
Faulting module name: ucrtbase.dll, version: 10.0.20226.1000, time stamp: 0x88427a69
Exception code: 0xc0000409
Fault offset: 0x000000000007cb9e
Faulting process id: 0xba20
Faulting application start time: 0x01d6c0640a4832d1
Faulting application path: C:\Program Files\WindowsApps\Microsoft.WindowsTerminal_1.4.3243.0_x64__8wekyb3d8bbwe\WindowsTerminal.exe
Faulting module path: C:\WINDOWS\System32\ucrtbase.dll
Report Id: 9108696c-1d8c-4343-bceb-6f75db8896c7
Faulting package full name: Microsoft.WindowsTerminal_1.4.3243.0_x64__8wekyb3d8bbwe
Faulting package-relative application ID: App``
````Fault bucket 2267956675769727742, type 5
Event Name: MoBEX
Response: Not available
Cab Id: 0
Problem signature:
P1: Microsoft.WindowsTerminal_1.4.3243.0_x64__8wekyb3d8bbwe
P2: praid:App
P3: 1.4.2011.19003
P4: 5fb70b02
P5: ucrtbase.dll
P6: 10.0.20226.1000
P7: 88427a69
P8: 000000000007cb9e
P9: c0000409
P10: 0000000000000007
Attached files:
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.67b2bbd3-7759-427e-9dfb-3c43cf740504.tmp.mdmp
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.e6c5fb30-ec96-4745-8fec-20cfda4ee56e.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.0b74bb08-4be0-437a-840c-e872736cc6c0.tmp.xml
WPR_initiated_DiagTrackMiniLogger_OneTrace User Logger 20201119 1 Event Collector_0_inject.etl
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.5c351159-c0bc-4eea-a4ed-51b4cc7bb056.tmp.etl
WPR_initiated_DiagTrackMiniLogger_WPR System Collector_inject.etl
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.747a5642-aeff-4533-a0e4-35c385bb3111.tmp.etl
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.9de3551d-1f3c-47fd-995f-ece2da088de9.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.a91c7939-254c-4ea0-a814-9d17053b2b94.tmp.txt
These files may be available here:
\\?\C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_Microsoft.Window_9caf26d4a58d33ffb8b9fb72dfc83bbe1722d_b0038913_d0e460cc-ff68-4dae-8ee6-0df080fced91
Analysis symbol:
Rechecking for solution: 0
Report Id: 9108696c-1d8c-4343-bceb-6f75db8896c7
Report Status: 2147487744
Hashed bucket: f34e6a2b8b76f1998f796694993afafe
Cab Guid: 0
Have uploaded the contents of C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_Microsoft.Window_9caf26d4a58d33ffb8b9fb72dfc83bbe1722d_b0038913_d0e460cc-ff68-4dae-8ee6-0df080fced91 to secure@microsoft.com referenceing this issue. I cannot find the other files listed in the above error log event. I’ve repeated this a few times an each time the other files are not present.
About this issue
- Original URL
- State: closed
- Created 4 years ago
- Comments: 35 (14 by maintainers)
If you’re impacted by this after the 1.8 update, can you go into Settings > Applications > All Applications, choose Windows Terminal and then Repair? We’ve heard that this helps.
Just ran into the same issue. Terminal was working fine yesterday, today it wouldn’t launch. If I add
"fontFace": "Consolas"insettings.jsonunderprofiles.defaultsthen it starts just fine. However, resetting the app also worked for me. I will send the diagnostic files just in case.Same problem fixed by adding the
fontFace. Realized not all Cascadia Code fonts were imported, just the most basic one from Terminal install. Installed all from https://github.com/microsoft/cascadia-code/releases/tag/v2105.24, specifically the OTF files. Can now removefontFaceand it loads normally.I started experiencing this, but only on one profile on my machine. It still works perfectly on the other. I’ve tried the reset, repair, restoring the .backup profile, and even adding the default font consolas setting. Nothing works for me, it opens and crashes with the same MobEx error. It stopped working a few days ago, FWIW. It had worked perfectly fine up until then.
@campbellkerr as a quick note your JSON was missing commas after the source property and before the fontFace property, which would have been an impact.
@DHowett yep that worked! Thanks.