The EVAL iso is the source iso for the target iso, so the svf patch extracts the target iso from the source iso, creating the non EVAL original MVS/VLSC iso.
So, what are the major differences between LTSC and 1607 LTSB if any? Figured i be on 1607 for a good many more years, but just curious.
LTSC is based on 1809, so if there's a reason you need 1809, upgrade to LTSC. Otherwise, stick with LTSB 2016.
Whether you need (not want) LTSB or LTSC depends mainly on the used hardware, that's the only factual reason to eventually need (not want) the new LTSC release, LTSB won't support new hardware, all other reasons are personal.
Sorry, can you elaborate more on this in detail? I'm interested and would like to know more about it. Thanks! Which apps? From the app store? I won't be using the appstore, maybe in the future for Forza Horizon.
https://forums.mydigitallife.net/th...e-activation-patch.56395/page-29#post-1484543 https://forums.mydigitallife.net/th...e-activation-patch.56395/page-29#post-1484555 https://forums.mydigitallife.net/threads/how-to-decrypt-knowngamelist-bin-file.78856/#post-1498189 Mostly for some AV...They want to sell you Server/Business version when it exists, obviously. but wiyh a bit of knowledge you can overcome this. Those LTSC editions (Enterprise LTSC/Server 2019) don' t come with store anyway, but it can be installed though... Server is more intended for specific usage, not general usage...if you want a bit of that and a bit of this, and maybe a bit of that and this in the future...you better go with Windows 10 Pro and save you the hassle in the future.
@chblock At least with LTSB/C you wont be getting new "features" every 6 months(designed by silly social media junkies) just regular bug fixes etc. I treat every new build like a new os, what worked with the old may not work with the new and i want a stable os/pc, not something so damn fragile it makes Mr Glass look like hes made from titanium for crying out loud. This stupid self imposed rule of a major update every 6 months is just plain stupid, developers and enthousiats must be having a hell of a time playing whack a mole every 6 months. Trouble is you got to use whatever your hardware supports, i tried to get a display driver for my i3 8300 and the driver only supported 1703(9?) upwards so completely putting the kibosh on LTSB without a graphics card.
I think the new version every six months thing is crazy too, but who am I so say really. I'm just really happy I have the choice with LTSC. Plus you get the benefit of less add-ons. If it were the world according to chblock, everything in Windows would be modular with the user's or admin's choice to include or not in the install.
Officially you dont have a choice with LTSB/C because of their licensing but ms know people are using them. LTSB 1607 is a bit slimmer than regular 1607 but not by much, its the not getting new crap, cough cough, i mean features every 6 damn months that makes it attractive. .
Well, yeah, officially I'm not using LTSC 2019, I'm using Win10 Home, blech. Unofficially, thanks to this forum, I have a choice. The guys that support this forum are my heros.
Can someone help me solve a problem I'm having with the en-gb language during USB installation? I'm using svf2iso GUI to download the required O.S, In this case it's 17763.107.101029-1455.rs5_release_svc_refresh_CLIENT_LTSC_EVAL_x64FRE_en-us.iso tool creates SW_DVD5_WIN_ENT_LTSC_2019_64-bit_English_International_MLF_X21-96427.iso SW_DVD5_WIN_ENT_LTSC_2019_64-bit_English_International_MLF_X21-96427.svf However every time I install via USB I get windows prompts wanting to verify the already assigned language & the install fails because the language,kb language layout etc is not working? I also tried deleting the SW_DVD5_WIN_ENT_LTSC_2019_64-bit_English_International_MLF_X21-96427.iso & re-building adding the svf name: SW_DVD5_WIN_ENT_LTSC_2019_64-bit_English_International_MLF_X21-96427.svf and adding the source name: 17763.107.101029-1455.rs5_release_svc_refresh_CLIENT_LTSC_EVAL_x64FRE_en-us.iso which successfully creates the SW_DVD5_WIN_ENT_LTSC_2019_64-bit_English_International_MLF_X21-96427.iso image again for transfer to USB. Here is the log, 13:33:34 CHECKING MVS PREREQUISITES 13:33:34 +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ 13:33:34 Language: en-gb 13:33:34 ISO Name: SW_DVD5_WIN_ENT_LTSC_2019_64-bit_English_International_MLF_X21-96427 13:33:34 ISO Hash: dad202319f78e8e0549966eaf8e57d54b1e7cb8f 13:33:34 EVAL Name: 17763.107.101029-1455.rs5_release_svc_refresh_CLIENT_LTSC_EVAL_x64FRE_en-us 13:33:34 EVAL Hash: 369e645a197bc2ca8309cb80467a85a16eacd1a7 13:33:34 +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ 13:33:57 CREATING MVS ISO 13:33:57 +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ 13:33:57 Language: en-gb 13:33:57 ISO Name: SW_DVD5_WIN_ENT_LTSC_2019_64-bit_English_International_MLF_X21-96427 13:33:57 ISO Hash: dad202319f78e8e0549966eaf8e57d54b1e7cb8f 13:33:57 EVAL Name: 17763.107.101029-1455.rs5_release_svc_refresh_CLIENT_LTSC_EVAL_x64FRE_en-us 13:33:57 EVAL Hash: 369e645a197bc2ca8309cb80467a85a16eacd1a7 13:33:57 +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ 13:33:57 Downloading EVAL ISO... 16:08:15 EVAL ISO exists. 16:08:15 Checking hash... 16:09:45 Check Hash: 369e645a197bc2ca8309cb80467a85a16eacd1a7 | SUCCESS! 16:09:45 Downloading Target SVF... 16:09:45 SVF Name: SW_DVD5_WIN_ENT_LTSC_2019_64-bit_English_International_MLF_X21-96427 16:17:51 Creating Target ISO... 16:25:35 Target ISO exists. 16:25:35 Checking hash... 16:27:21 Check Hash: dad202319f78e8e0549966eaf8e57d54b1e7cb8f | SUCCESS! 16:27:21 +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ What's strange is I can get this to install fine on an Intel 7th Gen laptop using rufus-3.4 GPT partition scheme, however when trying to install on my older laptop which already has Win10 LTSB 2015 I have to use the MBR partition scheme for older Bios-es, installation works this way until it gets to the language part of installing, even though English Language/Keyboard etc is already shown in the language list as default which proves svf2iso made the conversion correct,yet the install still fails, Any idea's? OOBEKEYBOARD OOBEZDP OOBEISPS are some of the install errors that arise.
The tool has nothing to do with installation errors, as long as the target iso's checksums match, the tool did its job properly. Stop using 3rd party tools, just format the USB FAT32 and extract the LTSC iso to it's root and it will be able to boot in all scenarios. The OOBExxxxxx errors occur sometimes for me too (OOBEREGION for me and mainly with IP builds and always in VM's). When i directly re-installed it always worked.
The reason why I came here was to avoid Pro lol, there's no way I'm using that Virus version. I know what LTSC and Server is, and that's why i want it. But I don't know how to activate and disable things in the OS