none
MDT Deployment fails with -2147467259 unless I reboot server. RRS feed

  • Question

  • Task Sequence will get to Inject Drivers stage then go VERY slowly, taking about 10-15 (sometimes more) minutes to complete the task.  It will then fail at the Applying Image stage with 'Litetouch deployment failed, Return Code = -2147467259  0x80004005'

    I have tried doing diskpart, clean all on the drive, to no avail.  The only thing that has worked is to reboot the server.  It then seems to work for a little while, maybe a day or so, before needing another reboot.

    Microsoft Deployment Toolkit 2013 Update 2 on Windows Server 2012 R2, deploying Windows 10 Enterprise  1511.  

    Any help would be appreciated!


    • Edited by JonathanFl Monday, December 12, 2016 9:32 PM
    Monday, December 12, 2016 9:31 PM

Answers

  • Error:

    Console > Error: 999
    Console > An error occurred while loading DISM. The DISM tool may be corrupt. 
    Console > Try reinstalling DISM.
    

    Wow, I have NEVER seen that error before.   :^O

    I would uninstall the ADK on your server, and re-install the latest ADK. then perform a FULL update on the deployment share, that should force MDT to copy down dism.exe again from the ADK.


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

    Monday, December 12, 2016 9:59 PM
    Moderator

All replies

  • If you are still having problems, please copy your bdd.log file to a public site like One Drive and share the link here.

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

    Monday, December 12, 2016 9:47 PM
    Moderator
    • Edited by JonathanFl Monday, December 12, 2016 9:57 PM
    Monday, December 12, 2016 9:56 PM
  • Error:

    Console > Error: 999
    Console > An error occurred while loading DISM. The DISM tool may be corrupt. 
    Console > Try reinstalling DISM.
    

    Wow, I have NEVER seen that error before.   :^O

    I would uninstall the ADK on your server, and re-install the latest ADK. then perform a FULL update on the deployment share, that should force MDT to copy down dism.exe again from the ADK.


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

    Monday, December 12, 2016 9:59 PM
    Moderator
  • I would uninstall the ADK on your server, and re-install the latest ADK. then perform a FULL update on the deployment share, that should force MDT to copy down dism.exe again from the ADK.

    I'll give this a go.  Thanks for finding that!
    Monday, December 12, 2016 10:05 PM
  • Well I've tested several deployments today.  It seems very stable.  Thanks for your help!

    Jonathan

    Tuesday, December 13, 2016 9:45 PM