PowerShell exits with code 0xE0434352 (EXCEPTION_COMPLUS) #8723

Closed
opened 2026-01-31 01:36:24 +00:00 by claunia · 26 comments
Owner

Originally created by @jackfoxy on GitHub (Jun 1, 2020).

Environment

Windows build number: 10.0.19041.0 Microsoft Windows NT 10.0.19041.0
Windows Terminal version (if applicable): 1.0.1401.0

other software:
PowerShell 7.0.1
git version 2.18.0.windows.1
posh-git https://github.com/dahlbyk/posh-git

Steps to reproduce

not sure I can always reproduce this
last time was running git push twice

MsTerminalCrash

Expected behavior

do not crash

Actual behavior

[process exited with code 3762504530]

Originally created by @jackfoxy on GitHub (Jun 1, 2020). <!-- 🚨🚨🚨🚨🚨🚨🚨🚨🚨🚨 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 ``` Windows build number: 10.0.19041.0 Microsoft Windows NT 10.0.19041.0 Windows Terminal version (if applicable): 1.0.1401.0 other software: PowerShell 7.0.1 git version 2.18.0.windows.1 posh-git https://github.com/dahlbyk/posh-git ``` # Steps to reproduce not sure I can always reproduce this last time was running git push twice ![MsTerminalCrash](https://user-images.githubusercontent.com/1824476/83370731-1a8a6500-a375-11ea-8c44-ab57a4a454c9.png) # Expected behavior do not crash # Actual behavior [process exited with code 3762504530]
Author
Owner

@zadjii-msft commented on GitHub (Jun 1, 2020):

@jackfoxy Does this repro in the legacy console host too, or just the Windows Terminal?

@zadjii-msft commented on GitHub (Jun 1, 2020): @jackfoxy Does this repro in the legacy console host too, or just the Windows Terminal?
Author
Owner

@jackfoxy commented on GitHub (Jun 1, 2020):

@zadjii-msft I use cmdr to get multi-tab terminal
My implementation of cmdr still uses posh-git, but is currently pointed to a previous PS build

Major  Minor  Build  Revision
-----  -----  -----  --------
5      1      19041  1

I have never had these PS crashes in cmdr. MS Terminal starts crashing on me almost immediately. Sometimes the crash closes the window, sometimes it does not and I see the exit code

@jackfoxy commented on GitHub (Jun 1, 2020): @zadjii-msft I use cmdr to get multi-tab terminal My implementation of cmdr still uses posh-git, but is currently pointed to a previous PS build ``` Major Minor Build Revision ----- ----- ----- -------- 5 1 19041 1 ``` I have never had these PS crashes in cmdr. MS Terminal starts crashing on me almost immediately. Sometimes the crash closes the window, sometimes it does not and I see the exit code
Author
Owner

@DHowett commented on GitHub (Jun 5, 2020):

Is this, perchance, happening when you press Ctrl+C? The exit code maps to E0434352, which is a .NET issue. I'm surprised that Terminal can cause that.

If you use the vintage console host and run the following, does it eventually crash?

$Host.UI.RawUI.BufferSize=$Host.UI.RawUI.WindowSize
@DHowett commented on GitHub (Jun 5, 2020): Is this, perchance, happening when you press <kbd>Ctrl+C</kbd>? The exit code maps to `E0434352`, which is a .NET issue. I'm surprised that Terminal can cause that. If you use the vintage console host and run the following, does it eventually crash? ```powershell $Host.UI.RawUI.BufferSize=$Host.UI.RawUI.WindowSize ```
Author
Owner

@jackfoxy commented on GitHub (Jun 5, 2020):

I just ran a dotnet build and pressed ctrl+c immediately. Build cancelled, no problem.

@jackfoxy commented on GitHub (Jun 5, 2020): I just ran a `dotnet build` and pressed `ctrl+c` immediately. Build cancelled, no problem.
Author
Owner

@zadjii-msft commented on GitHub (Jun 9, 2020):

I'm going to leave this open for now, but unless we can get a consistent repro, I'm not sure there's much we can do about this 😕

@zadjii-msft commented on GitHub (Jun 9, 2020): I'm going to leave this open for now, but unless we can get a consistent repro, I'm not sure there's much we can do about this 😕
Author
Owner

@loicwolff commented on GitHub (Jul 30, 2020):

I'm having the issue with Powershell Core (installed using Scoop).

To reproduce, go to C:\ (or anywhere with a big number of items in the hierarchy), run Get-ChildItem -Recurse and hit Ctrl + C.

Environment

Platform ServicePack Version      VersionString
-------- ----------- -------      -------------
 Win32NT             10.0.18363.0 Microsoft Windows NT 10.0.18363.0

Windows Terminal version: 1.1.2021.0

@loicwolff commented on GitHub (Jul 30, 2020): I'm having the issue with Powershell Core (installed using Scoop). To reproduce, go to `C:\` (or anywhere with a big number of items in the hierarchy), run `Get-ChildItem -Recurse` and hit `Ctrl + C`. Environment ``` Platform ServicePack Version VersionString -------- ----------- ------- ------------- Win32NT 10.0.18363.0 Microsoft Windows NT 10.0.18363.0 ``` Windows Terminal version: `1.1.2021.0`
Author
Owner

