locked
Errors when deploying custom Windows 10 wim from MDT RRS feed

  • Question

  • I'm trying to set up a deployment server for a custom wim of Windows 10 Ent x64 v1809. The Lite touch installation keeps failing. I'm using MDT v6.03 (Build 9600) and my Windows Server 2012 R2. I've tried multiple different solves so far including: 

    -stripping my task sequence down to the bare essentials

    -removing spaces from the name of my deployment share 

    -changing out my custom image for a stock windows iso

    -disabling the bios formatting step in the task sequence and using only UEFI

    Any help would be appreciated. 

    Failure ( 5616 ): 1:Verify BCDBootEx

    Litetouch deployment failed, Return Code = -2147467259 0x80004005

    Failed to run the action: Install Operating System.

    Unknown error (Error: 000015F0; Source: Unknown)

    The execution of the group (Install) has failed and the execution has been aborted. An action failed.

    Operation aborted (Error: 80004004; Source: Windows)

    Failed to run the last action: Install Operating System. Execution of task sequence failed.

    Unknown error (Error: 000015F0; Source; Unknown)

    Task Sequence Engine failed! Code enExecutionFail

    Task sequence execution failed with error code 80004005

    SetNamedSecurityInfo() failed.

    SetObjectOwner() failed. 0x80070005.

    RegQueryValueExW is unsuccessful for Software\Microsoft\SMS\Task Sequence,

    SMSTSEndProgram

    GetTsRegValue() is unsuccessful. 0x80070002.

    Error Task Sequence Manager failed to execute task sequence. Code 0x80004005



    Tuesday, February 12, 2019 7:12 PM

All replies

  • First double check your version of MDT, it should be 6.3.8456.1000

    Second I'd recommend test deploying to a Virtual Machine to eliminate that drivers are your issue.

    Here's a good step by step on building a reference image: Building a Windows 10 v1809 reference image using Microsoft Deployment Toolkit (MDT)

    Here are some ways to deal with drivers: MDT 2013 Lite Touch Driver Management


    Daniel Vega

    Tuesday, February 12, 2019 7:34 PM
  • Ok, my MDT is version 6.3.8450.1000. 

    The link you provided says that it's a guide for Windows Server 2019 or 2016. Will there be any difference working with Server 2012 R2?

    Wednesday, February 13, 2019 3:17 PM
  • It's not a guide for Server 2019, it merely says "In this example I have a file server named MDT01, running Windows Server 2019". He's also being a little cheeky because that's a very new Server OS.

    MDT
    Supported Operating System

    Windows 10 , Windows 7, Windows 8, Windows 8.1, Windows Server 2008 R2, Windows Server 2012, Windows Server 2012 R2, Windows Server 2016, Windows Server 2019



    Daniel Vega

    Wednesday, February 13, 2019 3:38 PM