locked
ADK 1809 / DISM fails on W10 LTSC RRS feed

  • Question

  • Hi,

    I'm trying to capture mounted Hyper-V snapshot with DISM to construct custom install.wim file. I used that process with W10 1607 LTSB and never had problems. After upgrading to 1809 DISM fails with the message:

    Error: 1805
    The environment specified is invalid.

    I'm using correct version of ADK and installed WinPE addon too (restarting the PC between installations):

    Windows 10 Enterprise LTSC 
    version 1809 
    build 17763.134

    Deployment Image Servicing and Management tool
    Version: 10.0.17763.1

    DISM log contains 1 warning:

    2018-11-16 10:37:44, Warning               DISM   DISM Provider Store: PID=8128 TID=3464 Failed to load the provider: C:\Program Files (x86)\Windows Kits\10\Assessment and Deployment Kit\Deployment Tools\amd64\DISM\MetaDeployProvider.dll. - CDISMProviderStore::Internal_GetProvider(hr:0x8007007e)

    And several errors:

    [8128] [0xc144012e] 
    2018-11-16 10:37:44, Error                 DISM   DISM WIM Provider: PID=8128 E:\ZZZZZ1259162177.txt (HRESULT=0x8007070D) - CWimManager::WimProviderMsgLogCallback
    2018-11-16 10:37:44, Error                 DISM   DISM WIM Provider: PID=8128 TID=3464 onecore\base\ntsetup\opktools\dism\providers\wimprovider\dll\wimmanager.cpp:1193 - CWimManager::Capture(hr:0x8007070d)
    2018-11-16 10:37:44, Error                 DISM   DISM WIM Provider: PID=8128 TID=3464 onecore\base\ntsetup\opktools\dism\providers\wimprovider\dll\wimmanager.cpp:4626 - CWimManager::InternalCmdCaptureBase(hr:0x8007070d)
    2018-11-16 10:37:44, Error                 DISM   DISM WIM Provider: PID=8128 TID=3464 "Error executing command" - CWimManager::InternalExecuteCmd(hr:0x8007070d)
    2018-11-16 10:37:44, Error                 DISM   DISM WIM Provider: PID=8128 TID=3464 onecore\base\ntsetup\opktools\dism\providers\wimprovider\dll\wimmanager.cpp:2203 - CWimManager::ExecuteCmdLine(hr:0x8007070d)
    2018-11-16 10:37:44, Error                 DISM   DISM.EXE: WimManager processed the command line but failed. HRESULT=8007070D
    2018-11-16 10:37:44, Info                  DISM   DISM.EXE: Image session has been closed. Reboot required=no.

    That ZZZZ... file is from PA Traps software and it wasn't a problem before (when using the same process on 1607 LTSB version of Windows/ADK 1607).

    Can it have anything to do with version of ADK and W10 LTSC? I think ADK came out with initial W10 version from October, and I'm using Windows released this week? Any help/ideas are greatly appreciated.

    Friday, November 16, 2018 2:52 PM

Answers

  • I have tried the same process using W10 Education, v1809 PC with native DISM tool and it worked, after disabling Secure Boot (DISM error 577 IIRC).

    So, I have to assume that PC I used for 2016 LTSB edition is not suited for 2019 LTSC.

    • Marked as answer by Alek_K Friday, January 18, 2019 11:15 AM
    Friday, January 18, 2019 11:14 AM

All replies

  • Hi Alek, 

    Does the issue occur on other Windows 10 1809 LTSC devices?

    Please try to run command line "DISM.exe /Online /Cleanup-image /Restorehealth" to make sure there is no corruption in your system. 

    If the issue persists, please upload %windir%/Logs/CBS/CBS.log to One Drive and paste the link here. 

    Bests, 


    Please remember to mark the replies as answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com

    • Edited by Joy-Qiao Monday, November 19, 2018 7:24 AM
    Monday, November 19, 2018 7:24 AM
  • I haven't tried it on other PCs - it is a process of preparing custom W10 installation media using Hyper-V snapshots. I'm editing virtual machine with W10 in Audit Mode, sysprepping, creating the checkpoint and mounting it as a drive. Then using DISM I'm creating install.wim from the mounted checkpoint. All works OK on LTSB 1607 and doesn't work at all with the new version.

    I did DISM cleanup in the VM and then also on the host, targeting the mounted checkpoint (dism /image:E: /cleanup-image /restorehealth) - there was no CBS log, but there is a DISM log

    https://1drv.ms/u/s!AislS8egB01UbXWXeN8oQqKnz3U

    Monday, November 19, 2018 9:01 AM
  • Hi Alek, 

    To narrow down the issue, would you capture several system images in a same Windows PE environment, and then capture a same system image in another different Windows PE environment?

    Bests, 


    Please remember to mark the replies as answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    Thursday, November 22, 2018 6:01 AM
  • Hi Alek, 

    Any update?

    Bests, 


    Please remember to mark the replies as answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    Monday, November 26, 2018 1:58 AM
  • Hi, 

    I'm sorry, I don't understand your instructions. I am able to capture .wim file from mounted Hyper-V snapshot for W10 LTSB 1607, using ADK for 1607. I successfully used that process on different builds of W10 Enterprise, always with the correct ADK (1607) installed, using DISM that comes with it.

    Trying the same process for W10 LTSC 1809 with ADK 1809, doesn't work.

    I'd appreciate more details about the tasks you want me to do, thanks.

    P.S. Sorry for delay in the answer.

    AK

    Tuesday, November 27, 2018 9:27 AM
  • Hi Alek, 

    After we create a bootable Windows PE, we could capture system image offline with this Windows PE tool. So to narrow down the issue, we capture several system image offline with a same USB Windows PE tool.  Also, we could create 2 USB Windows PE tool, and capture a same system image offline with both USB Windows PE. And then compare if the issue occur on them too.

    Bests, 


    Please remember to mark the replies as answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    Tuesday, December 4, 2018 7:21 AM
  • Ok, I can try to do that. But please keep in mind that it is not the process I am using. What I'm doing is:

    1. Create Hyper-V VM and install W10 LTSC in it, up to the point where it is possible to enter Audit Mode

    2. Configure the system in Audit Mode and once it's done sysprep it.

    3. Create checkpoint from the sysprepped VM and mount that checkpoint in Windows as read-only VHD

    4. Use DISM to capture mounted checkpoint as a .wim file

    5. Decompress Windows installation ISO and substitute install.wim found in that ISO with the file(s) created with DISM

    6. Use oscdimg tool to create new ISO that can be used to install modified Windows

    That process works very well for W10 LTSB 1607. For W10 LTSC 1809 step 4 fails - DISM tool does not create the .wim file correctly. I suppose I can try what you are suggesting, but that'd be a different workflow. 

    regards,

    Tuesday, December 4, 2018 8:25 AM
  • I have tried the same process using W10 Education, v1809 PC with native DISM tool and it worked, after disabling Secure Boot (DISM error 577 IIRC).

    So, I have to assume that PC I used for 2016 LTSB edition is not suited for 2019 LTSC.

    • Marked as answer by Alek_K Friday, January 18, 2019 11:15 AM
    Friday, January 18, 2019 11:14 AM