none
Windows 10 and MDT 2013 Update 1 build 6.3.8298.1000 RRS feed

  • Question

  • Hi am trying to deploy windows 10 x64 enterprise using  MDT 2013 Update 1 build 6.3.8298.1000 and getting below mention error message. kindly help me.

    FAILURE ( 5624 ): 1392: Run DISM:  /Apply-Image /ImageFile:"\\CM01\DeploymentShare$\Operating Systems\Windows 10 Enterprise Evaluation x64\Sources\install.wim" /Index:1 /ApplyDir:G:

    its my lti apply log

    Microsoft Deployment Toolkit version: 6.3.8298.1000 LTIApply 9/21/2015 11:24:28 AM 0 (0x0000)
    The task sequencer log is located at X:\WINDOWS\TEMP\SMSTSLog\SMSTS.LOG.  For task sequence failures, please consult this log. LTIApply 9/21/2015 11:24:28 AM 0 (0x0000)
    Will boot into Windows PE architecture x64 to match OS being deployed. LTIApply 9/21/2015 11:24:28 AM 0 (0x0000)
    OSDTargetDriveCache was determined earlier : G: LTIApply 9/21/2015 11:24:28 AM 0 (0x0000)
    Property OSDTargetDriveCache is now = G: LTIApply 9/21/2015 11:24:28 AM 0 (0x0000)
    Property OSDisk is now = G: LTIApply 9/21/2015 11:24:28 AM 0 (0x0000)
    Open Control File: OperatingSystems LTIApply 9/21/2015 11:24:28 AM 0 (0x0000)
    ------  Applying Windows image using DISM.exe ------ LTIApply 9/21/2015 11:24:28 AM 0 (0x0000)
    LTI applying image \\CM01\DeploymentShare$\Operating Systems\Windows 10 Enterprise Evaluation x64\Sources\install.wim using DISM LTIApply 9/21/2015 11:24:28 AM 0 (0x0000)
    Property SourcePath is now = \\CM01\DeploymentShare$\Operating Systems\Windows 10 Enterprise Evaluation x64 LTIApply 9/21/2015 11:24:28 AM 0 (0x0000)
    Cleaning off old operating system LTIApply 9/21/2015 11:24:28 AM 0 (0x0000)
    Skipping G:\Drivers LTIApply 9/21/2015 11:24:28 AM 0 (0x0000)
    Skipping G:\MININT LTIApply 9/21/2015 11:24:28 AM 0 (0x0000)
    Skipping G:\_SMSTaskSequence LTIApply 9/21/2015 11:24:28 AM 0 (0x0000)
    New ZTIDiskPartition : \\MININT-GRULTI5\root\cimv2:Win32_LogicalDisk.DeviceID="G:"    \\MININT-GRULTI5\root\cimv2:Win32_DiskPartition.DeviceID="Disk #0, Partition #1" LTIApply 9/21/2015 11:24:28 AM 0 (0x0000)
    About to run command: "\\CM01\DeploymentShare$\Servicing\X86\DISM.exe"  /Apply-Image /ImageFile:"\\CM01\DeploymentShare$\Operating Systems\Windows 10 Enterprise Evaluation x64\Sources\install.wim" /Index:1 /ApplyDir:G: LTIApply 9/21/2015 11:24:28 AM 0 (0x0000)
    Command has been started (process ID 1368) LTIApply 9/21/2015 11:24:28 AM 0 (0x0000)
    ZTI Heartbeat: command has been running for 0 minutes (process ID 1368) LTIApply 9/21/2015 11:24:29 AM 0 (0x0000)
      Console > Deployment Image Servicing and Management tool LTIApply 9/21/2015 11:24:29 AM 0 (0x0000)
      Console > Version: 10.0.10240.16384 LTIApply 9/21/2015 11:24:29 AM 0 (0x0000)
      Console > Applying image LTIApply 9/21/2015 11:24:35 AM 0 (0x0000)
      Console > Error: 1392 LTIApply 9/21/2015 11:25:29 AM 0 (0x0000)
      Console > The file or directory is corrupted and unreadable. LTIApply 9/21/2015 11:25:29 AM 0 (0x0000)
      Console > The DISM log file can be found at X:\WINDOWS\Logs\DISM\dism.log LTIApply 9/21/2015 11:25:29 AM 0 (0x0000)
    Return code from command = 1392 LTIApply 9/21/2015 11:25:29 AM 0 (0x0000)
    FAILURE ( 5624 ): 1392: Run DISM:  /Apply-Image /ImageFile:"\\CM01\DeploymentShare$\Operating Systems\Windows 10 Enterprise Evaluation x64\Sources\install.wim" /Index:1 /ApplyDir:G: LTIApply 9/21/2015 11:25:29 AM 0 (0x0000)


    • Edited by Kumar Lalit Monday, September 21, 2015 6:08 AM
    Monday, September 21, 2015 6:02 AM

All replies

  • I ran into this exact issue yesterday, and I was able to troubleshoot it.  The problem was that the wim file was corrupted.  I would recommend downloading the ISO again then extracting it and replacing install.wim.  It may be best to just import the operating system into the Deployment Workbench again from the redownloaded ISO.
    • Proposed as answer by RErekson Tuesday, September 22, 2015 12:34 PM
    Tuesday, September 22, 2015 12:12 PM