[Solved] KB4284833 Integration 2018-06 June Cumulative

Discussion in 'Windows Server' started by rafalek, Jul 6, 2018.

  1. rafalek

    rafalek MDL Novice

    Jun 19, 2012
    29
    27
    0
    #1 rafalek, Jul 6, 2018
    Last edited: Jul 6, 2018
    Hello Everyone,

    I have run into a strange issue when integrating 2018-06 Cumulative Update for Windows Server 2016 for x64-based Systems (KB4284833), when building Windows Server 2016 installer .iso.

    The starting base iso is version "en_windows_server_2016_updated_feb_2018_x64_dvd_11636692.iso"

    When integrating the update into wim via dism, it quickly gets to 100% and completes successfully, however after installing the image from the built iso, Windows Update downloads the Cumulative from the previous month (2018-05 Cumulative Update for Windows Server 2016 for x64-based Systems (KB4103720), even though KB4284833 states it supersedes the KB4103720 one.

    After integrating the update in dism into wim, I have also checked the present updates via /Get-Packages in the image and it is not there.

    I did a test with previous package from May (KB4103720) and it does integrate properly, is present on the Features as well as goes through the integration process slower, before getting to 100%.

    Do you Guys have any clues what could be happening? Is KB4284833 not integratable or has some issues?

    Thanks in advance.

    EDIT: Apparently, I have missed (KB4132216) which is required for (KB4284833) to proceed. The issue has now been solved.
     
  2. erpsterm35

    erpsterm35 MDL Expert

    May 27, 2013
    1,873
    1,747
    60
    be careful, rafalek.

    June 2018 cumulative updates KB4284833 & KB4284880 include the Windows10Upgrade.exe file which is placed in the \Windows\UpdateAssistantV2\ folder. may need to remove that file to prevent unexpected upgrades to newer builds at inconvenient times when an internet connection is active.
     
  3. Tito

    Tito Super Mod / Adviser
    Staff Member

    Nov 30, 2009
    18,681
    18,589
    340
    @erpsterm35

    That's not applicable for certain SKUs, including Server ones.