microsoft / microsoft/terminal

Application cannot start new process Error: 0xc0000142

Open
#18,874 4 comments 0 reactions 0 assignees View on GitHub
Issue-Bug Needs-Attention Needs-Triage Product-Conhost
Dominant language
C++
Stars
105k
Forks
9.6k
Avg merge
3d 17h
Merged PRs (30d)
29

Description

### Windows Terminal version

1.22.11141.0

### Windows build number

10.0.22631.5262

### Other Software

ingres 10, compiled with Viscual C++ 2010

### Steps to reproduce

Using database 4GL software (ingres 10), which works perfect in old cmd windows with legacy mode. Without legacy mode, I have the problem, if the software try to start a new process with CreateProcess() it fails, error message:
cmd.exe - Application Error The application was unable to start correctly (0xc0000142). Click OK to close the application.
Sytemcalls with system() inside the 4GL code works.
Exact the same problem with windows terminal 1.22.11141.0 and with preview 1.23.11132.0
I make a small test C program, compiled with VC 2010, using nearly the same code, as inside the ingres application (CreateProcess...) works without problems.

### Expected Behavior

no error message and starting the process like cmd with legacy mode

### Actual Behavior

error message:
cmd.exe - Application Error The application was unable to start correctly (0xc0000142). Click OK to close the application.

Contributor guide

Open the contributing guide

Research direction

Start by reproducing the failure with Ingres 10 on Windows Terminal 1.22.11141.0, comparing legacy and non-legacy modes. Compare the application's CreateProcess() path with the small VC 2010 C program and the system() behavior. Done means cmd.exe starts without error in non-legacy mode, matching legacy mode.

Written by the indexing model from the issue text.

Assessment

Tech stack
cpp
Domain
cli, operating-systems
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
32/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.