Exception 0xc0000409 in ucrtbase.dll #17591

Closed
opened 2026-01-31 05:46:55 +00:00 by claunia · 10 comments
Owner

Originally created by @Nazar78 on GitHub (May 27, 2022).

Windows Terminal version

1.12.10983.0

Windows build number

10.0.22000.708

Other Software

No response

Steps to reproduce

From the context menu it works, launching directly from the menu also works. But on the latest Windows 11 it doesn't work: Start -> right-click -> Windows Terminal or with Admin.

In the event viewer it's showing this:

Faulting application name: WindowsTerminal.exe, version: 1.12.2204.8003, time stamp: 0x62508e2a
Faulting module name: ucrtbase.dll, version: 10.0.22000.1, time stamp: 0x00e78ce9
Exception code: 0xc0000409
Fault offset: 0x000000000007dd7e
Faulting process id: 0x228c
Faulting application start time: 0x01d871efed6469ee
Faulting application path: C:\Program Files\WindowsApps\Microsoft.WindowsTerminal_1.12.10983.0_x64__8wekyb3d8bbwe\WindowsTerminal.exe
Faulting module path: C:\WINDOWS\System32\ucrtbase.dll
Report Id: b77f3deb-3000-4181-9d2c-5bfb3c0e1170
Faulting package full name:
Faulting package-relative application ID:

image

Expected Behavior

The Windows Terminal should normally open.

Actual Behavior

The Windows Terminal doesn't launch.

Originally created by @Nazar78 on GitHub (May 27, 2022). ### Windows Terminal version 1.12.10983.0 ### Windows build number 10.0.22000.708 ### Other Software _No response_ ### Steps to reproduce From the context menu it works, launching directly from the menu also works. But on the latest Windows 11 it doesn't work: Start -> right-click -> Windows Terminal or with Admin. In the event viewer it's showing this: > Faulting application name: WindowsTerminal.exe, version: 1.12.2204.8003, time stamp: 0x62508e2a > Faulting module name: ucrtbase.dll, version: 10.0.22000.1, time stamp: 0x00e78ce9 > Exception code: 0xc0000409 > Fault offset: 0x000000000007dd7e > Faulting process id: 0x228c > Faulting application start time: 0x01d871efed6469ee > Faulting application path: C:\Program Files\WindowsApps\Microsoft.WindowsTerminal_1.12.10983.0_x64__8wekyb3d8bbwe\WindowsTerminal.exe > Faulting module path: C:\WINDOWS\System32\ucrtbase.dll > Report Id: b77f3deb-3000-4181-9d2c-5bfb3c0e1170 > Faulting package full name: > Faulting package-relative application ID: ![image](https://user-images.githubusercontent.com/2883688/170762757-440b5550-4b3a-4364-a0da-5d671f921b24.png) ### Expected Behavior The Windows Terminal should normally open. ### Actual Behavior The Windows Terminal doesn't launch.
Author
Owner

@abhinavsatheesh commented on GitHub (May 28, 2022):

I seem to have the same issue with my PC.

It all started with a Windows Update to Build 22000.613

While opening by search Terminal from start menu it works.

@abhinavsatheesh commented on GitHub (May 28, 2022): I seem to have the same issue with my PC. It all started with a Windows Update to Build 22000.613 While opening by search Terminal from start menu it works.
Author
Owner

@lhecker commented on GitHub (May 30, 2022):

This is likely MSFT-33471786. It occurs because we're allocating (for example) 0x1fffffffffffff30 bytes of memory.

@lhecker commented on GitHub (May 30, 2022): This is likely MSFT-33471786. It occurs because we're allocating (for example) `0x1fffffffffffff30` bytes of memory.
Author
Owner

@lhecker commented on GitHub (May 30, 2022):

I have a theory why this happens but I can't reproduce the crash so I can't debug it unfortunately.
If someone has the time to spare could you please do these two things for me?

If you're uncomfortable uploading these files to GitHub, please feel free to send me them via mail to:
<my github username>@microsoft.com

  • A copy of your settings.json which you can find in this directory:
    %LOCALAPPDATA%\Packages\Microsoft.WindowsTerminal_8wekyb3d8bbwe\LocalState
  • A backup of your Console's registry
    • Start regedit.exe
    • Navigate to HKEY_CURRENT_USER\Console and export the Console directory as a .reg file

image

