none
Failure (5627) 50: Run DISM.exe RRS feed

  • Question

  • Whenever I try to deploy Windows 10 from my MDT 2013 Update 1 server, I get this series of errors during "Installing Operating System." I couldn't find any issues in BDD.log. 

    Specifically I get:  Failure (5627) 50: Run DISM.exe | Litetouch deployment failed. Return Code = -2147467259 0x800040005

    Any idea how to get past this? I checked and it looks like it's partitioning everything correctly. 


    Below is the smsts.log

    Expand a string: WinPEandFullOS	TSManager	9/24/2015 11:55:17 AM	1536 (0x0600)
    Executing command line: cscript.exe "%SCRIPTROOT%\LTIApply.wsf"	TSManager	9/24/2015 11:55:17 AM	1536 (0x0600)
    Process completed with exit code 5627	TSManager	9/24/2015 12:00:04 PM	1536 (0x0600)
    !--------------------------------------------------------------------------------------------!	TSManager	9/24/2015 12:00:04 PM	1536 (0x0600)
    Failed to run the action: Install Operating System. 
    Unknown error (Error: 000015FB; Source: Unknown)	TSManager	9/24/2015 12:00:04 PM	1536 (0x0600)
    Sending status message . . .	TSManager	9/24/2015 12:00:04 PM	1536 (0x0600)
    Executing in non SMS standalone mode. Ignoring send a task execution status message request	TSManager	9/24/2015 12:00:04 PM	1536 (0x0600)
    Set a global environment variable _SMSTSLastActionRetCode=5627	TSManager	9/24/2015 12:00:04 PM	1536 (0x0600)
    Set a global environment variable _SMSTSLastActionSucceeded=false	TSManager	9/24/2015 12:00:04 PM	1536 (0x0600)
    Clear local default environment	TSManager	9/24/2015 12:00:04 PM	1536 (0x0600)
    Let the parent group (Install) decides whether to continue execution	TSManager	9/24/2015 12:00:04 PM	1536 (0x0600)
    The execution of the group (Install) has failed and the execution has been aborted. An action failed.
    Operation aborted (Error: 80004004; Source: Windows)	TSManager	9/24/2015 12:00:04 PM	1536 (0x0600)
    Failed to run the last action: Install Operating System. Execution of task sequence failed.
    Unknown error (Error: 000015FB; Source: Unknown)	TSManager	9/24/2015 12:00:04 PM	1536 (0x0600)
    Sending status message . . .	TSManager	9/24/2015 12:00:04 PM	1536 (0x0600)
    Executing in non SMS standalone mode. Ignoring send a task execution status message request	TSManager	9/24/2015 12:00:04 PM	1536 (0x0600)
    Execution::enExecutionFail != m_eExecutionResult, HRESULT=80004005 (e:\nts_sms_fre\sms\client\tasksequence\tsmanager\tsmanager.cpp,767)	TSManager	9/24/2015 12:00:04 PM	1536 (0x0600)
    Task Sequence Engine failed! Code: enExecutionFail	TSManager	9/24/2015 12:00:04 PM	1536 (0x0600)
    ****************************************************************************	TSManager	9/24/2015 12:00:04 PM	1536 (0x0600)
    Task sequence execution failed with error code 80004005	TSManager	9/24/2015 12:00:04 PM	1536 (0x0600)
    Cleaning Up. Removing Authenticator	TSManager	9/24/2015 12:00:04 PM	1536 (0x0600)
    Cleaning up task sequence folder	TSManager	9/24/2015 12:00:04 PM	1536 (0x0600)
    


    Thursday, September 24, 2015 6:43 PM

Answers

  • Your deployment share is messed up.

    At the top of the Bdd.log I see:

    Microsoft Deployment Toolkit version: 6.2.5019.0
    

    Then later I see:

    Microsoft Deployment Toolkit version: 6.3.8298.1000

    These versions should *ALWAYS* match.

    Additionally, your WinPE version is:

    Property OSCurrentVersion is now = 6.3.9600

    Then later I see:

    About to run command: "\\XXX\e\DeploymentShare\Servicing\X64\DISM.exe"  /Apply-Image 
    /ImageFile:"\\rlsmdt\e\DeploymentShare\Operating Systems\Windows 10 Education x64 ISO Test\Sources\install.wim" /Index:1 /ApplyDir:C:	

    You can only install Windows 10 with the latest 10.0.10240 ADK, not the Windows 8.1 ADK

    * Install the Windows 10 ADK.

    * Be sure that after you install the ADK, you do a *FULL* update of your deployment share. FULL!

    Then, re-install, and verify you don't have "6.2.5019.0" nor "6.3.9600" in the bdd.log file, if you do, then you may need to create a *NEW* MDT deployment share from scratch.


    Keith Garner - Principal Consultant [owner] - http://DeploymentLive.com

    Monday, September 28, 2015 3:22 PM
    Moderator

