Having trouble slipstreaming updates into a Windows 10 10240(original 1507) install.wim file

Discussion in 'Windows 10' started by TheCollDude489, Jan 9, 2019.

  1. TheCollDude489

    TheCollDude489 MDL Novice

    Apr 16, 2018
    38
    4
    0
    I have been trying to do this several times, but every time I attempt to do so, I get errors from DISM like 0x800f081e, 0x800f0922, and 0x8000ffff. I have used several tools so far, and all of them are failing with these error codes. An example of one of the errors I am getting is below(taken when using W10UI version 5.8):

    DISM_Error.PNG

    The install.wim file I am trying to slipstream updates into is a Windows 10 10240 image with all editions included within the image(Home, Pro, Education, Enterprise, and LTSB with their respective N and VL variants). None of the indexes inside of the install.wim have been updated.

    These are the update files I have and am currently trying to slipstream into the install.wim file:
    • Windows10.0-KB3081452-x64_3163f6a4522049a3cf72586ce1d71db1b820646d.msu
    • windows10.0-kb3161102-x64_2707817e3c3ae5c2451401355c699583694085c4.msu
    • windows10.0-kb3172729-x64_3721c0d77731ca564387070698812dd496810bd8.msu
    • windows10.0-kb4032695-x64_ce02f93e314452c2dabd74bfbe536db170560ce6.msu
    • windows10.0-kb4051600-x64_faf3fa1332ac8e6337718ae3f19146220d62acdd.msu
    • windows10.0-kb4093430-x64_f8d4096fb43e560fbc4afbff51700d2924054bc6.msu
    • windows10.0-kb4471331-x64_f202191f922afe1ee58a77ae5419d8ec9faa18f7.msu
    • windows10.0-kb4483228-x64_cae2089e899fa42def18989f9216f46d8b08d9be.msu

    The updates listed above were downloaded straight from Microsoft's update servers(got the links to them through GitHub from a file posted by abbodi1406, the creator of WHDownloader) except for the first one, which was downloaded from an archival site.

    Could someone please assist me in solving this issue?
     
  2. LiteOS

    LiteOS MDL Expert

    Mar 7, 2014
    1,564
    670
    60
    Open the update with 7zip check the parent package in the mum file
    Look up for it and install it before
     
  3. PointZero

    PointZero MDL Member

    Oct 5, 2011
    1,158
    3,194
    60
    I don't have a suggestion for your issue (sorry), but just wanted to clarify one thing: @Alphawaves is the creator of WHDownloader. abbodi1406 is the one who maintains the lists of updates in it.

    Both members have important roles and I just wanted to make sure Alphawaves gets credit for his hard work in creating it.
     
  4. abbodi1406

    abbodi1406 MDL KB0000001

    Feb 19, 2011
    8,520
    29,689
    270
    - Latest cumulative updates are for Enterprise 2015 LTSB only

    - You cannot integrate two cumultive updates together, latest is enough

    - Since August or November 2016, cumulative updates cannot be offline integrated, msu do it online (Audit mode)
    https://forums.mydigitallife.net/posts/1292702/
     
  5. LiteOS

    LiteOS MDL Expert

    Mar 7, 2014
    1,564
    670
    60
    there a package that missing from the big update
    without it wont install and give error not applicable

     
  6. TheCollDude489

    TheCollDude489 MDL Novice

    Apr 16, 2018
    38
    4
    0
    Yeah I realized that when errors were happening that having both Cumulative updates in the folder at the same time would result in a disaster. I would think that DISM would skip over the CU made for non-LTSB editions, but that turned out not to be the case. But that issue about CUs not being integrated through DISM properly is still present, even in Windows 1809?

    Which package exactly is missing from the update?
     
  7. Enthousiast

    Enthousiast MDL Tester

    Oct 30, 2009
    18,547
    24,092
    340
    No, only in 1507 (only 2015 LTSB is still supported) and x86 2016 LTSB (which is fixed by @abbodi1406 )
     
  8. TheCollDude489

    TheCollDude489 MDL Novice

    Apr 16, 2018
    38
    4
    0
    I know that it only happens to 1507, but Microsoft never official fixed it? Even after all these years?
     
  9. Enthousiast

    Enthousiast MDL Tester

    Oct 30, 2009
    18,547
    24,092
    340
    They released 2016 LTSB just one year after 2015 LTSB, for a reason, but on x86 2016 LTSB they reproduced the offline integration problem from 2015 LTSB :D
     
  10. TheCollDude489

    TheCollDude489 MDL Novice

    Apr 16, 2018
    38
    4
    0
    Oh wow. And they never back-ported the fix to 1507. I assume I'll just have to go into Audit Mode and install the update through there? Also, does creating a WIM of the updated install(if it is done through Audit Mode) prevent the installer from upgrading the current version of Windows installed on a PC using said WIM?
     
  11. Enthousiast

    Enthousiast MDL Tester

    Oct 30, 2009
    18,547
    24,092
    340
    When you need it pre-installed, Audit/install update/sysprep/capture is the way to go for 2015 LTSB. Once the update is properly installed, it is there to stay.

    Afaik, inplace upgrade will install correctly, but then you're already online, when online there is no problem installing the cu, the problem only exists for when you want to offline (pre-) integrate the update on a mounted wim.
     
  12. TheCollDude489

    TheCollDude489 MDL Novice

    Apr 16, 2018
    38
    4
    0
    Oh, OK. Thanks for telling me. I was worried that doing that process would make it unable to be used for in-place upgrades, as some people reported in the past.
     
  13. LiteOS

    LiteOS MDL Expert

    Mar 7, 2014
    1,564
    670
    60
    check the mum file for info like i said before