Microsoft HTTPAPI/2.0 use Port 80 – Cannot Start WAMP Apache

Screenshot of Microsoft Web Deployment Service

Microsoft Web Deployment Service

I just installed fresh Microsoft Windows 7, and I installed WAMP for my APACHE – PHP server. When I want to start the server, the WAMP icon turn yellow (not green). Upon further investigation, I found out that when I go to WAMP dock icon -> Apache -> Service -> Test Port 80, I received a message that Port 80 is used Microsoft HTTPAPI/2.0.

I fire up Google and most of the solutions mentioned about turning off Microsoft SQL Server Reporting Services (SSRS). I have browsed my Services and couldn’t find any SSRS installed (although I have SQL Server 2008 Express installed).

Luckily I came across this forum which gives me the solution.

We must stop Web Deployment Agent Service (MsDepSvc) from Administrative Tools > Services area. You can disable the service, to have port 80 ready when you boot your system.

The following article will explain about this service, you can follow the link below to read more.

Microsoft Web Deploy

Web Deploy is a free technology built by my team that can improve web deployment. It is a deployment service that runs on a server, and enables you to either locally or remotely deploy applications onto it. Web Deploy includes built-in support for creating virtual directories and applications within IIS, copying files and folders, provisioning databases (both SQL Server and MySQL), setting file-system ACLs and more (it even includes built-in providers for things like setting registry entries, registering COM components, etc). In addition to having these built-in deployment features, it also supports a .NET based provider API that enables you to create and plug-in your own custom deployment actions – which allow you to customize it however you want.

106 Responses to “Microsoft HTTPAPI/2.0 use Port 80 – Cannot Start WAMP Apache”

  1. Manuel Canepa Says:

    Thank you!! You save my week, i spend ours trying to figure out which process listen on port 80

  2. Behruz Says:

    THANKS A LOT! Works for me.

  3. Marijn Says:

    Did not work for me with HTTPAPI/2.0

    In my case the culprit was the World Wide Web Publishing Service. Disabling it solved the problem.

  4. Fazlulhaq Amin Says:


  5. zahra Says:

    its working! thanks. it’s really good thank you

  6. Dan Olawale Says:

    Thanks SRS.Mohit. Your solution worked for me

Leave a Reply