starred/terminal
1
0
Fork 0
mirror of https://github.com/microsoft/terminal.git synced 2026-02-03 21:25:34 +00:00
Code Issues 19.0k Packages Projects Releases 20 Wiki Activity

CMD, [process exited with code 3762504530 (0xe0434352)] #18174

New Issue
Closed
opened 2026-01-31 06:05:52 +00:00 by claunia · 11 comments
claunia commented 2026-01-31 06:05:52 +00:00
Owner
Copy Link

Originally created by @kevincrans on GitHub (Aug 13, 2022).

Windows Terminal version

1.14.196.3.0

Windows build number

1?.?.22518.1000

Other Software

At least any windowed app with a console in any relevant prompt except the powershell hotfix for this, when restarting for example after the app updated. Look at steps to reproduce for similar software having this issue.

Steps to reproduce

The program I'm using is unofficial, but Similar issues are #4981 and #6287.

Expected Behavior

I expected to application to continue and restart. I also expected terminal to be fixed and not powershell.

Actual Behavior

It showed me my system specifications like supposed, but gave me the following error:
[process exited with code 3762504530 (0xe0434352)]

Originally created by @kevincrans on GitHub (Aug 13, 2022). ### Windows Terminal version 1.14.196.3.0 ### Windows build number 1?.?.22518.1000 ### Other Software At least any windowed app with a console in any relevant prompt except the powershell hotfix for this, when restarting for example after the app updated. Look at steps to reproduce for similar software having this issue. ### Steps to reproduce The program I'm using is unofficial, but Similar issues are #4981 and #6287. ### Expected Behavior I expected to application to continue and restart. I also expected terminal to be fixed and not powershell. ### Actual Behavior It showed me my system specifications like supposed, but gave me the following error: `[process exited with code 3762504530 (0xe0434352)]`
claunia commented 2026-01-31 06:05:54 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Aug 15, 2022):

I mean, it just kinda sounds like whatever application you're running is returning a non-zero exit code. Refer to:

Why am I seeing [process exited with code ...]?

I'd file an issue upstream with whatever software you're using. If the application should be exiting cleanly, it should be returning 0. The Terminal displays that message by default so that when an application does return an error, you can view its output.

@zadjii-msft commented on GitHub (Aug 15, 2022): I mean, it just kinda sounds like whatever application you're running is returning a non-zero exit code. Refer to: [Why am I seeing `[process exited with code ...]`?](https://github.com/microsoft/terminal/wiki/Frequently-Asked-Questions-(FAQ)#why-am-i-seeing-process-exited-with-code-) I'd file an issue upstream with whatever software you're using. If the application should be exiting cleanly, it should be returning `0`. The Terminal displays that message by default so that when an application does return an error, you can view its output.
claunia commented 2026-01-31 06:05:54 +00:00
Author
Owner
Copy Link

@Mrgaton commented on GitHub (Aug 22, 2022):

i got the same problem tryng to run my c# app 😢

[proceso terminado con el código 3762504530 (0xe0434352)]

@Mrgaton commented on GitHub (Aug 22, 2022): i got the same problem tryng to run my c# app 😢 [proceso terminado con el código 3762504530 (0xe0434352)]
claunia commented 2026-01-31 06:05:54 +00:00
Author
Owner
Copy Link

@Mrgaton commented on GitHub (Aug 22, 2022):

aparently is when i write something in the console.readline()

@Mrgaton commented on GitHub (Aug 22, 2022): aparently is when i write something in the console.readline()
claunia commented 2026-01-31 06:05:54 +00:00
Author
Owner
Copy Link

@DHowett commented on GitHub (Aug 23, 2022):

This error code means that your C# application is crashing with a "COM+" error. Terminal has displayed it so that you know what is going on!

@DHowett commented on GitHub (Aug 23, 2022): This error code means that your C# application is crashing with a "COM+" error. Terminal has displayed it so that you know what is going on!
claunia commented 2026-01-31 06:05:54 +00:00
Author
Owner
Copy Link

@Mrgaton commented on GitHub (Aug 23, 2022):

But only happens when i runned on windows terminal

@Mrgaton commented on GitHub (Aug 23, 2022): But only happens when i runned on windows terminal
claunia commented 2026-01-31 06:05:55 +00:00
Author
Owner
Copy Link

@kevincrans commented on GitHub (Aug 23, 2022):

@zadjii-msft < Someone already did, but it's lazy to say all the app makers fix it individually, while it's clearly a terminal issue, like @Mrgaton stated.
Did u even look into the powershell issue?
However, still thanks for giving insight, we could all use some of that.

@kevincrans commented on GitHub (Aug 23, 2022): @zadjii-msft < Someone already did, but it's lazy to say all the app makers fix it individually, while it's clearly a terminal issue, like @Mrgaton stated. Did u even look into the powershell issue? However, still thanks for giving insight, we could all use some of that.
claunia commented 2026-01-31 06:05:55 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Aug 23, 2022):

Of course it only happens on the Windows Terminal, conhost (the vintage console) never had any code to handle anything like this. If an app crashed running in conhost, it'd just disappear itself, which doesn't provide any useful information. Providing an error code is certainly useful - best practice has always been to return 0 if your process exits cleanly, and I'd want to know if my app wasn't for whatever reason.

You can always tell the terminal to just ignore this by settings closeOnExit: always.

I haven't looked more into the root of this, because there were no minimal repro steps in the OP 😉

@zadjii-msft commented on GitHub (Aug 23, 2022): Of course it only happens on the Windows Terminal, conhost (the vintage console) never had any code to handle anything like this. If an app crashed running in conhost, it'd just disappear itself, which doesn't provide any useful information. Providing an error code is certainly useful - best practice has _always_ been to return 0 if your process exits cleanly, and I'd want to know if my app wasn't for whatever reason. You can always tell the terminal to just ignore this by settings `closeOnExit: always`. I haven't looked more into the root of this, because there were no minimal repro steps in the OP 😉
claunia commented 2026-01-31 06:05:55 +00:00
Author
Owner
Copy Link

