Visual Studio 2013 and 2015: Unable to start debugging on the web server. Could not start ASP.NET debugging – How to fix that

Visual Studio 2013 e 2015: Unable to start debugging on the web server. Could not start ASP.NET debugging - Come risolvere

If you’ve stumbled upon this post you most likely experienced the following error message when you tried to run your web application in debug mode:

Unable to start debugging on the web server. Could not start ASP.NET debugging. More information may be available by starting the project without debugging.


If you’ve recently upgraded your system to Windows 10 I strongly suggest to jump down to the URL Rewrite Module Broken paragraph and follow the advices below: otherwise, keep reading.

Despite what the error message says, starting the project without debugging won’t give you more informations. Luckily enough, the issue is fairly known to ASP.NET developers thanks to many threads on IT resources websites such as StackOverflow. The cause has almost always something to do with the Application Pool used by your web application – usually the DefaultAppPool, unless you’ve chosen otherwise – which stopped working for no apparent reason.

First thing you can do is to try to manually restart it. In order to do that, go to Control Panel > Amdministrative Tools > IIS Manager > Application Pools, then click on the DefaultAppPool with the right mouse button and choose Start. As soon as you do that, perform an iisreset, wait for the reset and then try again the debug with Visual Studio to see if the problem is gone. If that’s so, you’re done: otherwise, go back to the IIS Manager > Application Pools panel and check again the DefaultAppPool status: if it’s stopped again, it means that something on your system causes the Application Pool crash which you need to find out.

The most common causes preventing the Application Pools to behave like that are usually two:

  • Missing permissions in the Web Application folder.
  • URL Rewrite Module Broken, an issue which is often related to a system upgrade (for example, from Windows 8 or 8.1 o to Windows 10).

Let’s see how we can handle either of them.

Missing permissions

This issue has been experienced by many users and has been reported frequently (such as in this thread) in the IIS official forum. First thing to do is to check if your Web Application folder has sufficient permissions to allow access to the Application Pool. Ensure that either IIS_IUSRS and IUSR (or the user impersonated by the Application Pool if there’s a specific one) do have read and execute rights, otherwise:

  • Set up the missing permissions accordingly.
  • Restart the Application Pool from IIS Manager > Application Pool
  • Restart the IIS instance by opening a command prompt with administrative rights and typing iisreset.
  • Try again to run your web application using Visual Studio’s debug mode and check if the problem is gone.

Again, if the error is still there you need to check the DefaultAppPool status: if it’s automatically stopping again, keep reading.

URL Rewrite Module Broken

This kind of issue is most frequent following a system upgrade, usually from Windows 8.1 to Windows 10, due to the fact that the installation process can occasionally break the IIS URL Rewrite module 2.0. To see if that’s what happened to your system, open the Event Viewer from Control Panel > Administrative Tools > Event Viewer. Once you get there, check the Windows Registry > Application tab and look for Origin IIS-W3SVC-WP and ID event 2280 event logs: chances are you’ll find a lot of them.


Open one of them and check if the error message looks like the following:

The Module DLL C:\WINDOWS\system32\inetsrv\rewrite.dll failed to load.

If you get this text, you’ve find the root of your problem. Luckily enough, all you need to do to solve that is to uninstall and reinstall the URL Rewrite module using the Control Panel software uninstall panel. You can then get the updated version from the Microsoft Web Platform Installer or downloading it from the official site:

HipIISEngineStub.dll failed to load

If you’re using IIS7.0 in conjunction with an Antivirus such as McAfee you could also face a different error in your Event Viewer:

HipIISEngineStub.dll failed to load. The data is the error.

If you’re experiencing this, the proper solution seems to be the following:

  • Open the   file (you’ll need Administrator priviledges to do that).
  • Remove the following line from the   section:
  • Remove the following line from the   section:
  • Save the file and restart IIS.

Thanks to George M. (see comments below) and this post for this workaround.

That’s it for now: happy debug!


About Ryan

IT Project Manager, Web Interface Architect and Lead Developer for many high-traffic web sites & services hosted in Italy and Europe. Since 2010 it's also a lead designer for many App and games for Android, iOS and Windows Phone mobile devices for a number of italian companies.

View all posts by Ryan