none
MDT Fails when deploying 1803 and 1809 RRS feed

  • Question

  • Dear Colleagues,

    I would like to ask for your assistance:

    - I have a Windows Server 2012 R2. 1809 ADK, MDT 6.3.8456.1000, DISM 10.0.17763.1 + WinPE 1809 installed.

    - Deploying Windows 10 1703 is always succeed.

    - I have an alternate DeplymentShare on the same server and 1803 deployment is succeed. 

    - Reference Image .wim file caputed with DISM 10.0.17763.1.

    - But with the main DeploymentShare I am unable to deploy the OS. I receive the following error after extracting .wim (100%):

    LTIApply.log

    ...

    Error: 50 DISM does not support servicing a Windows Vista RTM or earlier operating system.

    If the operating system us supported chech that SSShim.DLL is present.

    ...

    Did any of you run into this issue?

    Thank you in advance!

    Thursday, March 28, 2019 2:29 PM

Answers

  • ***UPDATE***

    Issue resolved.

    I had to reinstall Windows on the capturing computer. I had 1709, now have 1809. It seems it is not enough to have the latest ADK and DISM.

    Friday, March 29, 2019 1:37 PM

All replies

  • ***UPDATE***

    It seems, I have issues with the reference image's .wim file, due: 

    Deployment Image Servicing and Management tool
    Version: 10.0.16299.15


    Error: 13

    The data is invalid.

    The DISM log file can be found at C:\WINDOWS\Logs\DISM\dism.log

    [1692] [0x8007000d] ProcessDirectory:(640): The data is invalid.
    [1692] [0x8007000d] ProcessDirectory:(889): The data is invalid.
    [1692] [0x8007000d] ProcessDirectory:(889): The data is invalid.
    [1692] [0x8007000d] ProcessDirectory:(889): The data is invalid.
    [1692] [0x8007000d] ReadMetaDataBuffer:(120): The data is invalid.
    [1692] [0x8007000d] ReadMetaDataFile:(246): The data is invalid.
    [1692] [0x8007000d] WIMLoadImageInternal:(197): The data is invalid.
    2019-03-29 10:32:58, Error                 DISM   DISM WIM Provider: PID=1692 TID=2532 "Failed to open image." - CWimImageInfo::Mount(hr:0x8007000d)
    2019-03-29 10:32:58, Error                 DISM   DISM WIM Provider: PID=1692 TID=2532 onecore\base\ntsetup\opktools\dism\providers\wimprovider\dll\wimmanager.cpp:2684 - CWimManager::InternalOpMount(hr:0x8007000d)
    2019-03-29 10:32:58, Error                 DISM   DISM WIM Provider: PID=1692 TID=2532 onecore\base\ntsetup\opktools\dism\providers\wimprovider\dll\wimmanager.cpp:4028 - CWimManager::InternalCmdMount(hr:0x8007000d)
    2019-03-29 10:32:58, Error                 DISM   DISM WIM Provider: PID=1692 TID=2532 "Error executing command" - CWimManager::InternalExecuteCmd(hr:0x8007000d)
    2019-03-29 10:32:58, Error                 DISM   DISM WIM Provider: PID=1692 TID=2532 onecore\base\ntsetup\opktools\dism\providers\wimprovider\dll\wimmanager.cpp:2201 - CWimManager::ExecuteCmdLine(hr:0x8007000d)

    Friday, March 29, 2019 9:48 AM
  • ***UPDATE***

    Issue resolved.

    I had to reinstall Windows on the capturing computer. I had 1709, now have 1809. It seems it is not enough to have the latest ADK and DISM.

    Friday, March 29, 2019 1:37 PM