-
Notifications
You must be signed in to change notification settings - Fork 121
Unable to start program “C:\Program Files\dotnet\dotnet.exe” #807
Comments
@lkinsella are your running a x86 or x64 version of Windows? |
Windows 8.1 x64, generally running VS as an Administrator as well. |
Does |
I installed the x86 SDK installer and that created the latter (I've uninstalled it now), however VS still didn't play ball. I also tried VS Code and that can run and debug fine. |
@abpiskunov any ideas? |
I may try completely uninstalling VS and Core over the weekend and then reinstalling and see what happens. |
In your case we just run it via cmd line shell. Sample command line would look like this: C:\WINDOWS\system32\cmd.exe /c ""C:\Program Files\dotnet\dotnet.exe" "c:\users\xxx\documents\visual studio 2015\Projects\ConsoleApp4\src\ConsoleApp4\bin\Debug\netcoreapp1.0\ConsoleApp4.dll" & pause" So it looks like cmd shell is complaining in your case and i am wondering what would be different on your machine. Before running that command line we also merge all env variables for that process. So all env vars from current VS instance also would flow there. |
Yeh I can definitely manually do a build and run from the CLI but I'll try something akin to the above and see what the envars are like when I get in. I'll report back later. |
So I tried the command line you specified and that runs fine. I also uninstalled and reinstalled both VS2015 and .NET Core but it's still throwing the error. Environment variables for VS (according to Process Explorer):
|
i see that you have .dnx paths in your PATH env variable. Could you try to remove them just in case? |
I've nuked those but same issue. I've included the latest environment below for both VS and the instance of dotnet it appears to load, which I find odd as if it loads an instance (I assume for compilation/restore) then how does it not start? devenv.exe:
dotnet.exe (attached to devenv.exe, command line
|
I have the same issue. Unable to start C:\Program Files\dotnet\dotnet.exe Unhandled Exception: System.IO.IOException: Unable to read data from the transport connection: An established connection was aborted by the software in your host machine. ---> System.Net.Sockets.SocketException: An established connection was aborted by the software in your host machine Unhandled Exception: System.IO.IOException: Unable to read data from the transport connection: An established connection was aborted by the software in your host machine. ---> System.Net.Sockets.SocketException: An established connection was aborted by the software in your host machine |
@phillipsj you don't have the same issue, you have what ever exception says: some software on your machine prevents connection between VS and dotnet.exe. We saw example of that when firewalls or anti viruses did that. Please see you environment settings. (in the issue above dotnet has connection with VS and only when app is executed a command shell -cmd does not run dotnet.exe) |
Hi, has anyone had any luck finding the solution for this error? |
There were 2 different issues mentioned in this thread (1. when project can be executed, 2. when VS can not even connect to dotnet.exe) - what error do you have? |
The second one, "Unable to start program 'C:\Program Files\dotnet\dotnet.exe'. |
Did you able to get it work sebastianhoratiu ? if yes can you please share ? I have been scratching my head for this issue which i encountered recently while converting DNX project to .Net core 1.1 .. any suggestion/help appreciated.. |
Unfortunately not. I think only a re-install of Windows would fix it. |
It's decided!!!!!!!!!!!!!!!!!!!! Disable the program VPN. |
Try with adding Path "C:\Program Files\dotnet" to environment variables. It work for me. |
I've installed .NET Core 1.0.1 to use with VS 2015 Update 3 and I'm running as Administrator.
If I create any .NET Core project, be it console or web and attempt to run it Visual Studio then comes up with an error:
However I'm unable to ascertain why. I can run it from the CLI fine and non .NET Core works fine.
I've tried:
project.lock.json
.vs
folderAnd it still refuses to start.
The text was updated successfully, but these errors were encountered: