14 Comments

Windows Deployment Services service will not start (Error 0x2740 )

Starting Windows Deployment Services on a recently assigned Distribution Point for System Center Configuration Manager, I received the following error in the Application Event log on the DP:

An error occurred while trying to create the UDP endpoint for WDSPXE provider on interface x.x.x.x:67. This can happen if the network interface was disabled or changed, or some other application is already using the port. The provider will not be able to receive requests on this interface.

Error Information: 0x2740

This was because the DP was setup as a DHCP server and for WDS. Unfortunately WDSUTIL /set-server /UseDHCPPorts:No did not work. The fix was to perform the following registry change:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\WDSServer\Providers\WDSPXE
Set the registry value to: UseDHCPPorts = 0

The service then started without any issues.

Note: Another thing to remember, is that if you are running your WDS server on your DHCP server, you will need to set the 060 option in your DHCP Server Options. From a command prompt run the following command:WDSUTIL /set-server /DHCPOption60:yes

About AJ McKean

Based in sunny Tauranga, New Zealand, AJ McKean is a Senior Systems Engineer in Mt Maunganui. With over 15 years of professional IT experience working in both New Zealand and the United States, he holds several certifications including MCSE(2000-2003), MCITP:Enterprise(2008), MCSA(2012), VMware VCP-DCV5.5, CompTIA A+ & is an HP Storage Architect. He is passionate about all things IT, especially virtualization, automation & cloud technologies.

View all posts by AJ McKean »

« Previous post

siddartha says : December 25, 2014 at 5:16 am
Thanks It working for me..

Reply
- AJ McKean says : January 7, 2015 at 3:35 pm
  Awesome! Glad to hear it worked for you. Thanks for checking out the blog. 🙂
  
  Reply
- Francisco Nabas says : December 8, 2020 at 2:45 am
  Yes! worked like a charm for me! as i’m not running DHCP on the same server, the command WDSUTIL /set-server /UseDHCPPorts:No did the trick. Thanks!
  
  Reply
Peter says : August 26, 2015 at 11:30 am
Great!!! Thanks bro!

Reply
Dinanath Aphale says : August 18, 2016 at 5:58 pm
Thanks a lot……….. It working……….!!!

Reply
- AJ McKean says : August 19, 2016 at 1:24 pm
  Excellent, glad to hear it’s working! Thanks for popping by.
  
  Reply
Glaubert Suyan Dacio says : November 1, 2016 at 1:23 pm
Thanks bro! Works !!!

Reply
- AJ McKean says : February 20, 2017 at 9:39 am
  Awesome, glad to hear it!
  
  Reply
VJ says : March 1, 2017 at 10:08 am
It was opposite in my case but it gave me some kind of guidance. It was great to see this nice piece of KB from person next door. ( I have been working/living in Gisborne)

Reply
- AJ McKean says : March 13, 2017 at 1:17 pm
  Awesome, glad it pointed you in the right direction. Thanks for popping by. Nice to see a local! 🙂
  
  Reply
Igor Rudneff says : June 28, 2018 at 9:18 pm
Tnx man, you’ve saved my ass!

Reply
s. Miller says : January 24, 2019 at 3:24 am
I get the same error and the WDS server is not a DHCP server any idea’s

Reply
- s. Miller says : January 24, 2019 at 3:54 am
  One more thing it fails on WDSTFTP
  
  Reply
Kevin M Saucier says : February 11, 2020 at 7:22 am
I know this is old but, for the benefit of others, thanks for the pointer. My issue seemed to happen after I changed the IP address on the server’s NIC and moved DHCP to another server. I unchecked the boxes on the DHCP tab or WDS and restarted the service and it wouldn’t come back up. I restarted the server and had the same problem. Neither the command above nor the registry update worked for me so I just deleted the UseDHCPPorts entry and the service started right up. Appreciate the step in the right direction!

Reply