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

Bryant, Jason 21 Reputation points
2021-08-31T16:34:35.523+00:00

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

Microsoft Deployment Toolkit
Microsoft Deployment Toolkit
A collection of Microsoft tools and documentation for automating desktop and server deployment. Previously known as Microsoft Solution Accelerator for Business Desktop Deployment (BDD).
824 questions
{count} votes

Accepted answer
  1. AllenLiu-MSFT 40,001 Reputation points Microsoft Vendor
    2021-09-01T06:39:55.41+00:00

    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.

    0 comments No comments

18 additional answers

Sort by: Most helpful
  1. Bryant, Jason 21 Reputation points
    2021-09-01T13:14:42.917+00:00

    Correct. I replaced it in both locations and then updated the deployment share.
    Where are those 2 logs located? On the machine I am imaging or stored somewhere on MDT server?

    0 comments No comments

  2. AllenLiu-MSFT 40,001 Reputation points Microsoft Vendor
    2021-09-02T06:25:28.19+00:00

    Hi, @Bryant, Jason
    You may configure the SLSHARE in CustomSettings.ini file, then MDT will copy the log files to a server share if something goes wrong during deployment, or when a deployment is successfully completed.
    For the details and example:
    https://learn.microsoft.com/en-us/windows/deployment/deploy-windows-mdt/create-a-windows-10-reference-image#the-customsettingsini-file


  3. Bryant, Jason 21 Reputation points
    2021-09-08T13:22:44.79+00:00

    After recreating the MDT boot key it again it was able to complete

    0 comments No comments

  4. Andy Harris 121 Reputation points
    2021-09-21T09:22:04.477+00:00

    I have the same issue deploying 21H1. I've followed the instructions provided by AllenLiu and in the attached link, but the error still occurs. Any ideas what else may be causing the problem?

    0 comments No comments