terminal: Startup Crash in _HandleCreateWindow on 1.8 Stable

Had the same issue with the stack overflow

Deleted local settings, still crashed

Deleted %APPDATA%..\Local\Packages\Microsoft.WindowsTerminal_8wekyb3d8bbwe\LocalCache , then it worked again like nothing happened

On one of my machines after the update to 1.8.1444. it would open up fine to my default PowerShell tab, but any new tabs opened after that would crash it. On another machine, it crashed before showing any tabs.

To temporarily stay unblocked, I installed Windows Windows Terminal Preview (1.9.1445) on those machines to use in the interim. In a completely unexpected turn of events, as soon as I installed Preview on each machine, stable (1.8.1444) started functioning just fine again. Is Preview registering Cascadia globally upon install?

Not sure if this is the same error, but WT 1.8.1444 is crashing on startup for me, unless launched with the --help flag.

Event Viewer shows:

Faulting application name: WindowsTerminal.exe, version: 1.8.2105.24004, time stamp: 0x60ac2e94 Faulting module name: ucrtbase.dll, version: 10.0.19041.789, time stamp: 0x2bd748bf Exception code: 0xc0000409 Fault offset: 0x000000000007286e Faulting process ID: 0x6bc4 Faulting application start time: 0x01d752da2dd0acd4 Faulting application path: C:\Program Files\WindowsApps\Microsoft.WindowsTerminal_1.8.1444.0_x64__8wekyb3d8bbwe\WindowsTerminal.exe Faulting module path: C:\WINDOWS\System32\ucrtbase.dll Report ID: 7f624378-e80d-463a-9934-5274c0e3a95b Faulting package full name: Microsoft.WindowsTerminal_1.8.1444.0_x64__8wekyb3d8bbwe Faulting package-relative application ID: App

Same one here. It’s worth nothing that it happened right after rebooting to install KB5000736, but it could be unrelated.

Not sure if this is the same error, but WT 1.8.1444 is crashing on startup for me, unless launched with the --help flag.

Event Viewer shows:

Faulting application name: WindowsTerminal.exe, version: 1.8.2105.24004, time stamp: 0x60ac2e94 Faulting module name: ucrtbase.dll, version: 10.0.19041.789, time stamp: 0x2bd748bf Exception code: 0xc0000409 Fault offset: 0x000000000007286e Faulting process ID: 0x6bc4 Faulting application start time: 0x01d752da2dd0acd4 Faulting application path: C:\Program Files\WindowsApps\Microsoft.WindowsTerminal_1.8.1444.0_x64__8wekyb3d8bbwe\WindowsTerminal.exe Faulting module path: C:\WINDOWS\System32\ucrtbase.dll Report ID: 7f624378-e80d-463a-9934-5274c0e3a95b Faulting package full name: Microsoft.WindowsTerminal_1.8.1444.0_x64__8wekyb3d8bbwe Faulting package-relative application ID: App

For me repair fixed issue

What fixed the issue for me was logging out of Windows and logging in again. No need to reboot.

@MalcolmEvershed that’s a mystery to us, which we’re tracking over in #10243. We trusted the platform to provide a stable update experience and yet, we end up with PE files and fonts coming from the old version. It’s a madhouse.

FWIW, I ran into this when the Windows Store updated my Terminal to 1.8. Cascadia was not recognized in the Windows Settings -> Font Settings until I rebooted my machine, upon which Windows Terminal also started working again. Just wanted to post this in case others come across this thread (“try turning it off and on again”).

Had the same issue with the stack overflow

Deleted local settings, still crashed

Deleted %APPDATA%…\Local\Packages\Microsoft.WindowsTerminal_8wekyb3d8bbwe\LocalCache , then it worked again like nothing happened

I tried deleting both LocalCache and LocalState but no luck. I then deleted all of %APPDATA%…\Local\Packages\Microsoft.WindowsTerminal_8wekyb3d8bbwe and launched fine. Copied my old profile back in and it is running exactly as I want it to.