I'm also running Win10 LTSB 2016 on an intel i3-8350K with Z370 chipset. Never had any problem. It's been stable since day one.
I work in Global Security and get contracted out quite a bit. The primary entity I work with runs a custom LTSB, based off 2016, but designed around our security protocols which basically omits all of Microsoft's default security features, too, so we deploy an even lighter LTSB version (Defender, telemetry, biometric and interactive components are all removed by default directly from Microsoft). Even that version I have never had any issues running it on any system I own, down to the most ridiculous virtual machines for testing you could imagine, so I'm inclined to say the problem people are having with LTSB lies between the computer and computer chair, not with the OS. LTSB is a fantastic OS; but like any OS, trying to "debloat" it (particularly with some popular tools around these parts) can definitely cause issues.
Oh yeah it's most definitely this that is my problem, thank you so much for telling me this. Of course it's me and my computer that are the problem, not LTSB which have worked perfectly before (why haven't I thought of this theory before?) Strange that I got problems with LTSB all of a sudden and not 1803, but hey if it's not the computer it's gotta be me right? I'm also really really happy for you that you never had any issues like EVER right? Must be feeling great knowing that you are faultless and every machine you have ever owned have been too and ALL OS's you have ever tried have also been faultless, like the secret special extra customized LTSB version directly from NSA and Microsoft you are using. Damn I'm feeling so relived now.
I would not be so quick to accuse people of being the only reason, when something's not working right.. there are many different hardware/software combinations that can cause anomalies. you just cannot be sure, without testing the system in question, for yourself. -andy-
I may be able to get w7 installed on coffee lake. If not i will try ltsb2016 N. If not i will try 1709 Home N then 1803 Home N if i have to. I have options. I would have thought simpler systems give less grief.
I don't recommend the "N" version of LTSB because it's quite buggy, better install normal LTSB and remove Windows Media Player manually in Control Panel --> Programs and Features --> Turn Windows features on or off. You can also enable DirectPlay and .NET Framework 3.5 there.
I havnt met an os yet that isnt buggy to some degree. It depends where the bugs are and how they affect you. You forgot the part where i should lift the toilet seat before i piss.
ltsb 2016 n does not officially support coffee lake cpus as it supports up to kaby lake (and no higher). need upcoming ltsb/ltsc 2018/2019 n version for official coffee lake cpu support
When certain users come and say how awesomely good everything works for them and starts to say that the problems people have is either their computers or the people themselves and have no intent giving helpful advice that's where I draw the line frankly. Like AndyMutz said there is many different hardware/software combinations that can cause anomalies. LTSB 2016 1607 doesn't work well on my new machine for some reason but 1803 Enterprise does, how and why that is so I can't explain. The cheer arrogance is overwhelming, like "Duh it's not LTSB 2016 that's wrong, it's either your computer or you behind it" Stuff like that makes me bitchy right away.
AndyMutz - post no 71 "I have an i5-8400/B360 system running with LTSB 2016 and all is working perfectly fine. Leolo has also got it running on coffee lake.
Man wearing a hoodie in a dark corner of an alley "Psst,hey you there!wanna buy a $10000 rolex watch for 100 bucks.Just picked it lying on the road & need quick money". Standard reply "f*** off". Popular online forum "Hey you all I am using a super optimized secretly modified win 10 version with zero telemetry which works on all hardware". Standard reply "oooh can I get one too pretty please". Decide for yourselves.