none
MDT 8456 Litetouch deployment failed, Return Code = -2147467259 0x80004005 with Dell Latitude 3390 2-in-1 RRS feed

  • Question

  • I have problems with one device in our environment. 

    We use Surface and HP Probook and also Dell Latitude 3390.

    Only the Dell I get problems to image with MDT version 8450.

    Info :

    MDT version 8456

    ADK version 1809

    Windows 10 build 1809

    This information I get form the BDD.Log file

    New ZTIDiskPartition : \\MININT-UHHD9CS\root\cimv2:Win32_LogicalDisk.DeviceID="D:"    \\MININT-UHHD9CS\root\cimv2:Win32_DiskPartition.DeviceID="Disk #0, Partition #1" LTIApply 2/8/2019 4:21:55 PM 0 (0x0000)
    About to run command: "\\WINWDS01\DeploymentShare$\Servicing\X64\DISM.exe"  /Apply-Image /ImageFile:"\\WINWDS01\DeploymentShare$\Operating Systems\Windows 10 Pro Build 1803\Sources\install.wim" /Index:5 /ApplyDir:D: LTIApply 2/8/2019 4:21:56 PM 0 (0x0000)
    Command has been started (process ID 1952) LTIApply 2/8/2019 4:21:56 PM 0 (0x0000)
      Console > Deployment Image Servicing and Management tool LTIApply 2/8/2019 4:21:56 PM 0 (0x0000)
      Console > Version: 10.0.17763.1 LTIApply 2/8/2019 4:21:56 PM 0 (0x0000)
      Console > Applying image LTIApply 2/8/2019 4:22:09 PM 0 (0x0000)
      Console >
    [                           1.0%                           ]  LTIApply 2/8/2019 4:22:10 PM 0 (0x0000)
      Console >
    [=                          2.0%                           ]  LTIApply 2/8/2019 4:22:18 PM 0 (0x0000)
      Console >
    [=                          3.0%                           ]  LTIApply 2/8/2019 4:22:23 PM 0 (0x0000)
      Console >
    [==                         4.0%                           ]  LTIApply 2/8/2019 4:22:27 PM 0 (0x0000)
      Console >
    [==                         5.0%                           ]  LTIApply 2/8/2019 4:22:32 PM 0 (0x0000)
      Console >
    [===                        6.0%                           ]  LTIApply 2/8/2019 4:22:38 PM 0 (0x0000)
      Console >
    [====                       7.0%                           ]  LTIApply 2/8/2019 4:22:43 PM 0 (0x0000)
      Console >
    [====                       8.0%                           ]  LTIApply 2/8/2019 4:22:48 PM 0 (0x0000)
      Console >
    [=====                      9.0%                           ]  LTIApply 2/8/2019 4:22:52 PM 0 (0x0000)
      Console >
    [=====                      10.0%                          ]  LTIApply 2/8/2019 4:22:58 PM 0 (0x0000)
      Console >
    [======                     11.0%                          ]  LTIApply 2/8/2019 4:23:03 PM 0 (0x0000)
      Console >
    [======                     12.0%                          ]  LTIApply 2/8/2019 4:23:07 PM 0 (0x0000)
      Console >
    [=======                    13.0%                          ]  LTIApply 2/8/2019 4:23:11 PM 0 (0x0000)
      Console >
    [========                   14.0%                          ]  LTIApply 2/8/2019 4:23:16 PM 0 (0x0000)
      Console >
    [========                   15.0%                          ]  LTIApply 2/8/2019 4:23:21 PM 0 (0x0000)
      Console > Error: 1392 LTIApply 2/8/2019 4:23:27 PM 0 (0x0000)
      Console > The file or directory is corrupted and unreadable. LTIApply 2/8/2019 4:23:27 PM 0 (0x0000)
      Console > The DISM log file can be found at X:\WINDOWS\Logs\DISM\dism.log LTIApply 2/8/2019 4:23:27 PM 0 (0x0000)
    Return code from command = 1392 LTIApply 2/8/2019 4:23:27 PM 0 (0x0000)
    FAILURE ( 5624 ): 1392: Run DISM:  /Apply-Image /ImageFile:"\\WINWDS01\DeploymentShare$\Operating Systems\Windows 10 Pro Build 1803\Sources\install.wim" /Index:5 /ApplyDir:D: LTIApply 2/8/2019 4:23:27 PM 0 (0x0000)
    Event 41002 sent: FAILURE ( 5624 ): 1392: Run DISM:  /Apply-Image /ImageFile:"\\WINWDS01\DeploymentShare$\Operating Systems\Windows 10 Pro Build 1803\Sources\install.wim" /Index:5 /ApplyDir:D: LTIApply 2/8/2019 4:23:27 PM 0 (0x0000)
    Command completed, return code = -2147467259 LiteTouch 2/8/2019 4:23:27 PM 0 (0x0000)
    Litetouch deployment failed, Return Code = -2147467259  0x80004005 LiteTouch 2/8/2019 4:23:27 PM 0 (0x0000)
    Event 41014 sent: Litetouch deployment failed, Return Code = -2147467259  0x80004005 LiteTouch 2/8/2019 4:23:28 PM 0 (0x0000)
    For more information, consult the task sequencer log ...\SMSTS.LOG. LiteTouch 2/8/2019 4:23:28 PM 0 (0x0000)
    Property RetVal is now = -2147467259 LiteTouch 2/8/2019 4:23:28 PM 0 (0x0000)
    Validating connection to \\WinWDS01\DeploymentLogs$ LiteTouch 2/8/2019 4:23:28 PM 0 (0x0000)
    Mapping server share: \\WinWDS01\DeploymentLogs$ LiteTouch 2/8/2019 4:23:28 PM 0 (0x0000)
    Already connected to server WinWDS01 LiteTouch 2/8/2019 4:23:28 PM 0 (0x0000)
    OSDTargetDriveCache was determined earlier : D: LiteTouch 2/8/2019 4:23:28 PM 0 (0x0000)
    Property OSDTargetDriveCache is now = D: LiteTouch 2/8/2019 4:23:28 PM 0 (0x0000)
    Property OSDisk is now = D: LiteTouch 2/8/2019 4:23:28 PM 0 (0x0000)
    Copying D:\MININT\SMSOSD\OSDLOGS\LiteTouch.log to \\WinWDS01\DeploymentLogs$\MININT-UHHD9CS\LiteTouch.log LiteTouch 2/8/2019 4:23:28 PM 0 (0x0000)
    Copying D:\MININT\SMSOSD\OSDLOGS\LTIApply.log to \\WinWDS01\DeploymentLogs$\MININT-UHHD9CS\LTIApply.log LiteTouch 2/8/2019 4:23:28 PM 0 (0x0000)
    Copying D:\MININT\SMSOSD\OSDLOGS\LTICopyScripts.log to \\WinWDS01\DeploymentLogs$\MININT-UHHD9CS\LTICopyScripts.log LiteTouch 2/8/2019 4:23:28 PM 0 (0x0000)
    Copying D:\MININT\SMSOSD\OSDLOGS\PnpEnum.xml to \\WinWDS01\DeploymentLogs$\MININT-UHHD9CS\PnpEnum.xml LiteTouch 2/8/2019 4:23:28 PM 0 (0x0000)
    Copying D:\MININT\SMSOSD\OSDLOGS\Wizard.log to \\WinWDS01\DeploymentLogs$\MININT-UHHD9CS\Wizard.log LiteTouch 2/8/2019 4:23:28 PM 0 (0x0000)
    Copying D:\MININT\SMSOSD\OSDLOGS\ZTIBDE.log to \\WinWDS01\DeploymentLogs$\MININT-UHHD9CS\ZTIBDE.log LiteTouch 2/8/2019 4:23:28 PM 0 (0x0000)
    Copying D:\MININT\SMSOSD\OSDLOGS\ZTIConfigure.log to \\WinWDS01\DeploymentLogs$\MININT-UHHD9CS\ZTIConfigure.log LiteTouch 2/8/2019 4:23:28 PM 0 (0x0000)
    Copying D:\MININT\SMSOSD\OSDLOGS\ZTIDiskpart.log to \\WinWDS01\DeploymentLogs$\MININT-UHHD9CS\ZTIDiskpart.log LiteTouch 2/8/2019 4:23:28 PM 0 (0x0000)
    Copying D:\MININT\SMSOSD\OSDLOGS\ZTIDrivers.log to \\WinWDS01\DeploymentLogs$\MININT-UHHD9CS\ZTIDrivers.log LiteTouch 2/8/2019 4:23:28 PM 0 (0x0000)
    Copying D:\MININT\SMSOSD\OSDLOGS\ZTIGather.log to \\WinWDS01\DeploymentLogs$\MININT-UHHD9CS\ZTIGather.log LiteTouch 2/8/2019 4:23:28 PM 0 (0x0000)
    Copying D:\MININT\SMSOSD\OSDLOGS\ZTINextPhase.log to \\WinWDS01\DeploymentLogs$\MININT-UHHD9CS\ZTINextPhase.log LiteTouch 2/8/2019 4:23:29 PM 0 (0x0000)
    Copying D:\MININT\SMSOSD\OSDLOGS\ZTIPatches.log to \\WinWDS01\DeploymentLogs$\MININT-UHHD9CS\ZTIPatches.log LiteTouch 2/8/2019 4:23:29 PM 0 (0x0000)
    Copying D:\MININT\SMSOSD\OSDLOGS\ZTIValidate.log to \\WinWDS01\DeploymentLogs$\MININT-UHHD9CS\ZTIValidate.log LiteTouch 2/8/2019 4:23:29 PM 0 (0x0000)
    Copying X:\WINDOWS\TEMP\SMSTSLog\SMSTS.LOG to \\WinWDS01\DeploymentLogs$\MININT-UHHD9CS\SMSTS.LOG LiteTouch 2/8/2019 4:23:29 PM 0 (0x0000)
    Copying X:\WINDOWS\Debug\Netsetup.log to \\WinWDS01\DeploymentLogs$\MININT-UHHD9CS\ LiteTouch 2/8/2019 4:23:29 PM 0 (0x0000)
    Copying X:\WINDOWS\System32\wpeinit.log to \\WinWDS01\DeploymentLogs$\MININT-UHHD9CS\ LiteTouch 2/8/2019 4:23:29 PM 0 (0x0000)
    Copying log D:\MININT\SMSOSD\OSDLOGS\BDD.log contents to \\WinWDS01\DeploymentLogs$\MININT-UHHD9CS\BDD.LOG LiteTouch 2/8/2019 4:23:29 PM 0 (0x0000)

    Friday, February 8, 2019 3:39 PM

All replies

  • Is the issue with multiple systems (same model) or just one single computer?

    It seems like the issue is a bad drive


    Daniel Vega

    • Proposed as answer by Dan_Vega Monday, February 18, 2019 2:33 PM
    Wednesday, February 13, 2019 3:51 PM
  • Thank you for reply Daniel.

    First I also thought that there is a bad or missing driver.

    after many test I figure out that this particular device have some hardware issues.


    • Edited by EvdSteen Thursday, February 14, 2019 7:36 AM
    • Proposed as answer by Dan_Vega Monday, February 18, 2019 2:32 PM
    Thursday, February 14, 2019 7:35 AM
  • Hello 

    my issue with 4856 is totally different and was wondering if you are experiencing same problem as I do.

    none of my applications install after the upgrade and also when capturing image it will reboot into windpe wizard.


    Sunday, February 17, 2019 4:12 AM