XAMPP - Port 80 in use by Unable to open process with PID 4 12

Question

I have been trying to figure out how to fix this problem for two days  I m new to this kind of thing so I would appreciate it if someone could tell me how to fix it   I ve tried deleting skype but that didn t work  I ve tried turning off the world wide web thing off  IIS off nothing seems to work   12 51 22 PM   Apache    Problem detected  12 51 22 PM   Apache    Port 80 in use by  Unable to open process  with PID 4  12 51 22 PM   Apache    Apache WILL NOT start without the configured ports free  12 51 22 PM   Apache    You need to uninstall disable reconfigure the blocking application 12 51 22 PM   Apache    or reconfigure Apache and the Control Panel to listen on a different port

User · Answer

I had this problem too and stoping services using port 80 didn't helped. I resolved it by following this procedure (found on a french board):

Launch RegEdit
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\HTTP
Change the value of "start" to 4 (disabled)
Reboot your computer

Not sure how this affect other services, but it solved permanently the issue and so far I didn't see any issue.

Using Windows 10.

User · Answer

In httpd conf change the following lines and then restart the application    Listen 80 to Listen 8080   ServerName localhost 80 to ServerName localhost 8080   When you press  Start  the application can still say that you have an error like  Port 80 in use by  Unable to open process  with PID     but it will still work   If the error includes  Port 443 in use by  Unable to open process  with PID     you need to change both httpd conf and httpd-ssl conf    In httpd-ssl conf change    Listen 443 to Listen 4433   lt VirtualHost  default  443 gt  to  lt VirtualHost  default  4433 gt  ServerName www example com 443 to ServerName www example com 4433

User · Answer

In windows 10  to free up port 80   in my case  I open  Services  from  Search Windows   on the left corner on screen   then stop all of SQL server services MSSQLSERVER and it works again

User · Answer

I ve had the same problem  but in my case Apache was already running and for some reason the XAMPP config tool didn t show that  It happened after I started XAMPP for the first time after the installation  After crashing the other Apache instances all was fine and ports 80 and 443 were free again   So before making changes to your systeem  make sure something as obvious as the above isn t happening

User · Answer

Extracted from this article    Go to your run command and enter   netstat -o -n -a   findstr 0 0 80   The last number here is the process ID using it   This is most often IIS or other web relates service and is easy to resolve  but every so often  very often it would seem looking around on google  it appears to be PID 4     which according to the Windows Task Manager is the NT Kernel and System   Not very helpful given killing this will result in a blue screen of death     The thing hogging port 80 has nothing to do with IIS or web anything  it s SQL Server Reporting Services  Turn off anything that resembles a SQL Server Services and start Apache again  no need for a reboot   So problems with PID 4 listening to port 80   Check your SQL services and turn them off   UPDATE - Comment from  sangam      Worked at a shot  In my case  it turned out to be SQL server reporting   services  I stopped the service for all the installed instances  and   it worked  without machine reboot

User · Answer

Click services on the Xampp control panel  filename is services msc  extra info     First  look for IIS  if it is running  Stop it  stop this service option on the left after clicking on the service name    Then  this is the main problem  Look for Web deployment Service  not the exact name though it has Web deployment at the beginning    Stop this service too  Try again and Apache should work    If you are running Skype  exit out of that too  run Apache  then launch Skype

User · Answer

In Ubuntu by default  the system will not allow you to occupy privileged ports   0 to 1023   other than specifying the port as 80  you need to run XAMP with sudo

User · Answer

if the service is http sys  You need to change the binded IP address for http sys     netsh http add iplisten ipaddress      Work fine without restart the os

User · Answer

For those with ASP NET  C  or having SQL Server  users  If you are using SQlServer OR Visual Studio Your port might encounter  easiest thing you might want to do is on Command  servies msc and then find SQl Server Reporting Service and then stop it

User · Answer

Open a CMD prompt as administrator and execute the following command    net stop was  y  Open the Run dialog box  press Win R   then type  services msc  Then search for World Wide Web Publishing Service  WWW-Publishing Service  and Web Deployment Agent Service and stop them  You should also disable them  Start Apache again with XAMPP      Link Ref  https   www sitepoint com unblock-port-80-on-windows-run-apache

User · Answer

I ve had same problem  when I was installed MS WebMatrix  IIS Server was blocked the port 80 which XAMPP was running on  I tried to find   World Wide Web Publishing Service and stop it  but could not find it on list  Best way is changing a port   Please refer with this link ref

User · Answer

After changing the main port 80 to 8080 you have to update the port in the control panel   Then click here   And here   Then save and restart

User · Answer

It usually works afters you stop IIS Server and Skype

User · Answer

