The application was unable to start correctly 0xc0000142

[alexandrul]

• I was not able to find an open or closed issue matching what I'm seeing

Setup

• Which version of Git for Windows are you using? Is it 32-bit or 64-bit?

$ git --version --build-options

git version 2.23.0.windows.1
cpu: x86_64
built from commit: 4db2e5cc9e1522131a039cbad3970f147a39f0ce
sizeof-long: 4
sizeof-size_t: 8

• Which version of Windows are you running? Vista, 7, 8, 10? Is it 32-bit or 64-bit?

$ cmd.exe /c ver

Microsoft Windows [Version 6.1.7601]
64-bit

• What options did you set as part of the installation? Or did you choose the
  defaults?

> type "C:\Program Files\Git\etc\install-options.txt"

Editor Option: Notepad++
Custom Editor Path:
Path Option: Cmd
Plink Path: c:\Tools\PuTTY__x64\plink.exe
SSH Option: Plink
Tortoise Option: true
CURL Option: WinSSL
CRLF Option: CRLFCommitAsIs
Bash Terminal Option: ConHost
Performance Tweaks FSCache: Enabled
Use Credential Manager: Enabled
Enable Symlinks: Disabled
Enable Builtin Interactive Add: Disabled

Details

Random error dialogs when launching IntelliJ, unable to reproduce them reliably.

git exe - Application Error - alternative link

[alexandrul]

First time experiencing this issue (2.22.0 and older versions were working just fine).

[assarbad]

The error you are reporting is quite to the point.

The code 0xC0000142L is known as STATUS_DLL_INIT_FAILED:

{DLL Initialization Failed}
Initialization of the dynamic link library %hs failed. The process is terminating abnormally.

By the way: there's a slim chance that you can see that failure in the System or Application log with the Event Viewer (Win+R -> eventvwr.exe -> Return/Enter). But it's not certain.

If you are able to use ProcMon please do so and see if you can narrow it down to a single DLL failing to initialize. You will want to limit your view to "Show Process and Thread Activity" (the toolbar button with the Windows logo) and look for failures.

It's not per-se a problem if a DLL isn't found in one path, as long as other paths are being searched. But at some point it may end up having exhausted the path list and still not have found a matchign DLL name. This should stand out.

It'd be perfect if you could downgrade to a known-working version and do the same routine (with ProcMon) for comparison. This should pinpoint what DLL is the issue here.

You'll also want to ensure that IntelliJ executes the correct git.exe (which should be visible from ProcMon also).

[alexandrul]

@assarbad thank you so much for the instructions, I will reopen this issue if I will be able to get more details.