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).
831 questions
{count} votes

Accepted answer
  1. AllenLiu-MSFT 40,401 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. HORCHANI Said 1 Reputation point
    2021-09-23T11:00:52.193+00:00

    Hello , I have the same probléme As you !!! But no solutions !!!
    Can somebody Help us please :)

    0 comments No comments

  2. Karl Yang 1 Reputation point
    2021-09-28T15:23:54.53+00:00

    I run into the same problem, after install ADK for Windows 11, it is fixed. These are steps:
    Open https://learn.microsoft.com/en-us/windows-hardware/get-started/adk-install
    Select "Download the ADK for Windows 11"
    Uninstall Old ADK, install the new ADK for Windows 11
    Also "Download the WinPE add-on for the Windows ADK"
    Uninstall old adkwinpesetup, install the new one
    Open "Unattend.xml" from SIM correctly

    0 comments No comments

  3. Matthew Li 1 Reputation point
    2021-10-08T17:59:16.2+00:00

    I installed the new ADK for Win11 and also installed the ADKWinPE add-ons and still having the same issue. Still having issues opening Unattend.xml and unable to image any devices with the Win21H1 WIM.

    The OS that I created the WIM from was originally a 20H2 version and I ran the feature upgrade for 21H1.
    I haven't tried doing a fresh installation/upgrade from the 21H1 download though, but that may be my next steps to test when I have time.

    0 comments No comments

  4. Matthew Li 1 Reputation point
    2021-10-14T18:21:06.163+00:00

    So I created a new WIM, created a new Secure Task on Deployment workbench and went and try to create the catalog file again but still no luck.
    Below is the error that is coming up when I try to generate a new unattend.xml

    PROGRESS: 69: Cleaning up...
    ERROR: Unable to generate catalog on D:\DeploymentShare\Operating Systems\WIN10x64_21H1\WIN10x64_21H1.WIM: System.InvalidOperationException: The operation failed to complete. ---> System.Reflection.TargetInvocationException: Exception has been thrown by the target of an invocation. ---> System.NotImplementedException: The method or operation is not implemented.
    at System.Runtime.InteropServices.Marshal.ThrowExceptionForHRInternal(Int32 errorCode, IntPtr errorInfo)
    at Microsoft.ComponentStudio.ComponentPlatformInterface.CbsSessionAdaptor..ctor(String bootDrive, String imageWinDir, String servicingPath)
    at Microsoft.ComponentStudio.ComponentPlatformInterface.OfflineImageImpl.InitializePackages()
    at Microsoft.ComponentStudio.ComponentPlatformInterface.OfflineImageImpl..ctor(OfflineImageInfo imageInfo)
    --- End of inner exception stack trace ---
    at System.RuntimeMethodHandle.InvokeMethod(Object target, Object[] arguments, Signature sig, Boolean constructor)
    at System.Reflection.RuntimeConstructorInfo.Invoke(BindingFlags invokeAttr, Binder binder, Object[] parameters, CultureInfo culture)
    at System.RuntimeType.CreateInstanceImpl(BindingFlags bindingAttr, Binder binder, Object[] args, CultureInfo culture, Object[] activationAttributes, StackCrawlMark& stackMark)
    at System.Activator.CreateInstance(Type type, BindingFlags bindingAttr, Binder binder, Object[] args, CultureInfo culture, Object[] activationAttributes)
    at System.Reflection.Assembly.CreateInstance(String typeName, Boolean ignoreCase, BindingFlags bindingAttr, Binder binder, Object[] args, CultureInfo culture, Object[] activationAttributes)
    at Microsoft.ComponentStudio.ComponentPlatformInterface.Cpi.PlatformImplementation.CreateOfflineImageInstance(OfflineImageInfo imageInfo)
    --- End of inner exception stack trace ---
    at Microsoft.ComponentStudio.ComponentPlatformInterface.Cpi.PlatformImplementation.CreateOfflineImageInstance(OfflineImageInfo imageInfo)
    at Microsoft.ComponentStudio.ComponentPlatformInterface.OfflineImageCatalog.Serialize(OfflineImageInfo imageInfo)
    at Microsoft.ComponentStudio.ComponentPlatformInterface.OfflineImageInfo.CreateCatalog()
    at Microsoft.BDD.Catalog.Program.DoCatalog()

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

    0 comments No comments