Making MDT work with Windows ADK 2004 for BIOS Machines (2024)

Thank you so much! Even with Microsoft's 'hotfix', I was still experiencing the boot-loop issue (symptom #2). After adding the 'FixUEFIDetection.wsf' script to the first and second locations (as you described) in the task sequence, the boot-loop issue was resolved. I've been configuring MDT on a variety of host OSs, ADK versions, MDT versions, and there always seems to be an endless barrage of issues (resolve one error, and on to the next one). Microsoft deserves to be chastised on releasing half-ass 'solutions' such as this, and you deserved to be thanked. Typical Microsoft problems where they can't get their…Read more »

Thank you very much. I have been looking for the source of this problem for over a week. Thanks again!!

Tack för lösningen!

This is still a bug in the latest ADK.

Peace to all of you,
I had the same issue. I have created a base windows 11 image using on task sequence. Created a second task sequence to capture the image after I have installed company apps
The virtual machine gets stuck at loading files.
Turn off the VM (reference machine I wanted to capture) edit settings and had it start using the LiteTouchPE_x64.
Start the VM machine and it automatically continued the process of creating a wim file

Hey Johan, thanks for the very informative article and for updating it with the hotfix information. I, too, was wracking my brains why I kept seeing a "Formatting UEFI" message on BIOS boot machines. Even after re-generating the boot image in the MDT console. Then it dawned on me: A reminder for those who use WDS to boot over the network– Please also import the boot image into WDS. WDS does not pick up the newly-generated boot image from MDT, obviously. 🙂

thanks! needed this fix even with the hotfix. Not for all devices, but some new specialized laptops (kano).

Hello Johan. I've worked IT for 30 years but only recently stood up a WDS/MDT server for the first time and hit this bug. I applied the MS patch but the problem persisted. So I backed that out and applied your fix. My deployment get through the first stage now but then I have an unbootable disk. Any thoughts on where I went wrong?

Guys I am having almost the same problem, I am unable to capture a 20H2 image using Hyper-V with the latest MDT and ADK+WinPE. the process went fine but stuck in a loading file boot loop.

Hi Johan, thank you for the solution, I tried using the script and it didnt work for me. Here is the error I got. Failure Litetouch deployment failed, Retum Code -2147467259 Ox8000400S Failed to run the action: Fix uEFl Detection. Incorrect function. (Error. 00000001: Source: Window•s) The execution of the groik (Preinstall) has failed and the execution has been aborted. An action failed. Operation aborted (Error. 80004004; Source: Windows) Failed to run the last action: Fix UEFI Detection. Execution of task sequence failed. I saw from comments that there is a hotfix for MDT fixes the issue. Can someone provide…Read more »

Last edited 3 years ago by yaeslk

Quality Microsoft QA work with recent MDT releases. First WISM needed a slapdash hotfix, now BDD breaks in 8456. What's next, a hotfix to be able to properly partition and format a disk?

Thank You for the solution!!

Sweet jeebus, thank you for this! Been banging my head against the wall for the better part of a day figuring I had screwed up somewhere.

Working for me now with the June 2020 Hotfix. Thanks for posting this

Genius, thanks ever so much.

Fantastic stuff. I've been pulling my hair out here – I found your post early on but the hotfix was out. Applied that and updated the deployment share. No luck! That's after forcing a MBR (BIOS only) step in the task sequence. I have lots of old BIOS machines so can't manage with UEFI only.
I kept coming back to the same few posts online. In the end, tried with your script in there too, and it's progressed!
Perhaps I've not installed the hotfix correctly? It's straightforward but maybe December has taken its toll on my brain.

Just wanted to say thanks for this.
Had this issue today when imaging some older laptops. Saved me a lot of time

Thanks Johan, this script fixed it for me.

I am deploying Server 2016 DataCenter GUI with Litetouch. However the fix doesn't work. Would you know why?
I have applied the fix to the server 2019 task sequences and they are working.

thank you so much!!

Thanks Johan your fix worked for Win10 v2009 Image capture! Please keep up the good work, a very valuable resource for OSD folks. 🙂

Last edited 3 years ago by Zain K

Hello Johan,
What Drivers do you usually use for your reference image?

So I applied the hotfix, but seems like it made it worse in my case. Before the hotfix I had to mount my capture iso and boot from that when I wanted to capture, was caught in a loading loop otherwise, after the hotfix instead of rebooting before going into PE and capture my VM bluescreens and reboots, getting into the error that something went wrong and I should reinstall the OS. Followed the guidelinkes from the link to see if I missed something, but followed it like it were described.

Thanks for the link to the patch;)

You did not encounter a problem that on Vmware ESXi virtual machines during deployment refuse to see the hard drive … even if you integrate the drivers into WinPE Boot Image through MDT?
I tried different versions of SCSI controllers, HDD does not help anything. There were no such problems on WinPE Windows 8.1.

Last edited 4 years ago by AlektroNik

Hi Johan! I have been trying to do a build and capture of Windows 10 2004 with MDT 8456 and HypoerV, and with the help of this solution I was able to get it done, thanks!. BUT I noticed that when the Install Update step is running som updates are found, i.e Silverlight, and Windows Defender update, but all are set to be SKIP'ped in the log files…. Have you seen this behaviour and maybe have a clue on how to remediate it? I am updating towards Microsoft Update, and not using a WSUS server. Thanks!

Sorry…last post for now. The first attempt failed so I moved the task below "Apply Windows PE (BCD) and above "Restart computer". It errored out saying it was looking for a LTICleanup.wsf script file?

I took a stab at it and testing now. I also attempted to upload a screenshot, but it did not work out so well. I put your WSF code underneath "Capture Image" folder –> below "Execute Sysprep" and above the "Apply Windows PE (BCD)" task. I have a pretty vanilla capture and sysprep task sequence for reference.

Last edited 4 years ago by Sean Smith

Last edited 4 years ago by Sean Smith

Johan, you are simply the best. Thank you!

Is it the same issue when deploying servers (2019 and 2016) with MDT and ADK 2004?

Ran into this yesterday and been hunting for a fix, will give this a try – thanks!

Tack för lösningen Johan!

Last edited 4 years ago by Daniel Wahlfridsson

Great post – thank you – it saves me time