[DISCUSSION] Windows 10 Enterprise (N) LTSC 2019

Discussion in 'Windows 10' started by Tito, Feb 1, 2018.

  1. batmann

    batmann MDL Novice

    Dec 26, 2019
    18
    2
    0
    I'm on Win 7 Enterprise now. With a click of a mouse I can change my language. I think I've downloaded some languages packs in the old days.

    Isn't the same with Win 10 LTSC? Once I install a language version, the OS will always remain in that language and it cannot be changed anymore?

    Thanks for letting me understand this
     
  2. Enthousiast

    Enthousiast MDL Tester

    Oct 30, 2009
    47,233
    94,613
    450
  3. batmann

    batmann MDL Novice

    Dec 26, 2019
    18
    2
    0
    I'm downloading the 3 files you suggested me, but I'm not sure I will be able to create the language LTSC ISO after this. I really don't know how to do this. Can't I simply use the en-US only ISO, and then download the language pack later, like it works on WIN 7 ?

    Anyway the last link you shared doesn't seem to work. The google drive where should be stored the file "en_windows_10_enterprise_ltsc_2019_x64_dvd_5795bb03.iso " dosen't work. I'm getting a 404 page. Am I missing something?

    Thanks again
     
  4. batmann

    batmann MDL Novice

    Dec 26, 2019
    18
    2
    0
    I found the en-US file on a mirror. So, with the en-US file, I do not have to create the LTSC ISO with the toolpack, correct? I just need to put the ISO on a USB drive and make the fresh installation from the USB drive.

    Is this correct? If yes, any suggestion in how to do this?

    I will be able to install languages pack later? If yes, this seems the easiest thing for me. As said, I'm a complete newbie about this and would like to keep things as simple as possible.

    Thanks!
     
  5. Enthousiast

    Enthousiast MDL Tester

    Oct 30, 2009
    47,233
    94,613
    450
    No offense, but why do people who can't do simple things as putting 3 files in the same folder (or just 2 when en-US is wanted) and run a bat even want to install windows and specifically Enterprise 2019 LTSC?

    All questions, no basic knowledge at all, why not just go for it and learn by trial and error, like i did myself (in VMs and on real systems).

    I really wonder:)
     
  6. batmann

    batmann MDL Novice

    Dec 26, 2019
    18
    2
    0
    - want to install LTSC version because it's a much cleaner system than PRO (lot less useless things installed, more control on updates, and many other things). I'm updating from win 7 just because it will not get security updates anymore. So, LTSC version seems the closest OS to win 7.

    - I've never runned a bat file. I don't even know what is it. I'm trying downloading it, but the file on Megaupload is not downloadable. It keeps saying "temporary error".
     
  7. pfeldman

    pfeldman MDL Novice

    Jul 7, 2010
    7
    1
    0
    Hi,
    Sorry for being an idiot, but how do I do an inplace upgrade keeping files and apps from Enterprise N 2016 LTSB to Enterprise N 2019 LTSC using this

    SW_DVD5_WIN_ENT_LTSC_2019_64-bit_English_International_MLF_X21-96427.ISO

    ISO started from setup.exe in WIndows 10 2016 LTSB on the USB stick ?

    Posts in this thread say that this ISO contains both editions 'EnterpriseS' and 'EnterpriseSN', but it refuses to migrate apps because it says the editions are different.

    Which means that the dual-edition 2019 ISO can't upgrade N editions keeping files and apps ?

    That sucks.

    I see no SVFs for turning this ISO into an N-only edition that I used for 2016 LTSB

    I can fool setup.exe by making registry changes

    1. Open regedit.exe and navigate to HKLM\Software\Microsoft\Windows NT\CurrentVersion
    2. Change ProductName to Windows 10 Enterprise 2016 LTSB
    3. Change EditionID to EnterpriseS
    4. Navigate now to HKLM\Software\Wow6432Node\Microsoft\Windows NT\CurrentVersion
    5. Change ProductName to Windows 10 Enterprise 2016 LTSB
    6. Change EditionID to EnterpriseS

    but there are a *lot* of registry entries and Windows system files that have references to EnterpriseSN rather than EnterpriseS, like

    [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\PackageIndex\Product]
    "Microsoft-Windows-EnterpriseSNEdition~31bf3856ad364e35~amd64~~10.0.14393.0"=dword:00000000

    or

    [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\Packages\Microsoft-Windows-Branding-EnterpriseSN-Package~31bf3856ad364e35~amd64~~10.0.14393.0]
    "InstallClient"="DISM Package Manager Provider"
    "InstallName"="Microsoft-Windows-Branding-EnterpriseSN-Package~31bf3856ad364e35~amd64~~10.0.14393.0.mum"
    "InstallLocation"="\\\\?\\d:\\rs1.bin.amd64fre.dep\\mergedcomponents\\images\\client\\packages\\"
    "CurrentState"=dword:00000070
    "SelfUpdate"=dword:00000000
    "Visibility"=dword:00000002
    "InstallTimeHigh"=dword:01d1dfb5
    "InstallTimeLow"=dword:66647756
    "InstallUser"="S-1-5-18"

    [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\Packages\Microsoft-Windows-Branding-EnterpriseSN-Package~31bf3856ad364e35~amd64~~10.0.14393.0\Owners]
    "Microsoft-Windows-EnterpriseSNEdition~31bf3856ad364e35~amd64~~10.0.14393.0"=dword:00030070



    so I worry that I will completely trash my registry and system folder if I try to force setup.exe to run this way.

    Is there a way ?
     
  8. Enthousiast

    Enthousiast MDL Tester

    Oct 30, 2009
    47,233
    94,613
    450
    17763.107 (the build of your vlsc iso) doesn't contain N versions, download build 17763.316 and it will contain N versions and you should be able to upgrade without issues with keeping all files.
     
  9. Enthousiast

    Enthousiast MDL Tester

    Oct 30, 2009
    47,233
    94,613
    450
    Did you really look at the ISO filenames?
     
  10. pfeldman

    pfeldman MDL Novice

    Jul 7, 2010
    7
    1
    0
    wow - so many thanks - I would never have known that
     
  11. batmann

    batmann MDL Novice

    Dec 26, 2019
    18
    2
    0
    What you mean? Yes, I have 2 new big files after batching. One is named ".....consumer_edition_version_1809_updated_feb_2019_x64_dvd_d512df64" and the other is named "....enterprise_ltsc_2019_x64_dvd_e8629a2f".

    So, which one is the correct one to use?
     
  12. Enthousiast

    Enthousiast MDL Tester

    Oct 30, 2009
    47,233
    94,613
    450
    You wanted LTSC, so carefully look at the 2 ISOs again;)

    One of them has:
    in.
     
  13. batmann

    batmann MDL Novice

    Dec 26, 2019
    18
    2
    0
    I suspected that one was the correct version. Still, as a newbie, I find a little confusing that after doing the batching, you get 2 new files, one of which seems to be useless. n any case, it seems I made it in the end. Now:

    - how to check the checksum, to be sure that the file is good, not corrupted and so on?

    - with this ISO (that now contains the new language), I can still choose to install the OS in en-US during the installation? Or I'm forced to go with the new language now? Actually I need English language on a computer, and the other language on another computer. So, if I can choose both languages during the installation process, everything seems perfect.

    - how to create a USB bootable pen drive with this file?

    Thanks again!
     
  14. Enthousiast

    Enthousiast MDL Tester

    Oct 30, 2009
    47,233
    94,613
    450
    Because of what i explained earlier, the svf way (by @GezoeSloog) is en-US source iso (consumer) > desired language consumer svf patch (language not once mentioned by you all evening) > LTSC svf patch in that language.

    https://forums.mydigitallife.net/th...prise-n-ltsc-2019.76325/page-164#post-1508318

    No, it's in the language of the created ISO.

    - Format the USB FAT32 and extract the ISO to its root
    - or use Rufus
     
  15. batmann

    batmann MDL Novice

    Dec 26, 2019
    18
    2
    0
    https://forums.mydigitallife.net/th...prise-n-ltsc-2019.76325/page-164#post-1508318

    I've checked them and they seem ok. For the en-US language version I got more parameters to check, for the language pack ISO it seems to exists only SHA-1 checksum.....


    No, it's in the language of the created ISO.

    So, for the PC I want to install the OS with the en-US language, I need to use this version " en_windows_10_enterprise_ltsc_2019_x64_dvd_5795bb03 " that I downloaded from the other link? without batching, correct (the file is already ready to be imported into an USB drive with a program like Rufus)?


    - Format the USB FAT32 and extract the ISO to its root
    - or use Rufus[/QUOTE]

    I'll check how to use Rufus, I hope it will be easy.... thanks.
     
  16. Enthousiast

    Enthousiast MDL Tester

    Oct 30, 2009
    47,233
    94,613
    450
    Yes, MSFT still provides SHA-1 on MVS and en-US is on that list too, the other checksums are posted by me, after running the 7zip checksum tool on them.