Jump to content
IGNORED

Overview of Upcoming Windows Versions for Music Servers


Recommended Posts

Since both Windows 10 Enterprise LTSC 2021 and Windows 11 21H2 should be coming soon, let's take a look at what to be expected in the (near) future.

 

(Previously another thread about LTSC was also created on this forum, therefore I'd like to stick with the same forum as well.)

 

 

First of all, basically "plain vanilla" LTSC and IoT Enterprise LTSC should be identical to each other while the only difference should be the licensing terms etc.

 

https://docs.microsoft.com/en-us/windows/iot/iot-enterprise/getting_started

Quote

Windows 10 IoT Enterprise shares all the benefits of the worldwide Windows ecosystem. It is a binary equivalent to Windows 10 Enterprise, so you can use the same familiar development and management tools as client PCs and laptops.

 

Windows 10 Enterprise LTSC - What's new in Windows

https://docs.microsoft.com/en-us/windows/whats-new/ltsc/

 

What's new in Windows 10 Enterprise LTSC 2015

https://docs.microsoft.com/en-us/windows/whats-new/ltsc/whats-new-windows-10-2015

 

What's new in Windows 10 Enterprise LTSC 2016

https://docs.microsoft.com/en-us/windows/whats-new/ltsc/whats-new-windows-10-2016

 

What's new in Windows 10 Enterprise LTSC 2019

https://docs.microsoft.com/en-us/windows/whats-new/ltsc/whats-new-windows-10-2019

 

Upcoming Windows 10 and Office Long Term Servicing Channel (LTSC) releases - Microsoft Lifecycle

https://docs.microsoft.com/en-us/lifecycle/announcements/windows-office-ltsc-releases

 

LTSC: What is it, and when should it be used?

https://techcommunity.microsoft.com/t5/windows-it-pro-blog/ltsc-what-is-it-and-when-should-it-be-used/ba-p/293181

 

The next Windows 10 Long Term Servicing Channel (LTSC) release

https://techcommunity.microsoft.com/t5/windows-it-pro-blog/the-next-windows-10-long-term-servicing-channel-ltsc-release/ba-p/2147232

 

Windows lifecycle and servicing update

https://techcommunity.microsoft.com/t5/windows-it-pro-blog/windows-lifecycle-and-servicing-update/ba-p/2493043

 

Windows IoT support lifecycle and upcoming releases

https://techcommunity.microsoft.com/t5/internet-of-things/windows-iot-support-lifecycle-and-upcoming-releases/ba-p/2511888

 

Introducing the next feature update to Windows 10: 21H2

https://blogs.windows.com/windowsexperience/2021/07/15/introducing-the-next-feature-update-to-windows-10-21h2/

 

Licensing & Usage

https://docs.microsoft.com/en-us/windows/iot/iot-enterprise/commercialization/licensing

 

Search Product and Services Lifecycle Information

https://docs.microsoft.com/en-us/lifecycle/products/?terms=Windows 10 IoT Enterprise

 

What is Windows IoT Enterprise LTSC 2021? | Microsoft

https://www.arrow.com/ais/msembedded/resource/blog/what-is-windows-iot-enterprise-ltsc-2021

 

What’s New in Windows 10 IoT Enterprise LTSC 2021 - Embedded Computing Design

https://www.embeddedcomputing.com/technology/software-and-os/os-filesystems-libraries/whats-new-in-windows-10-iot-enterprise-ltsc-2021

 


 

And then here's why we're going for that particular version of Windows 10 in the first place

 

https://www.whatsbestforum.com/threads/taiko-audio-sgm-extreme-the-crème-de-la-crème.27433/page-81#post-609990

Quote

2) The noise signature of OS has a huge influence over the sound that comes out from the system. Windows LTSC is the clear leader in Emile's testing, and the gap between the latest from Microsoft and the different flavors of Linux can only be expected to increase in the future. When Microsoft delivers a better kernal and scheduler, Emile for sure will build an updated OS from these new components. So the OS is absolutely future obsolescence proof for many years to come

 

https://www.whatsbestforum.com/threads/taiko-audio-sgm-extreme-the-crème-de-la-crème.27433/page-141#post-628443

Quote

c) That's a lot of trial and error, we do take a different approach, we start out with Windows 10 IoT Enterprise LTSC which is a stripped down version of Windows for devices requiring stable performance over time, like cash registers, industrial appliances etc. It is only available to OEM system builders. This is actually a lighter weight system then Windows Server "out of the box", but we do subsequently modify it, this is quite common for OEM system builders and there are a wide range of tools available to do so. A lof of components we do not need for music playback cannot be removed or disabled after Windows has been installed, so we remove them from the installation media before they are installed. Do be prepared to allocate considerable time before attempting this yourself as removing something can lead to all sorts of unpredictable results. Our current software installation probably took hundreds of reinstalls to get where we are now. A faster way is to look around on GitHub, where several people have shared scripts to create a stripped windows installation media, do read the feedback first if these are operating reliably.

 

