I am trying to run any program on visual studio 2013 update 3 and I get the following alert box :
Process with an ID #### is not running .
// every tim
@Kilanny your answer is correct. Most machines in 2015 are 64bit, so there's a lot of chances that you just need to enable the 64bit option under the Tools main navigation link menu. No need to configure other files or hard code ports. Besides, port assignment should be dynamic. This fix applies to 2013 With Update 3 and Visual Studio 2015 Community Edition.
Check the images below for a mini tutorial: (I'm just improving Kilanny's answer)
The following steps fix the problem for Visual Studio 2015 and Visual Studio 2017:
.vs
folder.F5
and IIS Express should load as normal, allowing you to debug.Note: Based on my experience and others in the comments, this problem seems to be caused by moving a project between workstations, environments, or versions of Visual Studio. There must be some environment specific information contained in the
.vs
folder.
Then the problem maybe due to Visual Studio use of 32-bit IIS-Express.
Solution: In Visual Studio, go to Tools menu > Options > Projects and Solutions > Web Projects > Enable the option "Use the 64 bit version of IIS Express" and click ok
I tried the first error and that didn't help me. However What did work for me was to delete the hidden ".vs" folder which is at the solution root.
This can happen for various reasons, helpfully - if you run IISExpress.exe
(\Program Files (x86)\IISExpress\iisexpress.exe
for 32-bit, \Program Files\IISExpress\iisexpress.exe
for 64-bit) in the command line, you'll get some more details. In my case:
C:\Program Files\IIS Express>iisexpress.exe
Filename: \\?\C:\Users\My.Username\Documents\IISExpress\config\applicationhost.config
Line number: 15
Error: Configuration file is not well-formed XML
Nice and easy to fix, that one my was my fault though!
It looks like there are many solutions that work and some that don't...
My issue kept surfacing after a few test iterations. Yes restarting the PC and/or VS would resolve the issue...but temporarily.
My solution was to undo a security change I had enabled a couple days earlier to
Controlled folder access
underRansomware protection
.
I undid this change by:
(right click Start)
Setting->Update & Security->Windows Security->Virus & threat protection-> Virus & threat protection settings->Manage settings
Under Controlled folder access Click->Manage Controlled folder access (this is also the Ransomware protection screen)
Turn Controlled folder access off.
This was 100% the issue for me as I was able to run my test without restarting VS.