@lhecker commented on GitHub (May 30, 2022): I have a theory why this happens but I can't reproduce the crash so I can't debug it unfortunately. If someone has the time to spare could you please do these two things for me? If you're uncomfortable uploading these files to GitHub, please feel free to send me them via mail to: `<my github username>@microsoft.com` * A copy of your `settings.json` which you can find in this directory: `%LOCALAPPDATA%\Packages\Microsoft.WindowsTerminal_8wekyb3d8bbwe\LocalState` * A backup of your Console's registry * Start regedit.exe * Navigate to `HKEY_CURRENT_USER\Console` and export the `Console` directory as a .reg file ![image](https://user-images.githubusercontent.com/2256941/171064862-5671d8c7-d0d8-4f7a-bb44-88102db4c988.png)
Author
Owner

@Nazar78 commented on GitHub (May 31, 2022):

@lhecker

Thank you for looking into this, here you go the files requested.
Console.reg.txt
settings.json.txt

@Nazar78 commented on GitHub (May 31, 2022): @lhecker Thank you for looking into this, here you go the files requested. [Console.reg.txt](https://github.com/microsoft/terminal/files/8801013/Console.reg.txt) [settings.json.txt](https://github.com/microsoft/terminal/files/8801014/settings.json.txt)
Author
Owner

@abhinavsatheesh commented on GitHub (May 31, 2022):

In my Event Viewer, the crash is detailed like this

Faulting application name: WindowsTerminal.exe, version: 1.12.2204.8003, time stamp: 0x62508e2a
Faulting module name: ucrtbase.dll, version: 10.0.22000.1, time stamp: 0x00e78ce9
Exception code: 0xc0000409
Fault offset: 0x000000000007dd7e
Faulting process ID: 0x3910
Faulting application start time: 0x01d874b9caf953c6
Faulting application path: C:\Program Files\WindowsApps\Microsoft.WindowsTerminal_1.12.10983.0_x64__8wekyb3d8bbwe\WindowsTerminal.exe
Faulting module path: C:\WINDOWS\System32\ucrtbase.dll
Report ID: 30a1bc3f-f972-455b-b2fb-f234abbcbc57
Faulting package full name:
Faulting package-relative application ID:

@abhinavsatheesh commented on GitHub (May 31, 2022): In my Event Viewer, the crash is detailed like this Faulting application name: WindowsTerminal.exe, version: 1.12.2204.8003, time stamp: 0x62508e2a Faulting module name: ucrtbase.dll, version: 10.0.22000.1, time stamp: 0x00e78ce9 Exception code: 0xc0000409 Fault offset: 0x000000000007dd7e Faulting process ID: 0x3910 Faulting application start time: 0x01d874b9caf953c6 Faulting application path: C:\Program Files\WindowsApps\Microsoft.WindowsTerminal_1.12.10983.0_x64__8wekyb3d8bbwe\WindowsTerminal.exe Faulting module path: C:\WINDOWS\System32\ucrtbase.dll Report ID: 30a1bc3f-f972-455b-b2fb-f234abbcbc57 Faulting package full name: Faulting package-relative application ID:
Author
Owner

@ghost commented on GitHub (Jul 6, 2022):

:tada:This issue was addressed in #13212, which has now been successfully released as Windows Terminal v1.14.186.🎉

Handy links:

@ghost commented on GitHub (Jul 6, 2022): :tada:This issue was addressed in #13212, which has now been successfully released as `Windows Terminal v1.14.186`.:tada: Handy links: * [Release Notes](https://github.com/microsoft/terminal/releases/tag/v1.14.186) * [Store Download](https://www.microsoft.com/store/apps/9n8g5rfz9xk3?cid=storebadge&ocid=badge)
Author
Owner

@ghost commented on GitHub (Jul 6, 2022):

:tada:This issue was addressed in #13212, which has now been successfully released as Windows Terminal Preview v1.15.186.🎉

Handy links:

@ghost commented on GitHub (Jul 6, 2022): :tada:This issue was addressed in #13212, which has now been successfully released as `Windows Terminal Preview v1.15.186`.:tada: Handy links: * [Release Notes](https://github.com/microsoft/terminal/releases/tag/v1.15.186) * [Store Download](https://www.microsoft.com/store/apps/9n8g5rfz9xk3?cid=storebadge&ocid=badge)
Author
Owner

@abhinavsatheesh commented on GitHub (Jul 7, 2022):

Thanks a lot! It is now working

@abhinavsatheesh commented on GitHub (Jul 7, 2022): Thanks a lot! It is now working
Author
Owner

@zadjii-msft commented on GitHub (Jul 7, 2022):

@lhecker there's a whole pile of things like this:

You think there's any chance this fixed some of those also?

@zadjii-msft commented on GitHub (Jul 7, 2022): @lhecker there's a whole pile of things like this: * #12249 * #12767 * #13046 * #13108 * #13197 * #9959 (maybe, that thread is a bit off the rails now) You think there's any chance this fixed some of those also?
Author
Owner

@H1-N1 commented on GitHub (Mar 17, 2024):

doesn't work
i have the lastes update os and terminal
[process exited with code 5 (0x00000005)]

@H1-N1 commented on GitHub (Mar 17, 2024): doesn't work i have the lastes update os and terminal [process exited with code 5 (0x00000005)]
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/terminal#17591