none
MDT 2013 Update 1, Windows 10, Error -2147467259 0x80004005 RRS feed

  • Question

  • We have upgrade to MDT 2013 Update 1 and deploy a new Windows 10. Same Problem with Win10 Enterprise LTSB or Win 10 Professional


    Chris

    Wednesday, August 26, 2015 11:27 AM

Answers

  • there was no DISM Folder in deploymentshare - Tools - x64 .

    my co-worker extract it from iso and add a taskseqence now it works fine

    cmd /c copy %deployroot%\tools\x64\dism\*  x:\windows\system32\dism /y

    cmd /c copy %deployroot%\tools\x64\dism.exe  x:\windows\system32 /y


    Chris

    • Marked as answer by -- Chris -- Thursday, August 27, 2015 7:20 AM
    Thursday, August 27, 2015 7:20 AM
  • my colleague has forgotten to copy into WDS boot Folder.

    Chris

    Thursday, August 27, 2015 10:55 AM

All replies

  • DISM has an issue with the path your OS in. Can you post your actual BDD.log?

    Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

    Wednesday, August 26, 2015 3:59 PM
    Moderator
  • <![LOG[Copy File: C:\MININT\unattend.xml to C:\Windows\Panther\Unattend.xml]LOG]!><time="14:27:10.000+000" date="08-26-2015" component="LTIApply" context="" type="1" thread="" file="LTIApply">
    <![LOG[Copied unattend.xml to C:\Windows\Panther for image apply.]LOG]!><time="14:27:11.000+000" date="08-26-2015" component="LTIApply" context="" type="1" thread="" file="LTIApply">
    <![LOG[About to run command: dism.exe /Image:C:\ /Apply-Unattend:C:\Windows\Panther\Unattend.xml /ScratchDir:C:\MININT\Scratch]LOG]!><time="14:27:11.000+000" date="08-26-2015" component="LTIApply" context="" type="1" thread="" file="LTIApply">
    <![LOG[Command has been started (process ID 1044)]LOG]!><time="14:27:11.000+000" date="08-26-2015" component="LTIApply" context="" type="1" thread="" file="LTIApply">
    <![LOG[  Console > Deployment Image Servicing and Management tool]LOG]!><time="14:27:11.000+000" date="08-26-2015" component="LTIApply" context="" type="1" thread="" file="LTIApply">
    <![LOG[  Console > Version: 6.3.9600.16384]LOG]!><time="14:27:11.000+000" date="08-26-2015" component="LTIApply" context="" type="1" thread="" file="LTIApply">
    <![LOG[  Console > Error: 50]LOG]!><time="14:27:11.000+000" date="08-26-2015" component="LTIApply" context="" type="1" thread="" file="LTIApply">
    <![LOG[  Console > To service this Windows image requires the latest version of the DISM. See http://go.microsoft.com/fwlink/?LinkId=293395 to find the latest version of DISM, ]LOG]!><time="14:27:11.000+000" date="08-26-2015" component="LTIApply" context="" type="1" thread="" file="LTIApply">
    <![LOG[  Console > and http://go.microsoft.com/fwlink/?LinkId=293394 to learn how to install the latest version of DISM from the ADK on your computer.]LOG]!><time="14:27:11.000+000" date="08-26-2015" component="LTIApply" context="" type="1" thread="" file="LTIApply">
    <![LOG[  Console > The DISM log file can be found at X:\WINDOWS\Logs\DISM\dism.log]LOG]!><time="14:27:11.000+000" date="08-26-2015" component="LTIApply" context="" type="1" thread="" file="LTIApply">
    <![LOG[Return code from command = 50]LOG]!><time="14:27:11.000+000" date="08-26-2015" component="LTIApply" context="" type="1" thread="" file="LTIApply">
    <![LOG[FAILURE ( 5627 ): 50: Run DISM.exe]LOG]!><time="14:27:11.000+000" date="08-26-2015" component="LTIApply" context="" type="3" thread="" file="LTIApply">
    <![LOG[Event 41002 sent: FAILURE ( 5627 ): 50: Run DISM.exe]LOG]!><time="14:27:11.000+000" date="08-26-2015" component="LTIApply" context="" type="1" thread="" file="LTIApply">
    <![LOG[Command completed, return code = -2147467259]LOG]!><time="14:27:11.000+000" date="08-26-2015" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
    <![LOG[Litetouch deployment failed, Return Code = -2147467259  0x80004005]LOG]!><time="14:27:11.000+000" date="08-26-2015" component="LiteTouch" context="" type="3" thread="" file="LiteTouch">
    <![LOG[Event 41014 sent: Litetouch deployment failed, Return Code = -2147467259  0x80004005]LOG]!><time="14:27:11.000+000" date="08-26-2015" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
    <![LOG[For more information, consult the task sequencer log ...\SMSTS.LOG.]LOG]!><time="14:27:11.000+000" date="08-26-2015" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
    <![LOG[Property RetVal is now = -2147467259]LOG]!><time="14:27:11.000+000" date="08-26-2015" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
    <![LOG[Unable to copy log to the network as no SLShare value was specified.]LOG]!><time="14:27:11.000+000" date="08-26-2015" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
    <![LOG[CleanStartItems Complete]LOG]!><time="14:27:11.000+000" date="08-26-2015" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
    <![LOG[TSCore.dll not found, not unregistering.]LOG]!><time="14:27:11.000+000" date="08-26-2015" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
    <![LOG[About to run command: wscript.exe "X:\Deploy\Scripts\LTICleanup.wsf"]LOG]!><time="14:27:11.000+000" date="08-26-2015" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
    <![LOG[Microsoft Deployment Toolkit version: 6.2.5019.0]LOG]!><time="14:27:11.000+000" date="08-26-2015" component="LTICleanup" context="" type="1" thread="" file="LTICleanup">
    <![LOG[Removing AutoAdminLogon registry entries]LOG]!><time="14:27:11.000+000" date="08-26-2015" component="LTICleanup" context="" type="1" thread="" file="LTICleanup">
    <![LOG[VSSMaxSize not specified using 5% of volume.]LOG]!><time="14:27:11.000+000" date="08-26-2015" component="LTICleanup" context="" type="1" thread="" file="LTICleanup">
    <![LOG[Logs contained 8 errors and 0 warnings.]LOG]!><time="14:27:12.000+000" date="08-26-2015" component="LTICleanup" context="" type="1" thread="" file="LTICleanup">
    <![LOG[No Windows PE image to delete.]LOG]!><time="14:27:12.000+000" date="08-26-2015" component="LTICleanup" context="" type="1" thread="" file="LTICleanup">
    <![LOG[Checking mapped network drive.]LOG]!><time="14:27:12.000+000" date="08-26-2015" component="LTICleanup" context="" type="1" thread="" file="LTICleanup">
    <![LOG[testing drive Z: mapped to \\dsserver\deploymentshare$]LOG]!><time="14:27:12.000+000" date="08-26-2015" component="LTICleanup" context="" type="1" thread="" file="LTICleanup">
    <![LOG[Disconnecting drive Z: mapped to \\dsserver\deploymentshare$]LOG]!><time="14:27:12.000+000" date="08-26-2015" component="LTICleanup" context="" type="1" thread="" file="LTICleanup">
    <![LOG[Cleaning up C:\MININT directory.]LOG]!><time="14:27:12.000+000" date="08-26-2015" component="LTICleanup" context="" type="1" thread="" file="LTICleanup">
    <![LOG[Cleaning up TOOLS, SCRIPTS, and PACKAGES directories.]LOG]!><time="14:27:12.000+000" date="08-26-2015" component="LTICleanup" context="" type="1" thread="" file="LTICleanup">

    Chris

    Thursday, August 27, 2015 5:22 AM
  • there was no DISM Folder in deploymentshare - Tools - x64 .

    my co-worker extract it from iso and add a taskseqence now it works fine

    cmd /c copy %deployroot%\tools\x64\dism\*  x:\windows\system32\dism /y

    cmd /c copy %deployroot%\tools\x64\dism.exe  x:\windows\system32 /y


    Chris

    • Marked as answer by -- Chris -- Thursday, August 27, 2015 7:20 AM
    Thursday, August 27, 2015 7:20 AM
  • Have you updated the Deployment share to create new boot images ?

    I had the same issue and using the newly created boot images has fixed it for me. The version of the boot.wim should be 10.0 instead of 6.3.


    • Edited by T_Schneider Thursday, August 27, 2015 12:52 PM
    Thursday, August 27, 2015 10:14 AM
  • my colleague has forgotten to copy into WDS boot Folder.

    Chris

    Thursday, August 27, 2015 10:55 AM
  • The log above shows that you are running DIsm verion 9600, which is bad.

    Please ensure that you have the newest ADK 10.0.26624 installed.


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

    Monday, August 31, 2015 4:27 AM
    Moderator