XAMPP & Local Server 9 min read

How to Fix XAMPP Apache Not Starting on Windows: Step-by-Step Guide

By GardenWarGame Technical Team Systems & Infrastructure Specialist

Published: 2026-03-12 • Updated: 2026-10-12

When XAMPP displays "Error: Apache shutdown unexpectedly", it is almost always caused by port 80 or 443 being occupied by Windows services (such as IIS or World Wide Web Publishing), missing Visual C++ dependencies, or damaged configuration files.

✔ Rapid Direct Solution

Open Command Prompt as Administrator and run "netstat -ano | findstr :80". If Process ID 4 (System/IIS) is using port 80, stop the World Wide Web Publishing Service in Windows Services (services.msc). Alternatively, change the listening port in "C:\xampp\apache\conf\httpd.conf" from 80 to 8080 and restart XAMPP.

📋 Guide Table of Contents

1. Problem Diagnosis & Symptoms
2. Primary Root Causes
3. Step-by-Step Diagnostic Fixes
4. Verification & Testing
5. Quick Diagnostic Troubleshooting Matrix
6. Critical Mistakes to Avoid
7. Frequently Asked Questions (FAQ)

1. Problem Diagnosis & Symptoms

One of the most persistent hurdles encountered by local web developers on Windows is the red error in the XAMPP Control Panel: "Error: Apache shutdown unexpectedly. This may be due to a blocked port, missing dependencies, improper privileges, a crash, or a shutdown by another method." Apache cannot bind to its network sockets, preventing local PHP script execution and virtual host access.

2. Primary Root Causes

Cause: Port 80 conflict with World Wide Web Publishing Service (IIS), Skype, or VMware Workstation.
Cause: Port 443 (SSL) conflict with VMware Host Agent, VirtualBox, or VPN clients.
Cause: Missing Microsoft Visual C++ 2015–2022 Redistributable (x64/x86).
Cause: Corrupt Apache configuration directives in httpd.conf or httpd-vhosts.conf.
Cause: XAMPP installed inside "C:\Program Files" where Windows User Account Control (UAC) restricts file write permissions.

3. Step-by-Step Diagnostic Fixes

Check Which Process is Occupying Port 80 and Port 443

Before modifying configuration files, pinpoint the exact Windows process holding the port using the command line.

BASH

netstat -ano | findstr :80
netstat -ano | findstr :443

Pro Tip: Look at the last column in the output: that number is the PID (Process Identifier). If PID 4 is listed, it is the Windows HTTP kernel driver used by IIS.

Stop World Wide Web Publishing Service (W3SVC) and IIS

Windows often boots IIS services automatically. Press Windows Key + R, type "services.msc", and press Enter. Locate "World Wide Web Publishing Service", right-click it, select "Stop", and change its Startup Type to "Manual" or "Disabled".

CMD

net stop W3SVC
net stop WAS

Warning: Only disable W3SVC if you are not using Microsoft IIS for ASP.NET or other local server workloads.

Reconfigure Apache Ports in httpd.conf and httpd-ssl.conf

If you cannot disable the conflicting application, change Apache to listen on alternative ports such as 8080 and 4433. In XAMPP Control Panel, click "Config" next to Apache and choose "Apache (httpd.conf)". Search for "Listen 80" and "ServerName localhost:80".

APACHECONF

# In C:\xampp\apache\conf\httpd.conf:
Listen 8080
ServerName localhost:8080

# In C:\xampp\apache\conf\extra\httpd-ssl.conf:
Listen 4433
<VirtualHost _default_:4433>
ServerName localhost:4433

4. How to Verify the Resolution

✔ Open the XAMPP Control Panel and click the "Start" button next to Apache.
✔ Check that the "Apache" label turns green and displays active Port(s): 80, 443 (or 8080, 4433).
✔ Open your web browser and navigate to http://localhost (or http://localhost:8080). You should see the XAMPP dashboard.

5. Diagnostic Troubleshooting Matrix

Symptom Observed	Root Cause	Recommended Action
PID 4 holding port 80	Windows IIS or World Wide Web Publishing Service active	Disable W3SVC in services.msc or switch Apache port to 8080 in httpd.conf
Port 443 blocked	VMware Workstation or Skype holding HTTPS socket	Change httpd-ssl.conf Listen directive from 443 to 4433

6. Critical Mistakes to Avoid

❌ Do not delete the entire xampp/apache/conf folder; always create a backup copy before editing.
❌ Do not install XAMPP inside "C:\Program Files" due to Windows UAC restrictions. Use "C:\xampp".

7. Frequently Asked Questions

❓ Why does XAMPP Apache work after restarting Windows and then fail again?

This happens when a conflicting service like Windows IIS or a VPN software starts automatically at boot with a higher service priority. Changing the conflicting service startup type to "Manual" in Windows Services permanently resolves the issue.