https://www.whatsbestforum.com/threads/taiko-audio-sgm-extreme-the-crème-de-la-crème.27433/page-206

Quote

Emile, which license do you use for the Windows 10 Enterprise LTSC? Is it the “Windows 10 IoT Enterprise 2019 LTSC High-End?”

 

Quote

We have an OEM volume license with a slightly different description but I expect the software itself to be similar if not the same.

 


 

(I certainly don't recommend anyone to install this "Xtreme LiteOS 11" stuff for obvious reasons, we could end up losing the shirt or something if they're throwing malware / ransomware etc. into the mix.)

 

So I'm just talking about this (unofficial for sure) Xtreme LiteOS 11 as a proof of concept, apparently its footprint should be quite impressive to say the least

  • Superlite = just under 4.8GB
  • Barebone = just under 4.5GB

Even the CPU usage turned out to be significantly lower as shown below

 

 

So how do we do it then? We could either pay for NTLite or just use some freebies instead

 

https://audiophilestyle.com/forums/topic/58164-building-a-diy-music-server/page/72/?tab=comments#comment-1107878  

On 2/7/2021 at 11:15 PM, Nenon said:

Windows LTSC Guide

I have been putting some notes on this but haven't worked actively. I wanted to get the new chassis first, so I can start from scratch and document everything I do that makes a positive difference. I don't want to make any changes to my Windows, especially while using it to voice the power supply. 

 

https://www.ntlite.com/download/

https://www.ntlite.com/tutorial-for-creating-and-testing-a-700mb-windows-10-iso/

 

https://github.com/Sycnex/Windows10Debloater

 

https://github.com/DrEmpiricism/Optimize-Offline

 

https://github.com/LeDragoX/Win10SmartDebloat

 

https://github.com/W4RH4WK/Debloat-Windows-10

 

https://github.com/farag2/Windows-10-Sophia-Script

 

https://www.winreducer.net/winreducer-ex-100.html

 

https://freetimetech.com/windows-10-clean-up-debloat-tool-by-ftt/

 

https://mega.nz/file/JgNHzKyI#8z9GZ2TM2OtYlG4xcCmrz6aPnVeUKt_so__3h2WVwk0

 

(All of them should be able to support Windows 10 while YMMV with Windows 11.)

 


 

Now where do we get the latest build of Windows 11 since it ain't really going RTM yet? The semi-official way is called UUP (Unified Update Platform) as mentioned below

 

https://docs.microsoft.com/en-us/mem/configmgr/sum/deploy-use/uup-preview

https://docs.microsoft.com/en-us/windows/deployment/update/windows-update-overview

https://blogs.windows.com/windows-insider/2016/11/03/introducing-unified-update-platform-uup/

https://techcommunity.microsoft.com/t5/hybrid-work/managing-quality-updates-via-windows-update-for-business/m-p/1498601

https://techcommunity.microsoft.com/t5/windows-it-pro-blog/migrating-and-acquiring-windows-10-optional-content/ba-p/1698234

 

Personally I don't feel like going through all that technical stuff about UUP but IMHO it's still necessary to show that we're actually downloading those files from Microsoft

 

https://docs.microsoft.com/en-us/windows-server/administration/windows-server-update-services/deploy/2-configure-wsus

Quote

 

Let's ping that server uupdump.sf.tlu.dl.delivery.mp.microsoft.com

 

C:\>ping -n 1 uupdump.sf.tlu.dl.delivery.mp.microsoft.com

Pinging sni1gl.wpc.nucdn.net [152.199.39.108] with 32 bytes of data:
Reply from 152.199.39.108: bytes=32 time=37ms TTL=57

Ping statistics for 152.199.39.108:
    Packets: Sent = 1, Received = 1, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 37ms, Maximum = 37ms, Average = 37ms

 

And then ping sni1gl.wpc.nucdn.net

 

C:\>ping -n 1 sni1gl.wpc.nucdn.net

Pinging sni1gl.wpc.nucdn.net [152.199.39.108] with 32 bytes of data:
Reply from 152.199.39.108: bytes=32 time=36ms TTL=57

Ping statistics for 152.199.39.108:
    Packets: Sent = 1, Received = 1, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 36ms, Maximum = 36ms, Average = 36ms

 

Both of them were returning the same pair of matching IP addresses, though most likely you'll get a different pair on your side since that's gonna be based on your own physical location.

 

