Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Failed to initialize CoreCLR, HRESULT: 0x80004005

See original GitHub issue

I have a project with a tool defined in the project.json’s “tools” key. dotnet restore is able to find the tool and restore it succesfully.

However when I try to invoke the tool, I get the error:

`Failed to initialize CoreCLR, HRESULT: 0x80004005`

project.json of the tool.
project.json of the project that uses the tool.

What am I missing here?

Issue Analytics

State:
Created 8 years ago
Reactions:3
Comments:61 (28 by maintainers)

Top GitHub Comments

10reactions

kamilosxd678commented, Nov 2, 2016

I don’t know why this is closed, because .NET Core stability is some kind of a joke.

http://pastebin.com/raw/tdSdXDKa

I have to issue dotnet run command 37 TIMES before it actually works. THIRTY SEVEN GODDAMN TIMES OR MORE!

3reactions

markvinczecommented, Aug 14, 2017

Hmm, it turns out if I switch from the debian.8-x64 runtime to linux-x64, then it works.
Btw. what does the linux-x64 RID represent exactly? I found it in one of the examples repository, but I cannot find it on the page listing all the RIDs.

Top Results From Across the Web

How to fix exception "Failed to initialize CoreCLR, HRESULT

and I received in terminal "Failed to initialize CoreCLR, HRESULT: 0x80004005" I surfed internet, found solution to check permissions for ...

.Net application aborts at startup with "Failed to create ...

App runs successfully on OSX, but on Linux the app fails to start with Failed to create CoreCLR, HRESULT: 0x80004005 ...

Failed to initialize CoreCLR hresult: 0x80004005

I have created a new local project in VS Code and a new function app in Azure like described in this article:…

asp.net - Failed to create CoreCLR, HRESULT: 0x80004005

I have the same problem. One possibility it is coming is when the filesystem is read-only. It should be fixed as per github.com/dotnet/runtime/ ......

Published binaries: Failed to initialize CoreCLR, HRESULT

Published binaries: Failed to initialize CoreCLR, HRESULT: 0x80004005 ; State, Fixed F ; Affected Release, No affected release ; Target Release, 4.0 -...