At work yesterday I discovered that the localhost Apache web server on my PC wouldn’t start; it was running XAMPP.
Each time I tried to start Apache from the XAMPP control panel I got these error messages in the console:
08:59:34 [Apache] Attempting to start Apache app…
08:59:35 [Apache] Status change detected: running
08:59:35 [Apache] Status change detected: stopped
08:59:35 [Apache] Error: Apache shutdown unexpectedly.
08:59:35 [Apache] This may be due to a blocked port, missing dependencies,
08:59:35 [Apache] improper privileges, a crash, or a shutdown by another method.
08:59:35 [Apache] Press the Logs button to view error logs and check
08:59:35 [Apache] the Windows Event Viewer for more clues
08:59:35 [Apache] If you need more help, copy and post this
08:59:35 [Apache] entire log window on the forums
Fix
Reinstalling XAMPP didn’t fix the issue. But this did, spotted on the ever-wonderful Stackoverflow:
- Press Windows + R to bring up the Windows Run… dialog.
- Type services.msc and click OK.
- Scroll down the list of services to find World Wide Web Publishing Service.
- Right-click it and select Properties.
- Change the Startup type to Manual.
- Click Stop and wait for the service to stop.
- Click OK.
That fixed it. Now Apache is running, as evidenced by the green light on the XAMPP control panel:
thanks..it works!!
Nope, didn’t work. Still get the same problem
same here, I ended up renaming previous xampp install so it could install to c:\xampp and everything works now.
So, when I switch between them (I have an old php 5.2.9 install that I need for some legacy stuff) I’ll just rename the dirs appropriately.
Bit of a pain, but oh well, I needed php7.
hey, thanks.. it works.
XAMPP Apache problem solved.
Thanks It works
Thanks! Who would of thought! Bless you 🙂
Finally! Pew! Thanks man!
I tried but it didn’t work
I’m sorry that didn’t work for you. Are you using the latest version of Xampp? In the past I’ve also found that it didn’t work because it was clashing with port-allocation resources such as Skype—changing the port that Skype uses (i.e. moving away from port 80) resolved things.