Upgraded to Windows 10 and now WAMP won't work

aurath picture aurath · Jul 30, 2015 · Viewed 89k times · Source

I had WAMP working happily on windows 7 as my local development server. Upgraded to Windows 10 today and had an orange WAMP icon on my taskbar. Turns out Windows had installed and ran IIS automatically (why?).

I disabled IIS, restarted, started WAMP and the icon turned green. However, going to localhost results in a connection refused message. I used the 'Test Port 80' option on the WAMP menu and it says that yes, Server: Apache/2.2.21 (Win32) PHP/5.3.10 is listening on port 80.

The Apache error log doesn't display anything helpful.

[Wed Jul 29 17:48:40 2015] [notice] Apache/2.2.21 (Win32) PHP/5.3.10 configured -- resuming normal operations
[Wed Jul 29 17:48:40 2015] [notice] Server built: Sep 10 2011 11:34:11
[Wed Jul 29 17:48:40 2015] [notice] Parent: Created child process 4200
[Wed Jul 29 17:48:41 2015] [notice] Child 4200: Child process is running
[Wed Jul 29 17:48:41 2015] [notice] Child 4200: Acquired the start mutex.
[Wed Jul 29 17:48:41 2015] [notice] Child 4200: Starting 64 worker threads.
[Wed Jul 29 17:48:41 2015] [notice] Child 4200: Starting thread to listen on port 80.
[Wed Jul 29 17:48:41 2015] [notice] Child 4200: Starting thread to listen on port 80.

The Apache access log just displays several instances of

127.0.0.1 - - [29/Jul/2015:17:52:47 -0700] "GET / HTTP/1.1" 302 202

Any hints, clues, questions to ask on how to proceed? Any way to get more details on why the connection would be refused, and what changed in Windows 10 that would cause it?

Answer

Jack picture Jack · Jul 30, 2015
  1. Search for "Turn Windows features on or off" on the taskbar.
  2. Under "Internet Information Services" deselect "World Wide Web Services" that Microsoft must turn on by default (takes port).
  3. Reboot and WAMP came back up as before.

With some windows updates it might occur the need to repeat this operation