MDT Failure to Deploy Windows 10 21H1 (Failure 5627 0x80004005)

Question

Greetings,

I am trying to capture and deploy Windows 10 21H1 image via MDT.

My Setup:
Microsoft Deployment Workbench 6.3.8456.1000
KB4564442 Patch Update for MDT
Windows ADK for Windows 10, version 2004
Windows PE Add-on for ADK 2004
Microsoft Server 2016 (Running MDT)

We originally had the older version of MDT and ADK installed and it was working fine for Imaging machines with Win 10 v2004.
I uninstalled the MDT and ADK and installed the above versions.
Right Click and Updated the Deployment Share by Completely Regenerating the Boot images.

I built a 21H1 image from scratch on a Dell Laptop and configured settings for our systems.
I was able to successfully capture it.
Imported the wim into MDT as new OS.
I created a completely new Task Sequence to install the OS.
I boot to the MDT boot key, select the task sequence and it starts the install.
It will format the drive
It will install drivers on the machine
It will install the OS and then throw this error:

FAILURE ( 5627 ): -2147467259 0x80004005: Run DISM.exe
Litetouch deployment failed. Return Code = -2147467259 0x800040005
Failed to run the action: Install Operating System.
Unknown Error (Error: 000015FB; Source: Unknown)

I have tried multiple captures/imports of 21H1 from different machines and all capture normal then fail during the deployment.
I will mention that our normal 2004 Images are installing without issue.

Another thing I noticed was when I tried to Edit the Unattend.xml from the task sequence section it gives this error:

ERROR: Unable to generate catalog on I:\DeploymentShare\Operating Systems\Win10 21H1\21h1base.wim: System.ComponentModel.Win32Exception (0x80004005): The process cannot access the file because it is being used by another process
at Microsoft.ComponentStudio.ComponentPlatformInterface.WimImageInfo.PreCreateCatalog()
at Microsoft.ComponentStudio.ComponentPlatformInterface.OfflineImageInfo.CreateCatalog()
at Microsoft.BDD.Catalog.Program.DoCatalog()

Non-zero return code from catalog utility, rc = 2002

I have sent about 2 weeks on this and still not able to resolve it.

Please let me know if you have any suggestions

Answer 1

Hi, @Bryant, Jason
Thank you for posting in Microsoft Q&A forum.

When you say "KB4564442 Patch Update for MDT", did you replace the Microsoft.BDD.Utility.dll file in the MDT installation path and in all existing deployment shares like below article said?
https://support.microsoft.com/en-us/topic/windows-10-deployments-fail-with-microsoft-deployment-toolkit-on-computers-with-bios-type-firmware-70557b0b-6be3-81d2-556f-b313e29e2cb7

Then select the Deployment Share and choose the Update Deployment Share option, choosing to completely regenerate the boot image. Also update the boot image in your WDS or media.

If it doesn't help, you may check smsts.log and bdd.log for more details.

---

If the response 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.

Answer 2

So stupid how ridiculously complex it is to deploy an OS via the developer provided tools of said OS. Manual installation is super easy, with additional engineering and marketing effort to trick you into signing up for a M$ account and handing them as much tracking data as possible. Yet, in a Pro environment, this is the kind of B$ we have to put up with.

How many Windows installs are deployed vs manual? I'd have to guess it's something like 95% vs 5%, if not more.

For the 1000th time, get bent M$. Do you job properly.

Answer 3

Hello all,
I struggled for a few days with my MDT being upgraded to the newest possible version. I also upgraded the MDK to the latest possible version. Unfortunately, installing Windows 10 21H2 using MDT ended with the error you write about.
After a few days, I finally found a solution. Quite simply, this version of 21H2 made available by Microsoft in November 2021 is buggy and nothing can be done about it. I downloaded the one shared in December 2021 and the one for me installed without any errors. System capture to WIM file was also performed correctly.
I hope that my post will help you a little and save your time and nerves. greetings

Answer 4

Make sure you enabled DISM cmdlet in WinPE features

Answer 5

I manged to get a windows 10 21H2 build and capture task sequence and deploy task sequence working successfully. I have not tried Windows Server 2022 yet If I get time I will try and deploy a test for you. (I wont install the Windows Server 2022 ADK is it may mess up my working environment.)

I gave up troubleshooting in the end on my old server it should just would not work, I ended up building a new Windows Server 2019 server installed Windows 11 WAIK, Windows 11 PE tools, latest version of MDT also download and extracted MDT_KB4564442.exe and copied over to
%ProgramFiles%\Microsoft Deployment Toolkit\Templates\Distribution\Tools\x86\
%ProgramFiles%\Microsoft Deployment Toolkit\Templates\Distribution\Tools\x64\
(which I did on my old server and got errors).

Created a brand new deployment share
I then created brand new task sequences 1 for capture and 1 for deploy.
migrated my custom settings.ini files, apps, cmds, regkeys, powershell bits and bobs from the old server task sequence into my new environment,
Updated the deployment share recreated boot files
From the boot iso booted up a dummy hypervisor client
Performed a sucessful sysprep and capture
Imported the CAP Wim into OS
Tested deploy Task sequence with captured wim via USB to client device. Deploys successfully (well it actually fails ) I have loads of errors that my WMI queries in my task sequence are not working but I can go through all my errors one by one (at least the OS and apps are deploying).

My guess is that you need to install the Windows Server 2022 ADK and Server 2022 PE Addons tbh for server 2022 its a pain the exterior having a WAIK that supports one OS when you need to deploy multiple. and also its a pain that (i tried un-installing and installing my old environment with no success but when building a fresh it all worked.

Good luck