How to: Make a Windows 10 "1703 LTSB" ISO

Discussion in 'Windows 10' started by damianfox, Nov 19, 2015.

  1. AeonX

    AeonX MDL Addicted

    May 24, 2013
    793
    719
    30
    #341 AeonX, Apr 18, 2016
    Last edited by a moderator: Apr 20, 2017
    Use this instead:

    Code:
    forums.mydigitallife.net/threads/68791-Add-Multilingual-Support-to-Windows-10-Distribution-automated-batch-script
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  2. goitia93

    goitia93 MDL Novice

    Apr 18, 2016
    5
    0
    0
    Much thanks for this trick!
     
  3. jc8

    jc8 MDL Novice

    Mar 12, 2016
    31
    17
    0
    #343 jc8, Apr 20, 2016
    Last edited: Apr 20, 2016
    Hello there lads,
    I followed the tutorial to the letter and everything is working like a charm, thanks very much.
    The only thing that puzzles me now, Windows Subsystem for Linux (Beta) option is not available though :(
    Isn't the mentioned ISO up-to-date ? Am I supposed to install any updates ?
    Edit: It looks like I need build 14316.
     
  4. perre

    perre MDL Senior Member

    Nov 2, 2013
    285
    12
    10
    A question if I can so I only remove the telemetry in build 10586.:clap:
     
  5. sebus

    sebus MDL Guru

    Jul 23, 2008
    6,356
    2,026
    210
    #345 sebus, Apr 23, 2016
    Last edited by a moderator: Apr 20, 2017
  6. perre

    perre MDL Senior Member

    Nov 2, 2013
    285
    12
    10
    I updated the iso with MSMG Toolkit to update comulative the last but after making the update installation is again the installation of poerque comulative?:mad:
     
  7. T-S

    T-S MDL Guru

    Dec 14, 2012
    3,984
    1,331
    120

    Did you launch your command from a long path like the desktop?

    If so try from something of very short like C:\sxs, sometimes it helps
     
  8. abbodi1406

    abbodi1406 MDL KB0000001

    Feb 19, 2011
    16,191
    84,706
    340
    Are you using the old SxSExpand.exe? or the latest one (which require hex editing)?
     
  9. Tiger-1

    Tiger-1 MDL Guru

    Oct 18, 2014
    7,897
    10,733
    240
    sorry, but I think making this work is one a waste of time ;) because the kernel is the same for all Windows versions so after long research into the architecture in o.s. I see clearly that Windows Enterprise LTSB have all files and structures as Windows 10 PRO only stay disabled then I think that making some "tweaks" in the registry versions of LTSB turn in PRO easily as result is pure wast of time with none benefit; some days earlier I told that versions of LTSB is one super version of Windows 7 I'AM WRONG :cool:
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  10. sebus

    sebus MDL Guru

    Jul 23, 2008
    6,356
    2,026
    210
    Nobody forces you to even be in this thread, yet alone use any of it...
     
  11. Tiger-1

    Tiger-1 MDL Guru

    Oct 18, 2014
    7,897
    10,733
    240
    right is only my opinion ;) I don't want critisize nobody in this thread or your work on it :cool:
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  12. abbodi1406

    abbodi1406 MDL KB0000001

    Feb 19, 2011
    16,191
    84,706
    340
  13. harkaz

    harkaz MDL Novice

    Dec 27, 2012
    42
    87
    0
    MSMG ToolKit v4.3 is simply the best removal utility available! I had tried a handful of others before using this one.
    It just works exactly as it should. Essential to enhance privacy and performance of your Windows 10 images.
     
  14. shao_xie

    shao_xie MDL Novice

    May 11, 2016
    2
    0
    0
    I tried this tool- I removed many components, but the final output iso, was larger than the original iso - too large to burn onto a single layer dvd (about 4.7 gb). I did save source, then rebuild image. any advice to get the file size smaller is appreciated. :confused:
     
  15. Prosto

    Prosto MDL Addicted

    Mar 18, 2015
    768
    307
    30
    need to convert install.wim in install.esd in the first item of the main menu.

    and then apply to item #6 and create iso
     
  16. SunLion

    SunLion MDL Senior Member

    May 11, 2011
    317
    371
    10
    Only complementing, select “Apply” and “Re-Build Source WIM Image” before you convert wim to esd.
     
  17. T-S

    T-S MDL Guru

    Dec 14, 2012
    3,984
    1,331
    120

    It depends on the ISO you started from.

    If it was ESD based is normal that the WIM one is larger, if you started from a WIM one, the final WIM must be smaller than the original one, if you exported and rebuild the WIM
     
  18. dhjohns

    dhjohns MDL Guru

    Sep 5, 2013
    3,262
    1,731
    120
    I have my files on F-Drive. You don't need to rename it to Enterprise, any name will do. This is from my instructions to convert Pro to Enterprise. This will reduce size of install.wim by over 1 GB.
    ren F:\install.wim Enterprise.wim
    dism /export-image /sourceimagefile:F:\Enterprise.wim /sourceindex:1 /destinationimagefile:F:\Install.wim /compress:max
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  19. Enthousiast

    Enthousiast MDL Tester

    Oct 30, 2009
    47,233
    94,603
    450
    #360 Enthousiast, May 12, 2016
    Last edited: May 12, 2016
    You just rebuild the windows image after tinkering with it. I may hope someone who is removing stuff from the windows image has done that already (and he/she did rebuild the image according the "then rebuild image" text).

    Compressing the install.wim to install.esd (compress:recovery) will reduce the size significantly.

    ps, I don't get how a standard windows image which is lited (what this thread is about) can grow bigger than the original?