WDS not responding with new ADK for windows 10 2004

Question

We recently created a new hyper-v server 2019 with Windows Distribution Services 10.0.17763.1, Microsoft Deployment Toolkit 6.3.8456.1000, ADK for Windows 10 2004 and Windows PE add-on for the ADK 2004.
We've created an image with the latest Windows 10 Enterprise x65 20h2. Deployment works great on the hyper-v machines. However on a new Dell OptiPlex 5070, the WDS-server stops responding.
The wdsmgfw.efi file is loaded, but the boot hangs on connecting to the WDS server.
On the WDS server, the only possible setting for Multicast is "Use Address from the following range:", if we change this to "Obtain IP address from DHCP" (which is what we used to have), the service cannot start. Event viewer shows to events:

Log Name: Application
Source: WDSServer
Date: 3/11/2020 17:27:53
Event ID: 1536
Task Category: WDSServer
Level: Error
Keywords: Classic
User: N/A
Computer: mdt-wsus1.fede.adventist.be
Description:
An error occurred while trying to initialize multicast manager. Windows Deployment Services server will be shutdown.

Error Information: 0x5

Log Name: Application
Source: WDSServer
Date: 3/11/2020 17:27:53
Event ID: 1536
Task Category: WDSServer
Level: Error
Keywords: Classic
User: N/A
Computer: mdt-wsus1.fede.adventist.be
Description:
An error occurred while trying to initialize multicast manager. Windows Deployment Services server will be shutdown.

Error Information: 0x5

We had an old WDS system with ADK for 1903 and there it was not an issue, we could start the WDS with option: "Obtain ip address from DCHP".

It seems that the new ADK does not want to play nice with WDS. We don't know what to do as we have the images ready, but can only deploy them to virtual machines. Yes the dell machine is brand new and the boot options is secure with eufi. Legacy doens't work either, also would like to get it to work with eufi.

We are currently considering roling back to 1903 and imaging form a Windows 10 Enterprise x64 1903 instead of 2004 or 20h2.

But any help would be greatly appreciated

Answer 1

Hi,

There is a known issue about MDT version 8456 that causes MDT to incorrectly detect that UEFI is present on Windows 2004. Try to install the update and check if the issue persists again.

Windows 10 deployments fail with Microsoft Deployment Toolkit on computers with BIOS type firmware

Bests,

============================================

If the Answer is helpful, please click "Accept Answer" and upvote it.
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.