sni1gl.wpc.nucdn.net could also be found here

 

https://microsoft.com.ipaddress.com/azurecdn-licensing.microsoft.com

https://microsoft.com.ipaddress.com/msedge.sf.dl.delivery.mp.microsoft.com

https://microsoft.com.ipaddress.com/uupdump.sf.tlu.dl.delivery.mp.microsoft.com

 

nslookup uupdump.sf.tlu.dl.delivery.mp.microsoft.com

 

https://www.nslookup.io/dns-records/uupdump.sf.tlu.dl.delivery.mp.microsoft.com

Name:    sni1gl.wpc.nucdn.net
Addresses:  2606:2800:247:1cb7:261b:1f9c:2074:3c
          152.199.39.108
Aliases:  uupdump.sf.tlu.dl.delivery.mp.microsoft.com
          2-01-3cf7-0024.cdx.cedexis.net
          wildcardtlu-ssl.azureedge.net
          wildcardtlu-ssl.ec.azureedge.net
          scdn1f005.wpc.ad629.nucdn.net

 

nslookup sni1gl.wpc.nucdn.net

 

https://www.nslookup.io/dns-records/sni1gl.wpc.nucdn.net

Name:    sni1gl.wpc.nucdn.net
Addresses:  2606:2800:247:1cb7:261b:1f9c:2074:3c
          152.199.39.108

 

I hope that's more than enough to demonstrate what "UUP dump" is actually doing in the first place, it's always downloading files directly from the servers of Microsoft.

 

Here are some instructions

 

https://www.youtube.com/watch?v=4tYpbsOCZFs#t=2m44s

https://www.youtube.com/watch?v=jxd8gVxxg2k

 

I'm not posting any links to either site, though it's pretty easy to DAFS and then get build 22000.132 / 22000.160 etc. ourselves

 

https://www.google.com/search?q=40581f19-f582-43d6-9e6c-39aebde89d60

https://www.google.com/search?q=7a4e2fb8-88d7-4e4a-9a0d-6fb9c9f4df50

 

If we weren't exactly happy about jumping through all the hoops, we could consider joining their Windows Insider Program instead

 

https://docs.microsoft.com/en-us/windows/whats-new/windows-11#how-to-get-windows-11

https://www.microsoft.com/en-us/software-download/windowsinsiderpreviewiso

6ee25e52e740604881b2d11f003274f374488ae5 *Windows11_InsiderPreview_Client_x64_en-us_22000.iso
25617f9290a41f558cff1cccd415d566bc5d93c0 *Windows11_InsiderPreview_EnterpriseVL_x64_en-us_22000.iso

 


 

Alternatively, we could go for an existing version of IoT Enterprise LTSC instead

 

14393 (Windows 10 Version 1607)

 

Windows 10 IoT Enterprise CBB 1607
17114FC79D3DB79CA2F437F67F5FCA52EA91831A *CENA_X86FREO_EN-US_DV5.ISO
61F19FDDAE2092A13BD84FF9740B46B0215A8AD3 *CENA_X64FREO_EN-US_DV5.ISO

 

Windows 10 IoT Enterprise LTSB 2016
A577A7D997A455FF44A53A819510E7590B8F3B2C *CES_X86FREO_EN-US_DV5.ISO
470F865F42B7182472F5CD461FF3480ED363D5EB *CES_X64FREO_EN-US_DV5.ISO

 

17763 (Windows 10 Version 1809)

 

Windows 10 IoT Enterprise LTSC 2019 [ID: 3465]
6598bd10e43e4857610e66735b043f62e8036c11 *en_windows_10_iot_enterprise_ltsc_2019_x86_dvd_1df040b1.iso
225eea895e19bce56d43f00a1df37a93b6793bc9 *en_windows_10_iot_enterprise_ltsc_2019_x64_dvd_4c97c86c.iso

 

Windows 10 IoT Enterprise LTSC 2019 (x64) [ID: 6057]
2edc73585bd1557a3557ab80910da870341e7cb4 *en_windows_10_iot_enterprise_ltsc_2019_x86_dvd_2255a237.iso
b91f18cf0d63df2044f3a773eef5e58293c652b5 *en_windows_10_iot_enterprise_ltsc_2019_x64_dvd_a1aa819f.iso

 

