Note: The issue described in this blog post has been fixed in SCCM Technical Preview 1901. 


Have you ever installed Windows Deployment Services (WDS) and Dynamic Host Protocol (DHCP) on the same server? Usually installing WDS and DHCP on the same server doesn’t cause a problem, but in some cases, you will have issues with starting the WDS server.

This error is related to the DHCP ports and WDS ports conflicting.

In this blog post, I will briefly explain how WDS and DHCP works and how to solve the issue.

What is Windows Deployment Services (WDS)?

Windows Deployments Services is used to deliver a boot image to the workstation for operating system deployment from the network using PXE.

WDS is commonly used with deployments through SCCM and MDT.

What is Dynamic Host Protocol (DHCP)?

DHCP is a server role used to deliver IP addresses to clients dynamically.

The error with conflicting WDS and DHCP ports

Looking at the Event Log, you will see this nasty error:

“The Windows Deployment Services Server service terminated with service-specific error Only one usage of each socket address (protocol/network address/port) is normally permitted.”

WDS DHCP Port error

The reason why this happens is that both WDS and DHCP use the UDP port 67.

How to fix the error

The solution to this problem is manually changing a registry value to force the WDS service not to use the DHCP ports.

Here’s how you do it:

WDS and DHCP on the same server

Open Regedit and go to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\WDSServer\Providers\WDSPXE

WDS and DHCP on the same server

Open the reg value UseDhcpPorts and change it from 1 to 0

Now start the WDS Service, and it should work 🙂


There are many scenarios where you might want to have the WDS and DHCP server roles on the same server. If you use the above solution, you can 🙂

Did this article help you? Please leave a comment below!


Related posts

Subscribe to newsletter:

If you want to receive the latest news for MEMCM, Windows 10, and Powershell, please subscribe to my monthly newsletter!


  1. The correct method for fixing this is listed in technet, you tell WDS not to listen on port 67.

    Altering as above, can in multi network machines break DCHP, DNS, Active Directory and NFS Shares

  2. Thank you very much for this… just one comment if anyone struggles to find the key – the path is actually HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\WDSServer\Providers\WDSPXE


Please enter your comment!
Please enter your name here