none
Applying or Capturing Image No Progress Bar Movement RRS feed

  • Question

  • Hello--we are running MDT version 8443 and MS ADK version 10.1.15063.0.  During the applying image or capturing image step the progress bar remains stuck at 0% for about 15 minutes then bounces all the way to the end.

    I have completely updated the deployment share and am using the new boot ISO images as the PE boot media.

    I understand this issue is tied to the replacement of ImageX.exe with DISM.exe for these two steps, but I thought this was fixed in the latest ADK and version of MDT.  

    Any suggestions?

    Thanks!

    Sunday, May 14, 2017 10:19 PM

All replies

  • It was. Did you update your deployment share and force it to build a new boot image?

    If this post is helpful please vote it as Helpful or click Mark for answer.

    Monday, May 15, 2017 5:34 PM
  • Hello Dan.

    Interestingly I did a complete full update of the Deployment Share along with a full rebuild of the PE boot ISOs.

    I booted from one of the new ISOs and am still getting no progress indication during the apply step.

    Oddly the Windows ADK on the MDT server shows as version 10.1.15063, but when launching the command prompt (F8) when booted into the MDT wizard the boot version shows 10.0.15063.

    Thursday, May 18, 2017 2:40 PM
  • When you deploy a machine did you check the logs to see what version of DISM it is using? You should see something like:

    Console > Version: 10.0.15063.0	LTIApply

    I'll be honest after I saw that it started working again on the progress bar, I haven't paid close attention to recent deployments since the last ADK update.


    If this post is helpful please vote it as Helpful or click Mark for answer.

    Thursday, May 18, 2017 3:44 PM
  • Actually, the properties of the dism.exe in the boot ISO shows it is version 10.0.15063.0.

    Oddly the LTIApply.log for some reason echoes back this version:

    LTIApply 5/18/2017 10:38:10 AM 0 (0x0000)
      Console > Deployment Image Servicing and Management tool LTIApply 5/18/2017 10:38:10 AM 0 (0x0000)
      Console > Version: 6.3.9600.16384 LTIApply 5/18/2017 10:38:10 AM 0 (0x0000)
      Console > Applying image LTIApply 5/18/2017 10:38:16 AM 0 (0x0000)
      Console > The operation completed successfully. LTIApply 5/18/2017 10:40:38 AM 0 (0x0000)
    Return code from command = 0 LTIApply 5/18/2017 10:40:38 AM 0 (0x0000)


    Thursday, May 18, 2017 4:39 PM
  • I would try completely uninstalling the ADK (which you should always do, no upgrades).

    Reboot your machine to be safe.

    Install the latest ADK and then update your deployment share


    If this post is helpful please vote it as Helpful or click Mark for answer.

    Thursday, May 18, 2017 6:58 PM
  • Also make sure you don't have WAIK, but that's pretty old so hopefully you don't have that

    If this post is helpful please vote it as Helpful or click Mark for answer.

    Thursday, May 18, 2017 7:00 PM
  • Thanks Dan for the assistance so far.  It's appreciated.

    • I completely uninstalled MS ADK from the server.
    • WAIK was not installed.
    • I made sure the C:\Program Files (x86)\Windows Kits folder was gone.
    • I rebooted the server.
    • I downloaded the latest MS ADK 1703 build 10.1.15063.0 and installed on the server.
    • I rebooted the server again.
    • I updated the Deployment Share and did a complete rebuild of the PE boot ISOs.
    • I booted a test machine from the new PE ISO and verified that the version of DISM.exe shows as 10.0.15063.0.  Oddly if I check the properties of C:\Program Files (x86)\Windows Kits\10\Assessment and Deployment Kit\Deployment Tools\amd64\DISM\dism.exe on the MDT server it shows as 10.1.15063.0.
    • I started the image process but alas, still no progress during the apply step.  Here is a snippet of the LTIApply.log file:

    About to run command: "DISM.exe"  /Apply-Image /ImageFile:"\\******\DeploymentShare$\Operating Systems\WIN10X641607RT\WIN10X641607RT.wim" /Index:1 /ApplyDir:V: LTIApply 5/19/2017 10:33:00 AM 0 (0x0000)
    Command has been started (process ID 2604) LTIApply 5/19/2017 10:33:00 AM 0 (0x0000)
    ZTI Heartbeat: command has been running for 0 minutes (process ID 2604) LTIApply 5/19/2017 10:33:00 AM 0 (0x0000)
    Event 41003 sent: ZTI Heartbeat: command has been running for 0 minutes (process ID 2604) LTIApply 5/19/2017 10:33:00 AM 0 (0x0000)
      Console > Deployment Image Servicing and Management tool LTIApply 5/19/2017 10:33:01 AM 0 (0x0000)
      Console > Version: 6.3.9600.16384 LTIApply 5/19/2017 10:33:01 AM 0 (0x0000)
      Console > Applying image LTIApply 5/19/2017 10:33:07 AM 0 (0x0000)
      Console > The operation completed successfully. LTIApply 5/19/2017 10:35:30 AM 0 (0x0000)
    Return code from command = 0 LTIApply 5/19/2017 10:35:30 AM 0 (0x0000)


    Friday, May 19, 2017 3:08 PM
  • Here's what I have as per my logs.

    Latest MDT version

    Microsoft Deployment Toolkit version: 6.3.8443.1000

    Latest WinPE

    Property OSCurrentVersion is now = 10.0.14393
    Property OSCurrentBuild is now = 14393
    Property OSVersion is now = WinPE

    Latest DISM

      Console > Deployment Image Servicing and Management tool
      Console > Version: 10.0.15063.0
    

    Maybe check what version of MDT you have, your setup appears to keep using an old DISM.


    If this post is helpful please vote it as Helpful or click Mark for answer.

    Friday, May 19, 2017 3:55 PM
  • Oddly I appear to have newer versions of some items than you posted:

    Our MDT/PE versions:
    Microsoft Deployment Toolkit version: 6.3.8443.1000 ZTIGather 5/19/2017 11:00:54 AM 0 (0x0000)
    ------------------------- Object Initialization ------------------------- ZTIGather 5/19/2017 11:00:54 AM 0 (0x0000)
    ------------------------- Initialization ------------------------- ZTIGather 5/19/2017 11:00:54 AM 0 (0x0000)
    Synchronizing the environments. ZTIGather 5/19/2017 11:00:54 AM 0 (0x0000)
    Property DeployRoot is now = X:\Deploy ZTIGather 5/19/2017 11:00:54 AM 0 (0x0000)
    Property DeployDrive is now = X: ZTIGather 5/19/2017 11:00:54 AM 0 (0x0000)
    Finished synchronizing the environments. ZTIGather 5/19/2017 11:00:54 AM 0 (0x0000)
    Getting OS info ZTIGather 5/19/2017 11:00:54 AM 0 (0x0000)
    Property OSCurrentVersion is now = 10.0.15063 ZTIGather 5/19/2017 11:00:54 AM 0 (0x0000)
    Property OSCurrentBuild is now = 15063 ZTIGather 5/19/2017 11:00:54 AM 0 (0x0000)
    Property OSVersion is now = WinPE ZTIGather 5/19/2017 11:00:54 AM 0 (0x0000)

    DISM Console output:
    Deployment Image Servicing and Management tool
    Version:  10.0.15063.0

    So it appears my version of MDT and DISM are the same as yours, but my version of Windows PE is newer.


    Friday, May 19, 2017 5:25 PM