[WIM] [Imaging] Did something change in the way Windows 10 1803 installs?

Discussion in 'Windows 10' started by KaoDome, Aug 10, 2018.

  1. KaoDome

    KaoDome MDL Novice

    Jul 31, 2009
    29
    12
    0
  2. KaoDome

    KaoDome MDL Novice

    Jul 31, 2009
    29
    12
    0
    Thank you for that joluboga, when I saw your reply there I thought that could be it, but after executing the command in 1709 I saw everything was populated correctly so that doesn't seem to be the cause.

    Deployment Image Servicing and Management tool
    Version: 10.0.16299.15

    Details for image : WIMTest.wim

    Index : 1
    Name : Windows 10 Education
    Description : Bare installation for WIM test purposes.
    Size : 11,010,108,083 bytes
    WIM Bootable : No
    Architecture : x86
    Hal : acpiapic
    Version : 10.0.17134
    ServicePack Build : 1
    ServicePack Level : 1
    Edition : Education
    Installation : Client
    ProductType : WinNT
    ProductSuite : Terminal Server
    System Root : WINDOWS
    Directories : 17309
    Files : 80755
    Created : 8/9/2018 - 3:20:32 PM
    Modified : 8/9/2018 - 3:20:37 PM
    Languages :
    en-US (Default)

    The operation completed successfully.
     
  3. Enthousiast

    Enthousiast MDL Tester

    Oct 30, 2009
    16,103
    19,690
    340
    #4 Enthousiast, Aug 10, 2018
    Last edited: Aug 10, 2018
  4. Enthousiast

    Enthousiast MDL Tester

    Oct 30, 2009
    16,103
    19,690
    340
    I did several tests and now i remember 1709 or 1803 was troublesome when servicing by dism, you needed to have adk 17134.1 installed, iirc.

    My dism tests (1709 and 1803) resulted in errors:
    Code:
    dism /capture-image /imagefile:e:\install3.wim /capturedir:f:\ /name:"Test 1803 Captured By 1709" /Description:"Test 1803 Captured By 1709" /compress:maximum /checkintegrity /verify
    
    D:\>dism /capture-image /imagefile:e:\install3.wim /capturedir:f:\ /name:"Test 1803 Captured By 1709" /Description:"Test 1803 Captured By 1709" /compress:maximum /checkintegrity /verify
    
    Deployment Image Servicing and Management tool
    Version: 10.0.16299.15
    
    Saving image
    [===========================59.0%==                        ]
    
    Error: 577
    
    Windows cannot verify the digital signature for this file. A recent hardware or software change might have installed a file that is signed incorrectly or damaged, or that might be malicious software from an unknown source.
    
    The DISM log file can be found at X:\windows\Logs\DISM\dism.log
    
    D:\>
    Code:
    dism /capture-image /imagefile:d:\install_DISM_1803.wim /capturedir:f:\ /name:"Test 1803 Captured By 1803" /Description:"Test 1803 Captured By 1803" /compress:maximum /checkintegrity /verify
    
    Microsoft Windows [Version 10.0.17134.167]
    Not enough memory resources are available to process this command.
    
    X:\Sources>dism /capture-image /imagefile:d:\install_DISM_1803.wim /capturedir:f:\ /name:"Test 1803 Captured By 1803" /Description:"Test 1803 Captured By 1803" /compress:maximum /checkintegrity /verify
    
    Deployment Image Servicing and Management tool
    Version: 10.0.17134.1
    
    Saving image
    [========================   42.0%                          ]
    
    Error: 80
    
    The file exists.
    
    The DISM log file can be found at X:\windows\Logs\DISM\dism.log
    
    X:\Sources>dism /capture-image /imagefile:d:\install_DISM_1803.wim /capturedir:f:\ /name:"Test 1803 Captured By 1803" /Description:"Test 1803 Captured By 1803" /compress:maximum /checkintegrity /verify
    
    Deployment Image Servicing and Management tool
    Version: 10.0.17134.1
    
    Saving image
    [========================   42.0%                          ]
    
    Error: 80
    
    The file exists.
    
    The DISM log file can be found at X:\windows\Logs\DISM\dism.log
    
    X:\Sources>
    Using GimageX GUI tool I was able to successfully capture the 1803 install but with the same results as you had, not usable wim.
     
  5. Atari800XL

    Atari800XL MDL Addicted

    Apr 3, 2011
    650
    1,045
    30
    Thanks for your DISM tests, Enthousiast.
    I know from using ImageX for direct apply of UUP files that recent ImageX versions appear to be buggy (as confirmed by "JFX", developer of GetWAIKTools, etc.).
    I get the best (apply) results with ImageX from build 15063, maybe capturing is OK in that version as well? Maybe you can do some tests? (I'm using Wimlib for capturing myself, which is a bit faster)

    So I would recommend Wimlib for capture, and ImageX 15063 for apply.

    JFX used to provide a way to download older WAIK tools as well, but the links to older GetWAIKTools versions doesn't seem to work at the moment. I will ask him what's wrong...
     
  6. taviruni

    taviruni MDL Member

    May 8, 2010
    193
    113
    10
    Hello my friend, nice to see you around. But let me disagree a little, I think it is safer to say:

    So I would recommend Wimlib for capture and apply.
     
  7. Atari800XL

    Atari800XL MDL Addicted

    Apr 3, 2011
    650
    1,045
    30
    Sure, Wimlib is great for both, still: For me ImageX is faster for apply (specially for UUP files)

    It's nice to have a choice between the two, let's see if it helps the original poster.
     
  8. KaoDome

    KaoDome MDL Novice

    Jul 31, 2009
    29
    12
    0
    Thank you everybody for your replies! To be honest I am more interested in why this is happening at this point haha

    I was doing some tests too and it may be a bug in the imaging components of Windows 1709 (and previous?). Using the same DISM command line as I did but from 1803 the leads to an image that can be perfectly mounted or opened with 7-Zip for example. And the same happens if you capture using wimlib, it generates a functional image even if you capture in 1709 because it doesn't rely in Windows' imaging API.

    I nailed it down to the System32 directory, but I still don't know why it happens though. Capturing that directory alone leads to an image that can't be mounted or applied with 1709 utils.