[DISCUSSION] Windows 10 Enterprise (N) LTSB 2016

Discussion in 'Windows 10' started by Tito, Jul 21, 2016.

  1. acer-5100

    acer-5100 MDL Expert

    Dec 8, 2018
    1,826
    1,256
    60

    That's called windows update it's there since the W9x days.

    Please realize that W10 It's not W7 or XP where you needed like 200 packages and multiple reboots.

    Here you need basically ONE LCU, ONE SSU, ONE .net update. And possibly a microcode update, depending on your CPU .

    So getting them using a web browser is not that more complicate than getting them using an automated tool

    Remember that it's a moving target. Speaking of LTSB 2015 and 2016, the short answer is yes they are two different packages that must be downloaded separately.

    On recent windows SSU is embedded inside the LCU


    Yes WU on 2016 makes the update in two steps first downloading the build 2273, then the last one. Not sure if it's on purpose or because a bug.

    Whatever, there are some bugs preventing the offline update in one run of LTSB 2015 x86 and AMD64 and LTSB 2016 x86, but there are workarounds form various sources.
     
  2. Lex24

    Lex24 MDL Novice

    Apr 14, 2018
    22
    16
    0
  3. patapout

    patapout MDL Member

    Jun 23, 2014
    118
    47
    10
    After a few years without touching this version (14393.0),
    I used the W10UI_10.25 as usual, put the SSU and LCU, tried to integrate all that but...continuous error with LCU.
    I proceed in the same way for all 21h2 and 22h2 every month, however, without any problems... Did I miss something with this 1607 ?
    Is there a new way to do it ? Sorry for my bad english...
     
  4. migascalp

    migascalp MDL Member

    Sep 18, 2009
    153
    128
    10
    I updated iso 1607 LTSB with W10UI today with no problem.
    I used the following files:
    Code:
    windows10.0-kb4013419-x64_Safe_OS_DU_2017-08-28.cab
    windows10.0-kb4023057-x64_WU_2021.05.27.cab
    windows10.0-kb4039556-x64_DU_2017-10-10.cab
    windows10.0-kb4486129-x64-ndp48.msu
    windows10.0-kb4532820-x64_DU_2020-02-10.cab
    windows10.0-kb4535680-x64_Boot_DBX_2021-01-11.msu
    windows10.0-kb5012170-x64_Boot_DBX_5285.1.4.msu
    windows10.0-kb5022503-x64-ndp48_CU_2023.02.14.msu
    windows10.0-kb5023697-x64_LCU_2023.03.14.msu
    windows10.0-kb5023788-x64_SSU_2023.03.14.msu
     
  5. Lex24

    Lex24 MDL Novice

    Apr 14, 2018
    22
    16
    0
  6. abbodi1406

    abbodi1406 MDL KB0000001

    Feb 19, 2011
    14,647
    75,961
    340
    Windows 10 1607, x86?
     
  7. patapout

    patapout MDL Member

    Jun 23, 2014
    118
    47
    10
    I tried both (just in case).
    With only LCU n' SSU ...Is there a problem with x86 ??
    Caus' a friend of mine feels nostalgic about that LTSB release and I wanna help him a bit :)
    My running OS is LTSC 2021 IoT x64
     
  8. Lex24

    Lex24 MDL Novice

    Apr 14, 2018
    22
    16
    0
    #1189 Lex24, Mar 19, 2023 at 11:54
    Last edited: Mar 19, 2023 at 13:33
    I have just integrated 2023-03-14 updates, .NET Feature Pack and Intel microcode into install.wim (x64) extracted from the original ISO, without any problems (but I didn't have a chance to try installing the OS itself).

    Host OS: 22000.1641 (Win11 21H2)
    DISM ver: 22000.653
    W10UI v10.25

    ISO: en_windows_10_enterprise_2016_ltsb_x64_dvd_9059483.iso
    SHA256: 3874BC7160ED10F28744DC2B00F9518AF99E706296B969FB7EAF26009E1CAF76

    Updates:

    kb4486129 - .NET 4.8 Feature Pack (2020-01-09)
    kb4589210-v2 - Intel Microcode Update (2021-03-09)
    kb5022503 - CU for NET 4.8 (2023-02-14)
    kb5023788 - SSU 14393.5771 (2023-03-14)
    kb5023697 - LCU 14393.5786 (2023-03-14)

    Code:
    [W10UI-Configuration]
    Target        =F:\Storage\Windows\OS\14393.230314-wim\install.wim
    Repo          =
    DismRoot      =dism.exe
    
    Net35         =0
    Net35Source   =
    Cleanup       =1
    ResetBase     =1
    LCUwinre      =0
    WinRE         =0
    UpdtBootFiles =0
    SkipEdge      =0
    
    _CabDir       =W10UItemp
    MountDir      =W10UImount
    WinreMount    =W10UImountre
    
    wim2esd       =0
    wim2swm       =0
    ISO           =0
    ISODir        =
    Delete_Source =0
    
    AutoStart     =0
    

    Code:
    ============================================================
    Running W10UI v10.25
    ============================================================
    
    ============================================================
    Extracting .cab files from .msu files...
    ============================================================
    
    1/5: windows10.0-kb4486129-x64_0b61d9a03db731562e0a0b49383342a4d8cbe36a.msu
    2/5: windows10.0-kb4589210-v2-x64_bbbf54336d6e22da5de8d63891401d8f6077d2ce.msu
    3/5: windows10.0-kb5022503-x64-ndp48_d375ad9f6acfae313e74610b43f63ae9f4473c7a.msu
    4/5: windows10.0-kb5023697-x64_0cde92f5aaba06c1a1bfd64615010c90180dcb86.msu
    5/5: windows10.0-kb5023788-x64_33ea5888c89d2888b845cf02e8d3950d13d1d1f9.msu
    
    ============================================================
    Extracting files from update cabinets (.cab)...
    *** This will require some disk space, please be patient ***
    ============================================================
    
    1/5: Windows10.0-KB4486129-x64.cab [NetFx]
    2/5: Windows10.0-KB4589210-v2-x64.cab
    3/5: Windows10.0-KB5022503-x64-NDP48.cab [NetFx]
    4/5: Windows10.0-KB5023697-x64.cab [LCU]
    5/5: Windows10.0-KB5023788-x64.cab [SSU]
    
    ============================================================
    Mounting install.wim - index 1/1
    ============================================================
    
    Deployment Image Servicing and Management tool
    Version: 10.0.22000.653
    
    Mounting image
    [==========================100.0%==========================]
    The operation completed successfully.
    
    ============================================================
    Checking Updates...
    ============================================================
    
    ============================================================
    Installing servicing stack update...
    ============================================================
    
    Deployment Image Servicing and Management tool
    Version: 10.0.22000.653
    
    Image Version: 10.0.14393.0
    
    Processing 1 of 1 - Adding package Package_for_KB5023788~31bf3856ad364e35~amd64~~14393.5771.1.0
    [==========================100.0%==========================]
    The operation completed successfully.
    
    ============================================================
    Installing updates...
    ============================================================
    
    Deployment Image Servicing and Management tool
    Version: 10.0.22000.653
    
    Image Version: 10.0.14393.5771
    
    Processing 1 of 3 - Adding package Package_for_KB4486129~31bf3856ad364e35~amd64~~10.0.1.3106
    [==========================100.0%==========================]
    Processing 2 of 3 - Adding package Package_for_KB4589210~31bf3856ad364e35~amd64~~10.0.2.1
    [==========================100.0%==========================]
    Processing 3 of 3 - Adding package Package_for_DotNetRollup~31bf3856ad364e35~amd64~~10.0.4614.5
    [==========================100.0%==========================]
    The operation completed successfully.
    
    Deployment Image Servicing and Management tool
    Version: 10.0.22000.653
    
    Image Version: 10.0.14393.5771
    
    Processing 1 of 1 - Adding package Package_for_RollupFix~31bf3856ad364e35~amd64~~14393.5786.1.13
    [==========================100.0%==========================]
    The operation completed successfully.
    
    ============================================================
    Resetting OS image base...
    ============================================================
    
    Deployment Image Servicing and Management tool
    Version: 10.0.22000.653
    
    Image Version: 10.0.14393.5771
    
    [==========================100.0%==========================]
    The operation completed successfully.
    
    ============================================================
    Unmounting install.wim - index 1/1
    ============================================================
    
    Deployment Image Servicing and Management tool
    Version: 10.0.22000.653
    
    Image File : F:\Storage\Windows\OS\14393.230314-wim\install.wim
    Image Index : 1
    Saving image
    [==========================100.0%==========================]
    Unmounting image
    [==========================100.0%==========================]
    The operation completed successfully.
    
    ============================================================
    Rebuilding install.wim ...
    ============================================================
    
    Deployment Image Servicing and Management tool
    Version: 10.0.22000.653
    
    Exporting image
    [==========================100.0%==========================]
    The operation completed successfully.
    
    ============================================================
    Removing temporary extracted files...
    ============================================================
    
    
    ============================================================
       Finished
    ============================================================
    
    
    Press 9 to exit.
    
     
  9. patapout

    patapout MDL Member

    Jun 23, 2014
    118
    47
    10
    #1190 patapout, Mar 19, 2023 at 12:31
    Last edited: Mar 19, 2023 at 13:18
  10. abbodi1406

    abbodi1406 MDL KB0000001

    Feb 19, 2011
    14,647
    75,961
    340
  11. acer-5100

    acer-5100 MDL Expert

    Dec 8, 2018
    1,826
    1,256
    60

    Oh that's terrible. Five! :D

    That doesn't move the point by one bit.

    Updating the ISO of W10 makes no sense, unleess you are in some corner cases like You have a good connection at work, but poor at home, and you prepare the ISO where the connection is good, to install it where the connection is poor.

    Make no sense even for sysadmins who manage 200 PCs. Unless you are a really ignorant sysasmin you doesn't touch an ISO at all, just use ONE native VHD and copy it where it's needed.

    Seriously preparing an updates ISO make sense for xp/vista/w7/w8.x, for W10/W11 is better to employ the time having some sex with your partner/ having a nice dinner, or doing something else of useful/pleasurable.;)