@Enthousiast Then i have no clue since i have only default us-US also, and the autounattend.xml is set to "InputLocale>0413:00020409</InputLocale>" Maybe i have to try from the 17763.1 instead.
after thinkering about it, my guess it is that ïnputlocale" setting in the xml, i'll report back later on It's so nice, a lazy install edit: same thing..it keeps installing the dutch typing/dutch optical character recognition and reinstalling the latest CU.
Server LTSC channel builds are but there are also Server SAC builds that contain only Core editions (No Desktop Experience).
@Enthousiast Have you ever experienced this? Never happened to me on Pro or Pro for WS. I would format, install Windows 10 LTSC 2019, enter my product key in settings. Do a phone activation. Then randomly if I go to PC Settings, it would say at the bottom "not activated" then it goes away after I right click on Computer then go to system properties where it does say it's activated. Also yesterday I restored back an image which I took where Windows WAS activated, but just because I changed to a different mouse it said not activated. I got tired of this BS as the phone activation of Microsoft is horrendous, you need to press many digits in the IVR system just to get to an agent and then giving them the codes and what not takes ages.
A noob here. I've a Win10 LTSC 1809 iso. name: SW_DVD5_WIN_ENT_LTSC_2019_64-bit_English_MLF_X21-96425.iso SHA1 hash: d5b2f95e3dd658517fe7c14df4f36de633ca4845 I've some questions about it: 1) After going through a number of threads, I realised its not a MSDN version but a VLSC version. I don't know what that means, are vlsc isos official? 2) Can somebody please tell me which version of MSDN it corresponds to? Is it the February 2019 refresh? The LTSC 180917763.316 version? 3)I've verified the hash from one or two places, but have my reservations. Can somebody point me to a thread that has VLSC iso hash dumps, like this forum has for MSDN versions
Exactly the same ISO was also published on MSDN with that filename: Code: d5b2f95e3dd658517fe7c14df4f36de633ca4845 *en_windows_10_enterprise_ltsc_2019_x64_dvd_be3c8ffb.iso Microsoft messed something up with the filenames, so @Enthousiast decided to use VLSC filenames. They are official, from the (Microsoft) Volume Licensing Center. It's 17763.107, the re-release of 1809. We don't have VLSC dumps, only older VLSC catalogs. The latest if from October 2018, until Microsoft stopped publishing it: [Update] VLSC Catalog Edit: The VLSC catalogs don't include any hashes.
Hi, sorry for the noob question but what is the difference between the Re-Release ISO and the Feb 2019 ISO?
Build 17763.107 (Re-release) Nov 2018 (No N Version) Build 17763.316 (Refresh) Updated Feb 2019 (Latest)
All new 1809 (17763.1282) updates: https://forums.mydigitallife.net/threads/windows-10-hotfix-repository.57050/page-500#post-1601889
So I am running a Windows 10 Enterprise LTSB installation and it works just fine. But I wonder...Is there a good reason for me to install LTSC instead? Also, can I just upgrade to LTSC from LTSB? or Do I have to do a fresh LTSC installation?.