34718de302982cd15de31483cfe4743ca67586a9 *en_windows_10_consumer_edition_version_1809_updated_sept_2018_x86_dvd_c5960600_to_en_windows_10_iot_enterprise_ltsc_2019_x86_dvd_2255a237.svf
66cf9f85ec9d44a5f2c7cb9bbcf84d21b5dfce1b *en_windows_10_consumer_edition_version_1809_updated_sept_2018_x64_dvd_491ea967_to_en_windows_10_iot_enterprise_ltsc_2019_x64_dvd_a1aa819f.svf
e864c2449a038a95194d76c507b214261af83151 *en_windows_10_enterprise_ltsc_2019_x86_dvd_b8ef2c2b_to_en_windows_10_iot_enterprise_ltsc_2019_x86_dvd_2255a237.svf
ceaeea8a43334f060df92aaeff3e94aa0016e974 *en_windows_10_enterprise_ltsc_2019_x64_dvd_be3c8ffb_to_en_windows_10_iot_enterprise_ltsc_2019_x64_dvd_a1aa819f.svf
d4f179a5b09b091c60e0323e2c4bc93ecc1b9a76 *17763.107.101029-1455.rs5_release_svc_refresh_CLIENTENTERPRISEEVAL_OEMRET_x86FRE_en-us_to_en_windows_10_iot_enterprise_ltsc_2019_x86_dvd_2255a237.svf
d8bec76f34764a70ac2f65fed1b177ae1b10ad30 *17763.107.101029-1455.rs5_release_svc_refresh_CLIENTENTERPRISEEVAL_OEMRET_x64FRE_en-us_to_en_windows_10_iot_enterprise_ltsc_2019_x64_dvd_a1aa819f.svf
5cc9c6c8434a5433ca2069a4cd5d4673108d9eb8 *17763.107.101029-1455.rs5_release_svc_refresh_CLIENT_LTSC_EVAL_x86FRE_en-us_to_en_windows_10_iot_enterprise_ltsc_2019_x86_dvd_2255a237.svf
c6588a0b655f8832ce7965793d2558d90c53fc64 *17763.107.101029-1455.rs5_release_svc_refresh_CLIENT_LTSC_EVAL_x64FRE_en-us_to_en_windows_10_iot_enterprise_ltsc_2019_x64_dvd_a1aa819f.svf
a64d4929c1ec686b7737716da181e2112e037903 *en_windows_10_iot_enterprise_ltsc_2019_x86_dvd_2255a237_to_en_windows_10_iot_enterprise_ltsc_2019_x86_dvd_1df040b1.svf
209a71b5b31f9a1292c80cd11f595ddddd17b159 *en_windows_10_iot_enterprise_ltsc_2019_x64_dvd_a1aa819f_to_en_windows_10_iot_enterprise_ltsc_2019_x64_dvd_4c97c86c.svf
14f9a304263b81f60e36ab8e8e71c8fa44bb83eb *en_windows_10_iot_enterprise_ltsc_2019_x86_dvd_1df040b1_to_en_windows_10_iot_enterprise_ltsc_2019_x86_dvd_2255a237.svf
35055e87e57349668c4c099bfd7200f4b7dd12c1 *en_windows_10_iot_enterprise_ltsc_2019_x64_dvd_4c97c86c_to_en_windows_10_iot_enterprise_ltsc_2019_x64_dvd_a1aa819f.svf

 

19044 (Windows 10 Version 21H2)

 

(TBD)

 

XXXXX (Windows 11 Version XXXX)

 

 

AMA: Windows 11 and Windows 10 servicing & lifecycle

https://techcommunity.microsoft.com/t5/windows-events/ama-windows-11-and-windows-10-servicing-amp-lifecycle/ev-p/2557212

Quote

“We announced the next Windows LTSC would be built on Windows 10, version 21H2, and yes it will be a 5 year support lifecycle. We can expect that the next LTSC *after* Windows 10 Enterprise LTSC 2021 will be built on Windows 11. And it will also keep the 5 year support. However, that’s expected in 3 years or so, so anything can happen in that timeframe. If you need to use LTSC for a longer period, we recommend moving to Windows 10 IoT LTSC.”

 


 

 

 

 


 

About 150 bucks for the 2019 version, though it might be a good idea to wait until the 2021 version is available

 

https://audiophilestyle.com/forums/topic/59727-windows-ltsc-install-for-music-server/?tab=comments#comment-1063212  

On 6/25/2020 at 7:10 PM, dminches said:

After that I purchased an LTSC high-end license which was required since I am running a Ryzen 3700.  They have to mail the license to you since the CLA agreement requires you to put a sticker on the case.

 

Cost was about $150 in total.

 

https://buy.advantech.com/968TW19HL0-968TW19HL0/968TW19HL0/model-968TW19HL0.htm

https://www.advantech-cl.com/products/810da47f-3ba6-410a-a39c-8acc5232ce76/windows-10-iot/mod_3bbe22e9-3b81-4bcf-a830-413ac8f64ea8

Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now


×
×
  • Create New...