LTSC 2019 running on a 12 year old Dell laptop with 1.5 gb RAM and AMD Mobile Sempron processor. Works very well. I tried 64-bit but even though it got mostly through the install, it couldn't set up all the devices. 32-bit installed great. I upgraded from LTSB 2016. I disabled Windows Management Instrumentation during the upgrade to overcome any memory issues. This was just a "what if?" experiment.
KMS38 as mentioned in previous posts. Ironically in 20 years time Windows 10 will be long gone dead and buried! all credit to s1ave77 magician extraordinaire!
CodyQX4's Mstoolkit 2.6.4 with TAP selected also works fine for KMS https://forums.mydigitallife.net/th...al-kms-solution-for-microsoft-products.28669/
The refresh is 17763.107. The base was 17763.1, so the only difference is, the refresh iso has an older CU integrated, the current publicly offered CU is 17763.134 and the current CU in ReleasePreview ring is for 17763.165.
I downloaded the LTSC as soon as it was released. But there was all that mess about the October release and its bugs. Do I need to download a new iso for LTSC or I can just keep updating the one I'm using with Windows Update?
This version doesn't know how to get language package components Sorry, I've found it. Look at the results after the test https://forums.mydigitallife.net/th...prise-n-ltsc-2019.76325/page-111#post-1483328
until ms will fix this app association bugs, im staying out of all 1809/2019 branch among a lot of other bugs, this is basic ridiculous.
Iirc that bug is also reported on 1803 systems . Bug isn't present on my desktop and notebook running 17763.165.
This is reasonable and any responsible person would recommend for using productive systems....(I would not upgrade from LTSB2016 yet.) The insider program has utterly failed again since 1511....people reported the bugs but M$ did not care about. To wait is reasonable.