[DISCUSSION] Windows 10 Enterprise (N) LTSB 2016

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

  1. Enthousiast

    Enthousiast MDL Tester

    Oct 30, 2009
    38,801
    67,985
    450
    I would install the 19041.450 Education.
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  2. QS2k15

    QS2k15 MDL Novice

    Dec 27, 2014
    31
    3
    0
    #1102 QS2k15, Sep 6, 2020
    Last edited: Sep 7, 2020
    So the direct link and the torrent link on post #1 aren't functioning. Anyone have a suggestion where to find 2016 LTSB specifically. Thank you.
     
  3. Enthousiast

    Enthousiast MDL Tester

    Oct 30, 2009
    38,801
    67,985
    450
    #1103 Enthousiast, Sep 6, 2020
    Last edited: Sep 7, 2020
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  4. QS2k15

    QS2k15 MDL Novice

    Dec 27, 2014
    31
    3
    0
    #1104 QS2k15, Sep 7, 2020
    Last edited: Sep 7, 2020
    So that link you offered has been removed for ToS violations

    and I meant 2016 LTSB sorry I have the 2015 version i mis typed.

    I am 100% looking for the 2016 LTSB iso.

    Thank you.
     
  5. Enthousiast

    Enthousiast MDL Tester

    Oct 30, 2009
    38,801
    67,985
    450
    That was fast, i will send you a private convo.
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  6. xinso

    xinso MDL Guru

    Mar 5, 2009
    7,602
    10,021
    240
    #1108 xinso, Sep 7, 2020
    Last edited: Sep 8, 2020
    These two are Feature Update for Non-LTSB editions:
    KB4049411
    KB4033631
     
  7. sxhilkxdxm

    sxhilkxdxm MDL Junior Member

    Mar 7, 2020
    83
    22
    0
    #1109 sxhilkxdxm, Sep 9, 2020
    Last edited: Sep 9, 2020
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  8. abbodi1406

    abbodi1406 MDL KB0000001

    Feb 19, 2011
    13,128
    64,250
    340
    @summersuns

    run command prompt as administrator, then change to W10UI.cmd folder path
    execute W10UI.cmd and press "0" to start the process

    this mightshow the reason to terminating
     
  9. summersuns

    summersuns MDL Member

    Oct 26, 2014
    112
    20
    10
    Thanks for reply:

    Code:
    ============================================================
    Running W10UI v10.15
    ============================================================
    
    All applicable updates are detected as installed
    
    ============================================================
    Removing temporary extracted files...
    ============================================================
    
    0 was unexpected at this time.
    
    c:\WORK\W10UI_10.15f>
     
  10. summersuns

    summersuns MDL Member

    Oct 26, 2014
    112
    20
    10
    @ abbodi1406

    I noticed you liked my post but have nothing more to say about it.
    Does this mean you do not know what might be preventing the process from summarily terminating?
    I
    ran the script in a VirtualBox image of Windows 10 2021 LTSc while waiting for a reply but that proved to be exactly the same: complete the options press" 0" and watch to script window vanish!

    However I was able to browse the script reademe many times and cannot see where I am making an error.
    Cheers
     
  11. Sajjo

    Sajjo MDL Member

    Feb 6, 2018
    1,874
    2,609
    60
    @summersuns
    I gave you a like as well.
    Do you want to add me to the equation as well?

    Na, don't mind.

    Cheers
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  12. Lex24

    Lex24 MDL Novice

    Apr 14, 2018
    7
    4
    0
  13. abbodi1406

    abbodi1406 MDL KB0000001

    Feb 19, 2011
    13,128
    64,250
    340
    Still investigating

    are you trying to update the current VM? or extracted ISO?

    you could set the options correctly in W10UI.ini
    then edit W10UI.cmd and enable debug mode
    save and run
    then share the Debug.log or tmp.log
     
  14. summersuns

    summersuns MDL Member

    Oct 26, 2014
    112
    20
    10
    #1117 summersuns, Dec 11, 2021
    Last edited: Dec 11, 2021
    DELETED
     
  15. summersuns

    summersuns MDL Member

    Oct 26, 2014
    112
    20
    10
  16. summersuns

    summersuns MDL Member

    Oct 26, 2014
    112
    20
    10
    #1119 summersuns, Dec 11, 2021
    Last edited: Dec 12, 2021
    abbodi1406

    Managed to run the W10UI script successfully.
    Produced an updated ISO

    Thanks for your interest in troubleshooting
     
  17. Lex24

    Lex24 MDL Novice

    Apr 14, 2018
    7
    4
    0
    #1120 Lex24, Dec 13, 2021
    Last edited: Dec 15, 2021
    I have done some testing integrating the latest updates (as listed in my post #1115 above) into install.wim. Because of the size of LCU (1.6 GB) there are significant differences in the size of the updated install.wim, depending on the integration method:

    2.82 GB - original file
    2.92 GB - W10UI_10.15f with both Cleanup and ResetBase set to 1
    4.11 GB - W10UI_10.15f with both Cleanup and ResetBase set to 0
    4.72 GB - standard dism with both Cleanup and ResetBase set to 1

    It seems that abbodi's W10UI script performs some extra cleanup compared to the standard dism method (as shown in the Spoiler below).

    I usually install Windows directly from install.wim using dism and then install BCD files and partition or disk boot code manually. This way I do not need boot.wim or ISO file for anything, that is why they were not included in my tests.

    :: Integrate updates into Win10 Enterprise 2016 LTSB source
    ::
    :: change WKDIR variable as needed (Work Directory)
    :: place install.wim in WKDIR
    :: place updates in WKDIR\Updates (cab or msu files, each file on the separate line)

    @echo off
    set WKDIR=E:\WinISO

    mkdir %WKDIR%\WIN
    Dism /Mount-Image /ImageFile:%WKDIR%\install.wim /index:1 /MountDir:%WKDIR%\WIN
    Dism /Image:%WKDIR%\WIN /Add-Package /PackagePath:%WKDIR%\Updates\windows10.0-kb5005698-x64_ff882b0a9dccc0c3f52673ba3ecf4a2a3b2386ca.msu
    Dism /Image:%WKDIR%\WIN /Add-Package /PackagePath:%WKDIR%\Updates\windows10.0-kb4486129-x64_0b61d9a03db731562e0a0b49383342a4d8cbe36a.msu
    Dism /Image:%WKDIR%\WIN /Add-Package /PackagePath:%WKDIR%\Updates\windows10.0-kb4577586-x64_809b9640d04c5af4c7e78499052abaa936cb670a.msu
    Dism /Image:%WKDIR%\WIN /Add-Package /PackagePath:%WKDIR%\Updates\windows10.0-kb4589210-v2-x64_bbbf54336d6e22da5de8d63891401d8f6077d2ce.msu
    Dism /Image:%WKDIR%\WIN /Add-Package /PackagePath:%WKDIR%\Updates\windows10.0-kb5007152-x64-ndp48_5631ba2bdcb5a06578ebbd83970739fb87a3ac4f.msu
    Dism /Image:%WKDIR%\WIN /Add-Package /PackagePath:%WKDIR%\Updates\windows10.0-kb5008601-x64_c0fddabd5b9698548d741effbdfd03a4f2440ba2.msu
    Dism /Image:%WKDIR%\WIN /Cleanup-Image /StartComponentCleanup /ResetBase
    Dism /Unmount-Image /MountDir:%WKDIR%\WIN /Commit
    rmdir %WKDIR%\WIN