Failed to initialize CoreCLR, HRESULT: 0x80131500
See original GitHub issueSteps to reproduce
- Download https://dotnetcli.blob.core.windows.net/dotnet/beta/Binaries/Latest/dotnet-dev-centos-x64.latest.tar.gz
- Unpack tar file
- Set DOTNET_HOME as unzipped folder. [usr/share/dotnet]
- Change permission settings for unzipped folder dotnet
- run dotnet -version
Expected behavior
Should give version number
Actual behavior
Gives error message Failed to initialize Failed to initialize CoreCLR, HRESULT: 0x80131500
Environment data
dotnet --version
output:
Failed to initialize CoreCLR, HRESULT: 0x80131500
Issue Analytics
- State:
- Created 7 years ago
- Reactions:2
- Comments:70 (11 by maintainers)
Top Results From Across the Web
Failed to initialize CoreCLR, HRESULT: 0x80131500 #5455
I'm trying it on Fedora 23 (downloaded Centos binaries). I know that Fedora is not listed in supported distributions but I just wanted...
Read more >GCP - Failed to initialize CoreCLR, HRESULT: 0x80131500
I'm trying to go through the App Engine Quickstart tutorial for .Net and running into a problem with the dotnet cli.
Read more >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:…
Read more >Issue with VSTS Agent on Ubuntu – Failed to initialize ...
Failed to initialize CoreCLR, HRESULT : 0x80131500. I received this error message when trying to run the “config.sh” command ;.
Read more >Announcing .NET Core 1.0
Devs will start using these, and MS will have them hooked. ... Failed to initialize CoreCLR, HRESULT: 0x80131500. $ mkdir hwapp. $ cd...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
You can find out what is missing by running:
Replace
/opt/dotnet
with the directory you “un-tarred” the tar ball to.This seems to have solved my issue 😕