SCCM Distribution Point Windows Deployment Services Error 0xC1030104

In one of the remote sites, the SCCM operating system deployment was failing. The distribution point server was up and healthy. PXE and Multicast were enabled on the distribution point. However the PXE boot didn’t work in this case. Checking the SCCM distribution point windows deployment services error 0xC1030104 was observed. Looking at the error, it was almost sure that WDS was not functioning correctly.

SCCM Distribution Point Windows Deployment Services Error 0xC1030104

On the distribution point server, the WDS service had issues in starting. Most of all launching the Windows Deployment Services console showed a warning. Windows Deployment services is not configured. Unlike Configuration Manager 2007, there is no need to install WDS before you enable PXE in Configuration Manager 2012 & above. However WDS must be installed on the same server as the distribution point that you use to deploy the operating system. In addition when you enable PXE, the WDS service is installed by SCCM. So there is no much configuration required to be done. However in this case the WDS service wasn’t configured correctly.

SCCM Distribution Point Windows Deployment Services Error 0xC1030104Checking the event viewer on the server revealed two unique events. Event 257, An error occurred while trying to start the Windows Deployment Services server. Error Information: 0xC1030104.

PatchMyPC HorizontalAD
Patch My PC Sponsored AD

SCCM Distribution Point Windows Deployment Services Error 0xC1030104Another WDS related event, Event 513. An error occurred while trying to initialize provider WDSDCMGR from C:\Windows\system32\wdsdcmgr.dll. Windows Deployment Services server will be shutdown. Error Information: 0xC1030104.

SCCM Distribution Point Windows Deployment Services Error 0xC1030104Resolution – To fix the above issue, you can try the below mentioned steps.

  1. On the Distribution point properties, disable/uncheck PXE and Multicast feature.
  2. On the distribution point server, wait until WDS is uninstalled. If it’s uninstalled, proceed with rebooting the server. Else uninstall the WDS manually. In my case I had to uninstall WDS manually and reboot the server.
  3. Once the WDS is uninstalled, on the distribution point server rename RemoteInstall folder. You could rename it to RemoteInstall_old or even delete it.
  4. Enable PXE on the DP server. This will install WDS automatically. If the WDS is installed successfully, reboot the server. Notice that RemoteInstall folder and subfolders are also created.
  5. Distribute boot images again and restart WDS. That should get the OSD working again.


  1. Where do I see the progress of WDS install once I enable PXE on the DP again?
    NVMD: I found it here: ‪D:\SMS_DP$\sms\logs\smsdpprov.log
    Look for this line “Installed PXE“, you may still have to manually install the role, reboot and distribute content.

  2. Thank you, thank you, thank you.
    After a complete restore of my SCCM VM, i had exactly the same problem. This was exactly what i needed after a long time of searching and searching and searching.
    You made my day

  3. Prajwal, always very helpful with SCCM issues. This solved it for me as well.

  4. I am having issue i’ve tried all these steps so frustrated what logs can i post

  5. Nice one, this resolved the issue for me

      1. I tried this and still doesn’t work for me

  6. According to the above steps, still the same error alarm after restart

Comments are closed.