If w3wp.exe or inetinfo.exe is the offender, IIS is running. You have three choices:
Option A (Recommended for Veeam only): Change IIS to another port.
Option B: Stop and disable IIS (if not needed).
Option C: Stop IIS temporarily for Veeam to install, then re-bind later.
Once you have the PID, open Task Manager, go to the Details tab, and find the PID to see the process name.
Common Culprits:
Before diving into solutions, it is critical to understand why Veeam insists on Port 443. Veeam Backup & Replication uses Port 443 for several key functions:
If another application is squatting on Port 443, Veeam cannot start its core listening services, leading to installation rollbacks or failed service startups.
netstat -ano | findstr :443
Example output:
TCP 0.0.0.0:443 0.0.0.0:0 LISTENING 1234
The number 1234 is the Process ID (PID).
If Veeam is already installed (but services fail to start due to port conflict): If w3wp
After freeing port 443:
Check Veeam event logs (Event Viewer → Applications and Services Logs → Veeam Backup).
If you are installing or upgrading Veeam Backup & Replication (VBR), encountering the error "Required port 443 for Veeam Backup & Replication is occupied by another application" is a common, albeit frustrating, roadblock.
Port 443 is the standard port for HTTPS traffic. Because it is the default secure port for the web, many applications (IIS, Skype for Business, VMware Update Manager, and various web servers) fight for control over it. Veeam requires this port for its internal web server to communicate with the console, mount servers, and manage the backup infrastructure.
This article explores how to identify the culprit and resolve the conflict without compromising your network security. Option B: Stop and disable IIS (if not needed)
In the complex ecosystem of data center management, Veeam Backup & Replication has established itself as a gold standard for virtualization and cloud data protection. However, even the most robust platforms can encounter frustrating roadblocks. One of the most common and cryptic errors that administrators face during installation or upgrade occurs when Veeam attempts to bind to Port 443.
The full error typically reads:
"Required port 443 for Veeam Backup & Replication is occupied by another application. Please specify another port or stop the application that uses this port and try again."
While the error message seems straightforward—"another app is using the port"—the resolution is rarely a simple matter of killing a process. Port 443 is the default port for HTTPS (HTTP Secure) traffic, and in a Windows Server environment, multiple roles, services, and third-party applications compete for it.
This article provides a definitive, step-by-step guide to diagnosing why Port 443 is occupied on your Veeam server and how to safely resolve the conflict without breaking existing services. Option C: Stop IIS temporarily for Veeam to