@Mrgaton commented on GitHub (Aug 23, 2022):

I only know that's the program crashes on the console.readlline() I tested out

@Mrgaton commented on GitHub (Aug 23, 2022): I only know that's the program crashes on the console.readlline() I tested out
claunia commented 2026-01-31 06:05:55 +00:00
Author
Owner
Copy Link

@lamplt commented on GitHub (Nov 4, 2022):

I encountered it while obfuscating the dlls via a post build script. It looks like .exe was invoked before the obfuscation was completed. But the .exe is working well after that. So I just ignored it.

@lamplt commented on GitHub (Nov 4, 2022): I encountered it while obfuscating the dlls via a post build script. It looks like .exe was invoked before the obfuscation was completed. But the .exe is working well after that. So I just ignored it.
claunia commented 2026-01-31 06:05:55 +00:00
Author
Owner
Copy Link

@GitHub-source-42 commented on GitHub (Oct 10, 2024):

Same Error Code when Lauching Powershell through VS Code or directly from "C:\Program Files\PowerShell\7\pwsh.exe"

PowerShell 7.4.5

An error has occurred that was not properly handled. Additional information is shown below. The PowerShell process will exit.
Unhandled exception. System.Management.Automation.CmdletInvocationException: The type initializer for '' threw an exception.
---> System.TypeInitializationException: The type initializer for '' threw an exception.
---> System.IO.FileNotFoundException: Could not load file or assembly 'WinRT.Runtime, Version=2.0.0.0, Culture=neutral, PublicKeyToken=99ea127f02d97709'. The system cannot find the file specified.
File name: 'WinRT.Runtime, Version=2.0.0.0, Culture=neutral, PublicKeyToken=99ea127f02d97709'
at WinRT.ProjectionInitializer.InitalizeProjection()
at .cctor()
--- End of inner exception stack trace ---
at Microsoft.WinGet.Client.Commands.FindPackageCmdlet.ProcessRecord()
at System.Management.Automation.CommandProcessor.ProcessRecord()
--- End of inner exception stack trace ---
at System.Management.Automation.Runspaces.AsyncResult.EndInvoke()
at System.Management.Automation.PowerShell.EndInvoke(IAsyncResult asyncResult)
at System.Threading.Tasks.TaskFactory1.FromAsyncCoreLogic(IAsyncResult iar, Func2 endFunction, Action1 endAction, Task1 promise, Boolean requiresSynchronization)
--- End of stack trace from previous location ---
at Microsoft.WinGet.CommandNotFound.WinGetCommandNotFoundFeedbackPredictor.WarmUp()
at System.Threading.Tasks.Task.<>c.b__128_1(Object state)
at System.Threading.QueueUserWorkItemCallback.Execute()
at System.Threading.ThreadPoolWorkQueue.Dispatch()
at System.Threading.PortableThreadPool.WorkerThread.WorkerThreadStart()

@GitHub-source-42 commented on GitHub (Oct 10, 2024): Same Error Code when Lauching Powershell through VS Code or directly from "C:\Program Files\PowerShell\7\pwsh.exe" PowerShell 7.4.5 An error has occurred that was not properly handled. Additional information is shown below. The PowerShell process will exit. Unhandled exception. System.Management.Automation.CmdletInvocationException: The type initializer for '<Module>' threw an exception. ---> System.TypeInitializationException: The type initializer for '<Module>' threw an exception. ---> System.IO.FileNotFoundException: Could not load file or assembly 'WinRT.Runtime, Version=2.0.0.0, Culture=neutral, PublicKeyToken=99ea127f02d97709'. The system cannot find the file specified. File name: 'WinRT.Runtime, Version=2.0.0.0, Culture=neutral, PublicKeyToken=99ea127f02d97709' at WinRT.ProjectionInitializer.InitalizeProjection() at .cctor() --- End of inner exception stack trace --- at Microsoft.WinGet.Client.Commands.FindPackageCmdlet.ProcessRecord() at System.Management.Automation.CommandProcessor.ProcessRecord() --- End of inner exception stack trace --- at System.Management.Automation.Runspaces.AsyncResult.EndInvoke() at System.Management.Automation.PowerShell.EndInvoke(IAsyncResult asyncResult) at System.Threading.Tasks.TaskFactory`1.FromAsyncCoreLogic(IAsyncResult iar, Func`2 endFunction, Action`1 endAction, Task`1 promise, Boolean requiresSynchronization) --- End of stack trace from previous location --- at Microsoft.WinGet.CommandNotFound.WinGetCommandNotFoundFeedbackPredictor.WarmUp() at System.Threading.Tasks.Task.<>c.<ThrowAsync>b__128_1(Object state) at System.Threading.QueueUserWorkItemCallback.Execute() at System.Threading.ThreadPoolWorkQueue.Dispatch() at System.Threading.PortableThreadPool.WorkerThread.WorkerThreadStart()
claunia commented 2026-01-31 06:05:56 +00:00
Author
Owner
Copy Link

@DHowett commented on GitHub (Oct 10, 2024):

You are commenting with a powershell issue on a thread that clearly seems to be about CMD.
Please file your bug on the powershell repository.

@DHowett commented on GitHub (Oct 10, 2024): You are commenting with a powershell issue on a thread that clearly seems to be about CMD. Please file your bug on [the powershell repository](https://github.com/powershell/powershell).
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 Issue-Bug Issue-Question Needs-Tag-Fix Needs-Triage Resolution-Answered
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#18174
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?