All replies

  • Modify line 400 of the MDT 2013 U1 refresh ZTIPatches.wsf

    From:

      Set f = oFso.CreateTextFile( XMLFile, TRUE, )

    To:

      Set f = oFso.CreateTextFile( XMLFile, TRUE, TRUE )


    Most important details are logs. If you are unsure how to post logs or where to find them then reference https://keithga.wordpress.com/2014/10/24/video-mdt-2013-log-files-basics-bdd-log-and-smsts-log/

    • Proposed as answer by Ty GlanderModerator Thursday, September 24, 2015 9:38 PM
    • Unproposed as answer by Gustav Akk Friday, September 25, 2015 2:49 PM
    Thursday, September 24, 2015 9:38 PM
    Moderator
  • Ok, I changed the line in ZTIPatches and tried deploying again but it still failed with the same error. Should upload some other log?
    • Edited by Gustav Akk Friday, September 25, 2015 1:32 PM Wording
    Friday, September 25, 2015 1:27 PM
  • Post bdd.log to something like Onedrive and share it.

    Most important details are logs. If you are unsure how to post logs or where to find them then reference https://keithga.wordpress.com/2014/10/24/video-mdt-2013-log-files-basics-bdd-log-and-smsts-log/

    Friday, September 25, 2015 5:53 PM
    Moderator
  • We are going to need the bdd.log file.

    How to find the right MDT log files (bdd.log/smsts.log) to debug problems.

    Please upload to onedrive when ready.


    Keith Garner - Principal Consultant [owner] - http://DeploymentLive.com

    Sunday, September 27, 2015 11:11 PM
    Moderator
  • Attached is a link to the bdd.log

    https://onedrive.live.com/redir?resid=394ECEED47D96762!491&authkey=!APRs-qXV0NbqGeo&ithint=folder%2clog
    • Edited by Gustav Akk Monday, September 28, 2015 2:10 PM
    Monday, September 28, 2015 2:09 PM
  • Attached is a link to the bdd.log

    https://onedrive.live.com/redir?resid=394ECEED47D96762!491&authkey=!APRs-qXV0NbqGeo&ithint=folder%2clog
    Monday, September 28, 2015 2:11 PM
  • Sorry, but these are the wrong logs.

    IF the problem occurs during "Apply Operating System" then we will need the logs from the C:\ Drive, either in c:\minint or %systemroot%\temp. Check the video I posted above to guide you through finding the logs.


    Keith Garner - Principal Consultant [owner] - http://DeploymentLive.com

    Monday, September 28, 2015 2:54 PM
    Moderator
  • Sorry, my mistake. I've gone ahead and fixed that. The bdd.log should be correct now.

    https://onedrive.live.com/redir?resid=394ECEED47D96762!491&authkey=!APRs-qXV0NbqGeo&ithint=folder%2clog

    Monday, September 28, 2015 3:06 PM
  • Your deployment share is messed up.

    At the top of the Bdd.log I see:

    Microsoft Deployment Toolkit version: 6.2.5019.0
    

    Then later I see:

    Microsoft Deployment Toolkit version: 6.3.8298.1000

    These versions should *ALWAYS* match.

    Additionally, your WinPE version is:

    Property OSCurrentVersion is now = 6.3.9600

    Then later I see:

    About to run command: "\\XXX\e\DeploymentShare\Servicing\X64\DISM.exe"  /Apply-Image 
    /ImageFile:"\\rlsmdt\e\DeploymentShare\Operating Systems\Windows 10 Education x64 ISO Test\Sources\install.wim" /Index:1 /ApplyDir:C:	

    You can only install Windows 10 with the latest 10.0.10240 ADK, not the Windows 8.1 ADK

    * Install the Windows 10 ADK.

    * Be sure that after you install the ADK, you do a *FULL* update of your deployment share. FULL!

    Then, re-install, and verify you don't have "6.2.5019.0" nor "6.3.9600" in the bdd.log file, if you do, then you may need to create a *NEW* MDT deployment share from scratch.


    Keith Garner - Principal Consultant [owner] - http://DeploymentLive.com

    Monday, September 28, 2015 3:22 PM
    Moderator
  • Keith,

    How do you ensure you do a FULL update?

    Tuesday, May 3, 2016 12:30 AM
  • QuestionThank you,

    I ended up making a new MDT server from scratch and that seemed to fix everything. No issues since September.

    Just an update in case anyone stumbles upon this.

    Tuesday, May 3, 2016 1:05 AM