Discussion in 'Windows 10' started by Tito, Jul 21, 2016.
If you mean the "Update History" website, that is a listing of all previously released updates.
So the ones in WHD contain 100% all previous ones that were already released?
Yes, for over 3 years now.
Sorry, I didn't realise. MS has a really crappy system for naming and explaining things.
It's pretty common knowledge after 3 years
Hello everyone, well I unfortunately needed to upgrade to W10 Enterprise N 2016 LTSB because the previous compilation did not allow me to add more features, I made it forced because although it is an old compilation it never gave me problems just joys never "won" any bsod or locking system I believe it was one of my best installs I've ever done of Windows 10 so it's ball forward and I know I'm safe because the 1607 build is a charm (after a few tweaks)
Edit: thanks a lot for Instal.Tweak.exe works like one candy
You need to login to view this posts content.
How is that exactly?
Windows 10 LTSB 2016 installs and runs fine on an AMD Ryzen chip, drivers install without a problem. Ignore the complete and utter garbage written on this subject a few pages back.
What Ryzen? 1st gen? 2nd gen? APU or CPU?
AMD Ryzen 3 2200G 3.7GHz turbo CPU. It doesn’t matter really, none of them appear on the official MS compatibility list and all the chips were released after LTSB 2016.
I, too, have a test system with a B350 mobo and a 2200G CPU.
no problems at all with LTSB 2016
i see the new photoshop cc cant be installed on builds 1511 > 1607. it tells me to upgrade when i attemt to install it.
i have build 1607. is that the newest build??
LTSC is 1809
Oh I'll see if I can hunt down a iso and upgrade.
I am running LTSB 2016 on a Threadripper 1950X, no issues at all - performance and benchmarks are just as with Win 10 1709 (just did a test with a new Win 10 build to confirm that), actually even a little faster as LTSB 2016 has less crap running in the background. Additionally I´ve "NTLited" it to the extreme (preset is attached in case someone wants it, but take note that this basically only leaves the kernel + network working, haha. Also make sure to use it only on the 14393.0, install it and then let Windows Update download the CU´s - direct integration is not working via NTLite as MS f**ked up something with the 2018-05 CU which needs to be installed first on a live machine, but don´t worry, CU´s work fine with my preset and without any errors). Think I will stick to it until it "expires" support-wise in 2026
Question about CBB version. Is it possible to activate installed LTSB version with CBB key?
I have not found any iso of the Enterprise IoT CBB version available for download.
LTSB 2016 users:
Current updates for .14393 aka 1607 (LTSB 2016)
As of 2018/11/27
kb4467684 Cumulative Update 2018/11/27 [CU .2639]
kb4465659 Servicing Stack Update 2018/11/13
kb4132216 Servicing Stack 2018/05/21
kb4477029 Flash update 2018/11/20
kb4054590 .NET-4.7.2 2018/07/12
i have an issue integrating the latest kb4467684 Cumulative Update 2018/11/27 [CU .2639] offline in the install.wim by using dism command line, the CU doesn't get integrated.
Tried to install on a live 14393.0 and i receive a pop-up saying the update is not applicable!? What's going on??
thanks in advance