hindersaliva
asked on
WAMP won't start on Windows 10
Just installed WAMP on Windows 10. (There was no WAMP on my PC previously)
When I click the launch icon on my desktop, the command window opens for a few seconds and closes. The WAMP icon does not appear in the tray at the bottom right. (Although it did once, the first time, and it was Red).
I read somewhere (Google) that it could be a conflict with SkyPe also using Port 80. But my SkyPe is the latest version and Googling tells me that now you can't change (or see) the Port number on SkyPe!
What can I check please?
Thanks
When I click the launch icon on my desktop, the command window opens for a few seconds and closes. The WAMP icon does not appear in the tray at the bottom right. (Although it did once, the first time, and it was Red).
I read somewhere (Google) that it could be a conflict with SkyPe also using Port 80. But my SkyPe is the latest version and Googling tells me that now you can't change (or see) the Port number on SkyPe!
What can I check please?
Thanks
ASKER
Uninstalled SkyPe and also stopped IIS.
2 out of 3 services started, so the WAMP icon is yellow.
There was no Apache log file. (Now created but empty). Confirmed that this is what's not starting.
Uninstalled and reinstalled WAMP. No change.
2 out of 3 services started, so the WAMP icon is yellow.
There was no Apache log file. (Now created but empty). Confirmed that this is what's not starting.
Uninstalled and reinstalled WAMP. No change.
Start > Run > services.msc (enter)
wampapache64
wampmysqld64
wampmariadb64
Check if these 3 are there, and if not, that's already the problem.
If they are all 3 there, then one of them is not in the Running state. Then that's the problem that needs to be solved.
wampapache64
wampmysqld64
wampmariadb64
Check if these 3 are there, and if not, that's already the problem.
If they are all 3 there, then one of them is not in the Running state. Then that's the problem that needs to be solved.
ASKER
run CMD in ADMINISTRATOR mode
netstat -abn | more
you should watch the LEFT side where it says :80
The program responsible is under this line
Example:
TCP 0.0.0.0:21 0.0.0.0:0 LISTENING
[FileZilla Server.exe]
Filezilla server is listening on port 21
netstat -abn | more
you should watch the LEFT side where it says :80
The program responsible is under this line
Example:
TCP 0.0.0.0:21 0.0.0.0:0 LISTENING
[FileZilla Server.exe]
Filezilla server is listening on port 21
Sadly, right now, you have to scour through all your services, and stop them one by one, until you find out which service/program is using it.
You can also try to connect to your localhost with the browser, hopefully that also gives you hints where to look for.
Otherwise, use cmd again:
telnet localhost 80
get (enter enter)
And read it all the error text, checking for hints.
You can also try to connect to your localhost with the browser, hopefully that also gives you hints where to look for.
Otherwise, use cmd again:
telnet localhost 80
get (enter enter)
And read it all the error text, checking for hints.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Admin: please award all points to Kimputer. Thanks.
Depending on which person you talk to, it could be quite unsatisfactory.
For me, it would be unsatisfactory, as I always like to know EXACTLY what's going on with my system. Right now, you evaded the problem by having WAMP work AROUND it.
For internal use, you now use http://localhost:8081 instead of the much nicer http://localhost
I'm glad you have it up and running, but if I had this problem personally, I would dig deeper to try to find out what is listening on port 80 (I don't like any software running without my knowledge, or wasting system resources)
Btw, you should be able to award points yourself (but as I don't ask questions a lot myself, I'm not sure about the exact steps, besides the fact that I know EE changed the procedure a bit)
For me, it would be unsatisfactory, as I always like to know EXACTLY what's going on with my system. Right now, you evaded the problem by having WAMP work AROUND it.
For internal use, you now use http://localhost:8081 instead of the much nicer http://localhost
I'm glad you have it up and running, but if I had this problem personally, I would dig deeper to try to find out what is listening on port 80 (I don't like any software running without my knowledge, or wasting system resources)
Btw, you should be able to award points yourself (but as I don't ask questions a lot myself, I'm not sure about the exact steps, besides the fact that I know EE changed the procedure a bit)
ASKER
Thanks Kimputer
Also WAMP has detailed log files (In this case, Apache). Please find the log folder and read what's happening.