@liesauer commented on GitHub (Aug 12, 2020):

same here.

PowerShell 6.2.4
Copyright (c) Microsoft Corporation. All rights reserved.

https://aka.ms/pscore6-docs
Type 'help' to get help.

Loading personal and system profiles took 1467ms.
C:\Users\me> cd e:
E:\> cd .\Projects\
E:\Projects> cd .\test\
E:\Projects\test [dev ↑2 +0 ~6 -0 !]> git pull

[已退出进程,代码为 3221225786]
@liesauer commented on GitHub (Aug 12, 2020): same here. ``` PowerShell 6.2.4 Copyright (c) Microsoft Corporation. All rights reserved. https://aka.ms/pscore6-docs Type 'help' to get help. Loading personal and system profiles took 1467ms. C:\Users\me> cd e: E:\> cd .\Projects\ E:\Projects> cd .\test\ E:\Projects\test [dev ↑2 +0 ~6 -0 !]> git pull [已退出进程,代码为 3221225786] ```
Author
Owner

@zadjii-msft commented on GitHub (Aug 12, 2020):

Oh hmm, @DHowett any chance this is related to that "global dotnet tool ctrl-c" issue we were seeing a few months ago? #3869 perchance?

@zadjii-msft commented on GitHub (Aug 12, 2020): Oh hmm, @DHowett any chance this is related to that "global dotnet tool ctrl-c" issue we were seeing a few months ago? #3869 perchance?
Author
Owner

@DHowett commented on GitHub (Aug 12, 2020):

Yes. If you are seeing this with PowerShell 6 specifically, or any version of powershell installed via scoop, this is because the powershell wrapper is being terminated when you press ctrl+c. It should not be doing that. This is an upstream bug that is already being tracked on the scoop repository.

@DHowett commented on GitHub (Aug 12, 2020): Yes. If you are seeing this with PowerShell 6 _specifically_, or _any version of powershell installed via scoop_, this is because the powershell wrapper is being terminated when you press ctrl+c. It should not be doing that. This is an upstream bug that is already being tracked on the scoop repository.
Author
Owner

@DHowett commented on GitHub (Aug 13, 2020):

/dup https://github.com/lukesampson/scoop/issues/3634

@DHowett commented on GitHub (Aug 13, 2020): /dup https://github.com/lukesampson/scoop/issues/3634
Author
Owner

@ghost commented on GitHub (Aug 13, 2020):

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 13, 2020): 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!
Author
Owner

@jackfoxy commented on GitHub (Aug 13, 2020):

I know for sure I did not install powershell with scoop

@jackfoxy commented on GitHub (Aug 13, 2020): I know for sure I did not install powershell with scoop
Author
Owner

@DHowett commented on GitHub (Aug 13, 2020):

@jackfoxy can you run gcm -all pwsh?

@DHowett commented on GitHub (Aug 13, 2020): @jackfoxy can you run `gcm -all pwsh`?
Author
Owner

@liesauer commented on GitHub (Aug 13, 2020):

I know for sure I did not install powershell with scoop

+1

@liesauer commented on GitHub (Aug 13, 2020): > I know for sure I did not install powershell with scoop +1
Author
Owner

@DHowett commented on GitHub (Aug 13, 2020):

If you are seeing this with PowerShell 6 specifically

@liesauer based on your comment, this applies to you. If you didn’t install via scoop but you’re seeing this issue, that statement applies to you.

Can you also run the gcm command i asked @jackfoxy to run?

@DHowett commented on GitHub (Aug 13, 2020): > If you are seeing this with PowerShell 6 specifically @liesauer based on your comment, this applies to you. If you didn’t install via scoop but you’re seeing this issue, that statement applies to you. Can you also run the `gcm` command i asked @jackfoxy to run?
Author
Owner

@liesauer commented on GitHub (Aug 13, 2020):

@DHowett

C:\Users\aaa> gcm -all pwsh

CommandType     Name                                               Version    Source
-----------     ----                                               -------    ------
Application     pwsh.exe                                           0.0.0.0    C:\Users\aaa\.dotnet\tools\pwsh.exe
@liesauer commented on GitHub (Aug 13, 2020): @DHowett ``` C:\Users\aaa> gcm -all pwsh CommandType Name Version Source ----------- ---- ------- ------ Application pwsh.exe 0.0.0.0 C:\Users\aaa\.dotnet\tools\pwsh.exe ```
Author
Owner

@DHowett commented on GitHub (Aug 13, 2020):

@liesauer you’re seeing https://github.com/PowerShell/PowerShell/issues/11314, which has been fixed in newer versions of PowerShell’s dotnet global tool wrapper. I’m not sure how to update the shim specifically if a standard tool update doesn’t do it.

@DHowett commented on GitHub (Aug 13, 2020): @liesauer you’re seeing https://github.com/PowerShell/PowerShell/issues/11314, which has been fixed in newer versions of PowerShell’s dotnet global tool wrapper. I’m not sure how to update the shim specifically if a standard tool update doesn’t do it.
Author
Owner

