Visual Studio 2015 Update 1 - No IIS Express Response While Debugging

Question

I have an error in my code development environment. I can't solve it and I can't work properly rightnow.

Details:
I'm working with "Visual Studio 2015 Update 1", "Windows 8.1 ( with latest updates )". I'm launching one webapi2(resource service) and two asp.net mvc applications(backend and frontend) in Visual Studio Start - debug mode. We are using IIS express not local IIS (inetmgr) because my team mates don't want to run solution in it.

Here is the start action of one project:

The problem is:
When I (start)launch the Visual Studio for debug mode; Visual Studio opens the browser but applications won't work. Sites are stay at loading mode. It's kinda stuck. I mean; Browser is still waiting a response from IISexpress to show, but there is no response there. Here is what I saw (Yükleniyor means Loading...):

If I wait too long, Browser-IIS will give this error: "HTTP Error 403.14 - Forbidden The Web server is configured to not list the contents of this directory."

And I see this message in Diagnosic Tools Window: "The thread 0x3714 has exited with code 0 (0x0). The thread 0x2780 has exited with code 0 (0x0). The thread 0x35d0 has exited with code 0 (0x0). etc etc...". There is no error message from Visual Studio. How can I solve this problem ?

Important Note:
If I restart Visual Studio, I can debug the application JUST one time!. If I click the stop and run again, the problem comes back.

Another Note: I tried to contact with Microsoft. I wrote the same problem to them. But 2 weeks pasted, they are not returned back yet.

I tried already:
Working in release mode
Open Visual Studio in Safe Mode.
Restore Visual Studio
Uninstall and reinstall Visual Studio
Uninstall and reinstall IIS Express
Uninstall only VS update 1
Tried in another 2 computers ( Solution and applications are working well. )

Answer 1

In my system the problem seems to be solved. I updates the following items by "Tools/Extensions and Updates ..." menu of Visual Studio 2015:

1. Microsoft ASP Net Web Framework And Tools (Version 5.2.40204.0).
2. Microsoft ASP Net Web Tools (Version 14.201.20203.0).
3. Web Essentials 2015.1 (Version 1.0.207).

I think the problem was solved by update N. 2, but for completeness I reported all items updated.

Answer 2

The issue seems similar to the one I am experiencing in an ASP.NET MVC app. SignalR v2.2.0 was the culprit in my case and the temporary easy fix that worked for me was to replace app.MapSignalR(); in my Startup class with this:

 var task=Task.Run(()=>app.MapSignalR());
 task.Wait(300);
 if (task.IsCanceled)
 {
     Task.Run(() => app.MapSignalR()).Wait(300);
 }

This solution was provided by JonasSyrstad on this SignalR issue thread, along with other useful info: github.com/SignalR/SignalR/issues/3414#issuecomment-75537540

Apparently, the problem is not specific to SignalR. You can find more details in Kaspars Ozols' answer on another thread: https://stackoverflow.com/a/34227866/4491770