Updated the 1809 Updates Overview (17663.1294): https://forums.mydigitallife.net/th...-17763-xxx-pc-rs5.77945/page-216#post-1490183
So you would recommend 2016 LTSB over 2019 LTSC? Do you know the main performance differences other than services? I know LTSC 2019 has the dark mode system wide, and cortona separate. I just want a build version where the privacy was the best, would that be 2016 LTSB? I want to also use MSMG Toolkit to remove more stuff.
I wouldn't. one big reason is the recent CUs for LTSB 2016 (v1607) are huge and take almost an hour or two to install (the x64 CUs are about 1.5Gb or 1.6Gb) recent CUs for LTSC 2019 (v1809) take a little less time to install and are much smaller
on a 15W mobile CPU maybe. I still use LTSB 2016 on my main system (i9-9900K) and it takes around 10 minutes to completely install a CU. -andy-
Yea but in LTSC 2016 they had cortona seperate from the start menu and taskbar not like LTSC 2019. Makes Privacy more better.
I don't understand many of the acronyms in the first page. Anyway, I'd like to know which is the easiest method for integrating all the needed updates into an ISO of W10 Enterprise 2019 LTSC.
Too much stuff I don't know what is, I guess I'll simply install updates manually. Just for confirmation, can I grab the March ISO or I have to go through all this process to generate a February ISO?
I have a weird bug... I'm following this guide, but when I use svfx.exe, it just cannot see any .iso files in the folder. :/
Can you specify what iso and svf patch you are using (full filenames), so we can verify if you have the correct ones?
Nerver mind, it was the wrong .sfv file preventing the program to see .iso files. Anyway, could you please answer to my previous question about why we go through all this process to generate an ISO which is dated to February 2019 instead of using the ready one from March 2019?
There is no Enterprise LTSC ISO released after the one from feb 2019, 17763.316 is the latest one. The 17763.316 ISO = compiled march 6. but is updated with the feb CU. ps, when you had opted for the re-release 17763.107 LTSC ISO, you only had to download the 17763.107 EVAL LTSC source ISO and the svfsfx exe patch in the desired language and ran the patch next to the eval source iso
I opted for 17763.316 actually, so I patched two times following your guide. Anyway, isn't this ISO dated 15 March? Ok, I just noticed that going through your process actually generated the same exact ISO that was available for download in that post. lol
Here is the content and checksums of the 17763.316 Enterprise 2019 LTSC ISOs: https://forums.mydigitallife.net/th...prise-n-ltsc-2019.76325/page-164#post-1508318 Check the date of integration of the updates by MSFT. Yes, @LostED mirrors the en-US ISOs too.
He also mirrors other languages, I could find mine there directly, and checksum is correct. Anyway, can I use abbodi1406 tool for integrating updates on W7? In his post he says "Recommended Host OS: Windows 8.1 or later".