XAMPP - Port 80 in use by    Unable to open process    with PID 4  12  run the comment in cmd tasklist  and find which the PID and process name related to this now open window task manager  you can also open window task manager by using CTRL ALT DEL  now click on the process tab and find the name which using PID and right click on that and end process  now again restart the xampp

User · Answer

I have the same issue  I solved the problem  just disabled   BranchCache Service  in services   Somehow windows updates  this service is triggered in startup  and uses 80 ports  When you check via netstat you could see the system is used this but couldnt understand which service is used

User · Answer

What worked for me was stopping the Internet Information Services  IIS   If you are using Windows 7  click on your Start button and in your search box  type  iis   Click on  Internet Information Services  IIS  Manager   When the window pops up  and assuming you ve got none of the icons selected  you should just be able to click Stop on the right action pane  My XAMPP Apache started right up  Hope it all worked out for you

User · Answer

Another very easy option is to simply set Apache to listen on a different port  This can be done by clicking on the  Config  button on the same line as the  Apache  module  select the  httpd conf  file in the dropdown  then change the  Listen 80  line to  Listen 8080   Save the file and close it   Now it avoids Port 80 and uses Port 8080 instead without issue  The only additional thing you need to do is make sure to put localhost 8080 in the browser so the browser knows to look on Port 8080  Otherwise it defaults to Port 80 and won t find your local site   This will also require you to restart Apache for the change to take effect   Voila  Fixed

User · Answer

The Web Deployment Agent Service is deployed with WebMatrix and was the cause of my woes  It may also be distributed with other applications installed using Microsoft   s Web Platform Installer   Uninstall it solved my problems

User · Answer

I write this  because i coudn t find answear for the same question  In my case PID was 2484    you must find a process or service with this PID  open cmd  in Windows  and write    tasklist  Find your PID in this list and read name of process or service  Now you can kill this using Task Manager  find this name on Process list click End Process     That s my case  Possibly you must open services msc and stop Service with your PID   On my computer xampp it worked fine

User · Answer

If you ve SQLServer Reporting Services running locally then you need to stop that also

User · Answer

SQL Server Reporting Service  was causing issues in my system  after stopping it  Apache started working fine

User · Answer

You might need to stop the  Web Deployment Agent Service   Press Win R and type  services msc  Right click on Web Deployment Agent Service and select  Stop   Restart XAMPP  Also after  double clicking  Web Deployment Agent Service  you can  make the Startup type to Manual  So that  Web Deployment Agent Service  will not start automatically

User · Answer

So I have faced the same problem when trying to start Apache service and I would like to share my solutions with you  Here are some notes about services or programs that may use port 80    Skype  Skype uses port 80 443 by default  You can change this from Tools - gt  Options - gt  Advanced - gt  Connections and disable the checkbox  use port 80 and 443 for addtional incoming connections   IIS  IIS uses port 80 be default so you need to shut it down  You can use the following two commands  net stop w3svc  net stop iisadmin  SQL Server Reporting Service  You need to stop this service because it may take port 80 if IIS is not running  Go to local services and stop it  VMware Workstation  If you are running VMware Workstation  you need to stop the VMware Workstation server - port 443 as well    These options work great with me and I can start Apache service without errors   The other option is to change Apache listen port from httpd conf and set another port number   Hope this solution helps anyone who faces the same problem again

User · Answer

For me usually works   - Turn off Skype  - Turn off all SQL Server processes displayed in services msc   - Turn off World Wide Web Publishing in services msc

User · Answer

Open Task Manager  Ctrl Alt Delete   Go to  Details  tab  Sort by PID number  End process that is using PID number indicated in error  Restart XAMPP

User · Answer

I had same issue  After some googling arrived to this page  Since I guess this error may have various reasons  so listen to my experience   Xampp red line log    12 53 54 PM   Apache  Problem detected  12 53 54 PM   Apache    Port 443 in use by  Unable to open process  with PID 3908        Finally it turned out that I had this line of code in my php codes     res   file get contents  http     SERVER HTTP HOST   SERVER REQUEST URI       The purpose of this piece of code was to get a mirror of php result from somewhere in my server  But it s just stucked in a loop that gets its own content   I repaired code    res   file get contents str replace  my uri php     mirror uri php     http     SERVER HTTP HOST   SERVER REQUEST URI        Then I restarted apache     and that apache error never happened again   So sometimes searching for probable halting points in your code is a good approach

User · Answer

As there is comment by  johnkarka on the question  this port is used by SQL Server reporting service as well  After stopping this  Apache started fine    Go to  SQL Server Configuration Manager  Click on  SQL Server Reporting Service  and stop it     The funny thing is IIS was working fine in same configuration but not Apache  had to stop SQL Reporting service to make it work on default port  80

[windows] XAMPP - Port 80 in use by "Unable to open process" with PID 4! 12

Examples related to windows

Examples related to apache

Examples related to xampp