^^Only way to know this for sure is by actually installing & using ltsb2016 for few days.There may be no performance penalties,there may be negligible performance penalties or there may be performance penalties only with certain programs/games under certain conditions.
There are no performance penalties. The problem with LTSB 2016 is that the AMD drivers won't install at all, because they require a newer Windows version. Force-install of the drivers will result with a screen full of graphical glitches. In my Raven Ridge build, I ended up using the MSMG Toolkit to strip-down the latest Windows version available and using the PC with it, while waiting the end of the year for the new LTSC release. Nvidia drivers instead doesn't require a minimum Windows 10 version, they works in all Win10 versions, even Win7.
can you please share your soft- and hardware details, because I have a raven ridge test system (MSI B350M Mortar + R3 2200G) and I have no problems with the latest WHQL drivers (adrenalin 18.5.1) on LTSB 2016 (14393.2273). -andy-
Hmmmm I got a question - I'm using this 2016 and when 2018 is released will my 2016 be upgraded by MS Update or will I have to reinstall ? Thank you
LTSB can't be upgraded by MS update,you will have to download newer LTSB iso & then do a manual upgrade/install.
Maybe AMD followed nvidia example & released drivers with wddm 2.2 support(aka supported by older win 10 versions like ltsb2016).
I thought so whitestar_999 - Just thought I would ask as the only dumb question is the one that isn't asked
I'm using an Asus B350M-E with 2400G. Maybe the Vega 11 drivers are different than the Vega 8 (mostly confirmed when in April there was a driver update in Microsoft Update Catalog for Vega 8, but not for Vega 11).
Some feedback regarding the w10 LTSB 2016 June 2018 CU Update from WHDownloader… 1. Today I downloaded the WHDownloader kb4284880 / 14393 CU and Flash updates 2. I then used W10UI_4.7 to install same 3. I noticed that this kb4284880 was actually CU-2311 vs CU-2312 and confirmed this after installation and reboot using PC Settings / System / About 4. I then downloaded kb4284880 CU-2312 from Microsoft Update Catalog 5. I attempted to install kb4284880 CU-2312 using W10UI_4.7 but was informed that no update was needed 6. So, I manually installed kb4284880 CU-2312 from Microsoft Update Catalog 7. I confirmed after this installation and reboot using PC Settings / System / About this was in fact kb4284880 / 14393 CU- 2312
Did they publish 2 different CU's with the same kb nr for 14393 too? Else i don't get your post, i only see 1 new CU released May 12. 2018 on catalog. I see they, did, this is the one from WHD: Code: --------------------------- Checksum information --------------------------- Name: Windows10.0-KB4284880-x86.msu Size: 707974846 bytes (675 MB) CRC32: 75C7C217 CRC64: BD2776114423EDF0 SHA256: BFCF65559118122C6FCF58A36CCD9B124C8901A6ABF094F58C038CBFB5EFAD17 SHA1: 2BAA171E28BBC0CE4BEA7EF6439D423705195ED3 BLAKE2sp: 043A962BC1D1E2F320D46EEBBBF8167FD673A93C3B2A6356A4B2EB9303934F97 Code: <mum2:customInformation Dependency="Language Pack" Version="10.0.14393.2311" xmlns:mum2="urn:schemas-microsoft-com:asm.v3" /> This is the one from catalog: Code: --------------------------- Checksum information --------------------------- Name: windows10.0-kb4284880-x86_d76326a44c61704b741efdec2086f0ebcd151c3e.msu Size: 709021367 bytes (676 MB) CRC32: BF01541D CRC64: B318F22A3EECD71B SHA256: B0DFBEF7FF09EDBC57F631C50E3B35D93AC49F900109EB2774C5596DD02FD271 SHA1: D76326A44C61704B741EFDEC2086F0EBCD151C3E BLAKE2sp: 5D2E19C9B03A7A356AAA736851187422E1A0293C5015D0714C05E00EB95B4181 Code: <mum2:customInformation Dependency="Language Pack" Version="10.0.14393.2312" xmlns:mum2="urn:schemas-microsoft-com:asm.v3" />
This update won't install for me (error 0x800f0922). At restart it goes to 100%, then revert changes... Tried already: sfc, restorehealth, clean components, reset Windows update, reinstalling netfx 3.5 and 4. Appart from in-place reinstall, I'm out of clue. Also it seems automatic update is on now, probably because they updated Windows Update client, I was using murphy78's script. But anyway I use WFC with whitelist method so that doesn't affect me that much, otherwise it would be that kind of infinite loop. edit: Fixed...after investigating the cbs.log, problem was due to my app-readiness service being disabled.
Obviously LTSB wasn't programmed to fully utilize hardware that didn't even exist when it came out. Security and bug fixes only. Windows as a service does have advantages, if you want your system on the cutting edge instead of stability.
Are you sure? No hardware support fixes? Some people swear by LTSB as the best for gaming computers with new hardware.
Depends on your luck & hardware.e.g.nvidia always release their drivers with older win 10 versions like ltsb supported but amd didn't until now when they started releasing some drivers supported on ltsb(ryzen 2200g but not 2400g,don't know about mainstream gfx cards series).