@liesauer commented on GitHub (Aug 13, 2020):

@DHowett i will try updating powershell later and see if still have this issue.

@liesauer commented on GitHub (Aug 13, 2020): @DHowett i will try updating powershell later and see if still have this issue.
Author
Owner

@DHowett commented on GitHub (Aug 13, 2020):

Thanks! Let me know if it works out.

@DHowett commented on GitHub (Aug 13, 2020): Thanks! Let me know if it works out.
Author
Owner

@liesauer commented on GitHub (Aug 13, 2020):

@DHowett it works! thanks!

PowerShell 7.0.3
Copyright (c) Microsoft Corporation. All rights reserved.

https://aka.ms/powershell
Type 'help' to get help.

Loading personal and system profiles took 1721ms.
C:\Users\aaa> cd e:
E:\> cd .\Projects\
E:\Projects> cd .\project\
E:\Projects\project [dev ↑2 +0 ~6 -0 !]> git pull
E:\Projects\project [dev ↑2 +0 ~6 -0 !]>
@liesauer commented on GitHub (Aug 13, 2020): @DHowett it works! thanks! ``` PowerShell 7.0.3 Copyright (c) Microsoft Corporation. All rights reserved. https://aka.ms/powershell Type 'help' to get help. Loading personal and system profiles took 1721ms. C:\Users\aaa> cd e: E:\> cd .\Projects\ E:\Projects> cd .\project\ E:\Projects\project [dev ↑2 +0 ~6 -0 !]> git pull E:\Projects\project [dev ↑2 +0 ~6 -0 !]> ```
Author
Owner

@jackfoxy commented on GitHub (Aug 13, 2020):

@DHowett

PowerShell 7.0.2
Copyright (c) Microsoft Corporation. All rights reserved.

https://aka.ms/powershell
Type 'help' to get help.

   A new PowerShell stable release is available: v7.0.3
   Upgrade now, or check out the release page at:
     https://aka.ms/PowerShell-Release?tag=v7.0.3

PS E:\GitRepos> gcm -all pwsh

CommandType     Name                                               Version    Source
-----------     ----                                               -------    ------
Application     pwsh.exe                                           7.0.2.0    C:\Program Files\PowerShell\7\pwsh.exe
@jackfoxy commented on GitHub (Aug 13, 2020): @DHowett ``` PowerShell 7.0.2 Copyright (c) Microsoft Corporation. All rights reserved. https://aka.ms/powershell Type 'help' to get help. A new PowerShell stable release is available: v7.0.3 Upgrade now, or check out the release page at: https://aka.ms/PowerShell-Release?tag=v7.0.3 PS E:\GitRepos> gcm -all pwsh CommandType Name Version Source ----------- ---- ------- ------ Application pwsh.exe 7.0.2.0 C:\Program Files\PowerShell\7\pwsh.exe ```
Author
Owner

@DHowett commented on GitHub (Aug 13, 2020):

Okay, thanks everyone. I closed this because most of the commenters reported a Ctrl+C issue, which is actually off-topic for this thread. That was not the right resolution, as that's not what this bug was reporting. 😄

@DHowett commented on GitHub (Aug 13, 2020): Okay, thanks everyone. I closed this because _most of the commenters_ reported a <kbd>Ctrl+C</kbd> issue, which is actually off-topic for this thread. That was not the right resolution, as that's not what this bug was reporting. :smile:
Author
Owner

@DHowett commented on GitHub (Aug 13, 2020):

As best as I can tell, Terminal is the messenger here--it's reporting that PowerShell has been unexpectedly terminated due to an exception. This issue should be filed on the PowerShell repository.

@DHowett commented on GitHub (Aug 13, 2020): As best as I can tell, Terminal is the messenger here--it's reporting that PowerShell has been unexpectedly terminated due to an exception. This issue should be filed on the [PowerShell repository](https://github.com/PowerShell/PowerShell).
Author
Owner

@zadjii-msft commented on GitHub (Nov 1, 2021):

@jackfoxy Did you ever figure this out, or report this at the PowerShell repo? From the looks of things, this is a PowerShell bug of some sort that the Terminal happens to be catching. I'm sure their team would have a better job diagnosing the issue.

@zadjii-msft commented on GitHub (Nov 1, 2021): @jackfoxy Did you ever figure this out, or report this at the PowerShell repo? From the looks of things, this is a PowerShell bug of some sort that the Terminal happens to be catching. I'm sure their team would have a better job diagnosing the issue.
Author
Owner

@jackfoxy commented on GitHub (Nov 1, 2021):

@zadjii-msft I haven't experienced this in a long time.

@jackfoxy commented on GitHub (Nov 1, 2021): @zadjii-msft I haven't experienced this in a long time.
Author
Owner

@zadjii-msft commented on GitHub (Nov 1, 2021):

Even better! Thanks for following up.

@zadjii-msft commented on GitHub (Nov 1, 2021): Even better! Thanks for following up.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/terminal#8723