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 ADMIN 1 Reputation point
    2021-10-15T10:45:09.843+00:00

    Same for me ... can sommebody help us please !!!!!


  2. HugoExceptOnFire 1 Reputation point
    2021-11-25T14:47:31.257+00:00

    Hi, I'm getting the same error, can't edit the unattend.xml file for any of the new Windows ISOs in MDT

    Performing the operation "generate" on target "Catalog".
    Starting: "C:\Program Files\Microsoft Deployment Toolkit\Bin\Microsoft.BDD.Catalog40.exe" "C:\DeploymentShare\Operating Systems\Windows 10 Enterprise LTSC 2021 x64\Sources\install.wim" 2 > "C:\Users\adminhl\AppData\Local\Temp\Microsoft.BDD.Catalog.log" 2>&1
    No existing catalog file found.
    PROGRESS: 0: Starting.
    PROGRESS: 0: Creating mount folder: C:\Users\adminhl\AppData\Local\Temp\IMGMGR_install_Windows 10 Enterprise N LTSC 2021_frb2jptd.acl.
    PROGRESS: 5: Creating temp folder: C:\Users\adminhl\AppData\Local\Temp\IMGMGR_install_temp_wj30p4ts.5ru.
    PROGRESS: 10: Mounting Windows image: C:\DeploymentShare\Operating Systems\Windows 10 Enterprise LTSC 2021 x64\Sources\install.wim. This might take a few minutes.
    PROGRESS: 30: Mounted Windows image.
    PROGRESS: 33: Serializing Data.
    PROGRESS: 63: Cleaning up...
    PROGRESS: 63: Unmounting Windows image: C:\DeploymentShare\Operating Systems\Windows 10 Enterprise LTSC 2021 x64\Sources\install.wim.
    PROGRESS: 66: Deleting mount folder.
    PROGRESS: 69: Cleaning up...
    ERROR: Unable to generate catalog on C:\DeploymentShare\Operating Systems\Windows 10 Enterprise LTSC 2021 x64\Sources\install.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
    

    The script it was running:

    Import-Module "C:\Program Files\Microsoft Deployment Toolkit\bin\MicrosoftDeploymentToolkit.psd1"
    get-MDTOperatingSystemCatalog -ImageFile "C:\DeploymentShare\Operating Systems\Windows 10 Enterprise LTSC 2021 x64\Sources\install.wim" -Index "2" -Verbose
    

    The MicrosoftDeploymentToolkit.psd1 file references a required assembly "Microsoft.BDD.PSSnapIn.dll", which is version 6.3.8456.1000
    I have Microsoft Deploment Workbench version 6.3.8456.1000 installed, I have the patch listed above installed. I am running Windows Server 2016.

    I have the latest version of the Windows ADK installed, System Image Manager is version 10.0.22000.1

    0 comments No comments

  3. Matthew Lane 11 Reputation points
    2021-12-09T13:24:12.227+00:00

    Exactly the same issue here except I have tested Windows 10 21H2.

    I cannot deploy the OS from within the task sequence with Failed to run the action: Install Operating System.
    Unknown Error (Error: 000015FB; Source: Unknown)

    When creating a new task sequence using the latest Windows 10 21H2 Enterprise
    Right click the newly created task sequence > Os info > edit unattend.txt (which runs)

    Import-Module "C:\Program Files\Microsoft Deployment Toolkit\bin\MicrosoftDeploymentToolkit.psd1"
    get-MDTOperatingSystemCatalog -ImageFile "D:\MDTDeployment\Operating Systems\Windows 10 Enterprise x64\Sources\install.wim" -Index "3" -Verbose

    Get the following (not copied everything but)
    Performing the operation "generate" on target "Catalog".
    Starting: "C:\Program Files\Microsoft Deployment Toolkit\Bin\Microsoft.BDD.Catalog40.exe" "D:\MDTDeployment\Operating Systems\Windows 10 Enterprise x64\Sources\install.wim"

    PROGRESS: 69: Cleaning up...
    ERROR: Unable to generate catalog on D:\MDTDeployment\Operating Systems\Windows 10 Enterprise x64\Sources\install.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) blah blah

    So cannot be any Bios related issues as someeone previously mentioned as this is occuring before even trying to deploy the operating system my guess is as soon as MDT recognises the unattend.xml we will then be able to deploy the image.
    I have tested with older versions of Operations System such as Windows 10 Enterprise LTSC 2019 an can edit clicking the edit unattend.xml that fine so its just new OS's that are having the issue.

    I have MDT installed on a Windows Server 2016 VM with all the latest patches and the latest available SDK for Windows 10 (not tried the Windows 11 ADK) has anyone tried this yet win11 ADK as a workaround ?

    0 comments No comments

  4. Neil Chuang 1 Reputation point
    2021-12-10T07:43:53.407+00:00

    hi guys

    Use Windows 2012 to build MDT, it will work well

    0 comments No comments