The classic: Litetouch deployment failed, Return Code = -2147467259 0x80004005


  • Hi all,

    Trying to deploy Windows 10 to a Hyper V VM with MDT. It gets to "Install Operating System" in the Task Sequence and then fails. 

    BDD.log is saying this:

    FAILURE ( 5624 ): 13: Run DISM:  /Apply-Image /ImageFile:"\\mdtserver\DeploymentShare$\Operating Systems\Windows 10 Pro x64 1803\WIN10PRO.wim" /Index:1 /ApplyDir:D:
    Litetouch deployment failed, Return Code = -2147467259  0x80004005

    It is a 50 GB Virtual Drive and the TS looks to be partitioning it correctly so I don't believe it's a partitioning issue. 

    The VM has 4GB of RAM.

    DISM.log is saying this:

    2018-05-02 11:20:00, Error                 DISM   DISM WIM Provider: PID=1788 TID=1768 onecore\base\ntsetup\opktools\dism\providers\wimprovider\dll\wimmanager.cpp:991 - CWimManager::Apply(hr:0x8007000d)
    2018-05-02 11:20:00, Error                 DISM   DISM Imaging Provider: PID=1788 TID=1768 onecore\base\ntsetup\opktools\dism\providers\imagingprovider\dll\genericimagingmanager.cpp:2813 - CGenericImagingManager::InternalCmdWimApply(hr:0x8007000d)
    2018-05-02 11:20:00, Error                 DISM   DISM Imaging Provider: PID=1788 TID=1768 onecore\base\ntsetup\opktools\dism\providers\imagingprovider\dll\genericimagingmanager.cpp:547 - CGenericImagingManager::ExecuteCmdLine(hr:0x8007000d)

    Any  ideas?

    Wednesday, May 02, 2018 4:30 PM

All replies

  • Well, I updated to the newest ADK and it got to the point where it finishes installing the OS but then fails after that.

    DISM.log is now showing:

    2018-05-02 14:57:57, Error                 CSI    00000003 (F) c0000103 [Error,Facility=(system),Code=259 (0x0103)] #7# from WCP::Implementation::CDirectoryEnumerator::InternalInitializeParent=0, Directory=[l:33]'\??\D:\Windows\System32\downlevel'[gle=0xd0000103]
    2018-05-02 14:57:57, Error                 CSI    00000004@2018/5/2:22:57:57.280 (F) onecore\base\wcp\rtllib\nativelib\ntenumerators.cpp(133): Error c0000103 [Error,Facility=(system),Code=259 (0x0103)] originated in function WCP::Implementation::CDirectoryEnumerator::InternalInitialize expression: status
    2018-05-02 14:57:57, Error                 CSI    00000005 (F) HRESULT_FROM_WIN32(267) #5# from SssPreloadDownlevelDependenciesFlags=1 Cookie=[version=10.0.17134.1, location=[l:113 ml:120]'\??\D:\Windows\WinSxS\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.17134.1_none_eedfeda03074e04e\', arch=amd64][gle=0x8007010b]
    2018-05-02 14:57:57, Error                 DISM   DISM.EXE: Failed to bind to ssshim.dll inside D:\Windows. HRESULT=8007010B

    BDD is saying: 

      Console > Deployment Image Servicing and Management tool	LTIApply	5/2/2018 2:57:57 PM	0 (0x0000)
      Console > Version: 10.0.17134.1	LTIApply	5/2/2018 2:57:57 PM	0 (0x0000)
      Console > Error: 50	LTIApply	5/2/2018 2:57:57 PM	0 (0x0000)
      Console > DISM does not support servicing a Windows Vista RTM or earlier operating system. 	LTIApply	5/2/2018 2:57:57 PM	0 (0x0000)
      Console > If the operating system is supported check that SSShim.DLL is present.	LTIApply	5/2/2018 2:57:57 PM	0 (0x0000)
      Console > The DISM log file can be found at X:\WINDOWS\Logs\DISM\dism.log	LTIApply	5/2/2018 2:57:57 PM	0 (0x0000)
    Return code from command = 50	LTIApply	5/2/2018 2:57:57 PM	0 (0x0000)
    FAILURE ( 5627 ): 50: Run DISM.exe	LTIApply	5/2/2018 2:57:57 PM	0 (0x0000)
    Litetouch deployment failed, Return Code = -2147467259  0x80004005	LiteTouch	5/2/2018 2:57:58 PM	0 (0x0000)

    SSShim.dll is present on the deployment machine under X:\Windows\System32\

    • Edited by henry-jtek Wednesday, May 02, 2018 8:41 PM
    Wednesday, May 02, 2018 7:06 PM
  • After reading the logs on a successful build 1709 deployment, I have come to the conclusion that it's failing when DISM tries to apply the Unattend.xml only on build 1803. I know the 1803 ADK is being accessed during the task sequence because it says Version: 10.0.17134.1. The 1803 image version on MDT matches the version of DISM available on the system so I'm not sure why I am experiencing this error.

    Is this a new bug with 1803/1803 ADK? Why is MDT unable to see that the Windows 10 1803 WIM is not an unsupported OS? (Below Windows Vista RTM) 

    Thursday, May 03, 2018 2:28 PM
  • Could you upload your BDD.log to an external hosting website so that I could take a look?


    Vacuum Breather Blog | Wing Commander Saga | Twitter

    Note: Posts are provided "AS IS" without warranty of any kind. If posts are helpful please don't forget to rate them as "Helpful" or as "Answer".

    Thursday, May 03, 2018 6:23 PM
  • Is Dynamic Memory enabled on your Hyper-V virtual machine? If so, try turning it off and run your task sequence again.

    That did the trick for me when I was deploying a MDT TS on a Hyper-V vm.
    Friday, May 18, 2018 11:16 AM