Visual Studio 2013 > New project > unspecified error (exception from hresult: 0x80004005 (e_fail))

Question

Can anybody shed any light on the above error? I\'ve tried with both Express and Ultimate editions of VS 2013.

I\'m running 64-bit Windows 7.

Solutions to si

Answer 1

I had the same error. I solved the error by running Visual Studio 2013 at "run as administrator" mode as when you use web application projects IIS Express is involved.

Answer 2

I was facing the same issue. I was selecting the 'Empty' MVC project template and was getting the same error again and again.

I tried selecting the 'MVC' project template and got the same error to.

Doing a bit of googling showed that a messed up application host config file of IIS express can also cause the problem. I had only one site configured in IIS express and I tried to host that from command prompt. That's when it showed me the error in applicationHostConfig file of IIS express including line number where the error was. I was playing with the file in the past and added a site without specifying the name.

Fixing that problem solved the issue for me.

Answer 3

Removing Read Only property from IISExpress\Config files (applicationhost, aspnet, redirection) solved the problem for me.

Answer 4

I'm using Windows 8 x64 and i've found a solution by installing IIS Express 8 x64.

http://www.microsoft.com/en-us/download/details.aspx?id=34679

Answer 5

I had the same issue and scavenged the internet for solutions, because I did not want to reinstall VS 2013, only to find my solution in someone else's problem (oh the irony).

I had this error because my applicationhost.config was blank. I figured this part out when I realised that the project was created, just not added to the solution. So, I tried adding the project manually and it claimed that there was an error in applicationhost.config file. I go to see it, and it was empty.
For whatever reason this happens, it stops the IISexpress.exe from working either.
So, I deleted the applicationhost.config file and tried adding the project to the solution, and voila, everything works like a charm.

Answer 6

Have you tried to manually install NuGet for VS 2013?

I had a similar issue, until I found that the VS 2013 setup - for some reason - did not install the NuGet package manager. After I installed it manually everything worked fine.