>>106304295
Fixed-release SKU of Windows instead of rolling - you'll be stuck to one specific version/semester/whatever the current naming is for the feature upgrades, though the update cycle for the release will be longer than in the regular GAC editions (5 or 10 years, depending on whether it's regular or IoT LTSC.)
Also you'll be missing on the surface-level UWP applications (located in Program Files\WindowsApps) like News, Weather, Game Bar, even Store and winget from the "App Installer" package.
Obviously the system apps based on UWP/AppX from %SystemRoot%\SystemApps like ShellExperienceHost, SecHealthUI, StartMenuExperienceHost, Search etc. will stay and are still in use, along with the fundamental UWP/AppX infrastructure holding it.
You can always launch "wsreset -i" to reinstall back Store, then install the App Installer package if it wasn't restored back. Or if all you care about is winget - use asheroto's script.
Otherwise (IoT) Enterprise LTSC isn't any more different than Enterprise SKU regular (other than the miniscule details you might not care about.)
Make sure you backup your important stuff, along with configuration stuff in the AppData subfolders and %ProgramData% for your programs, so that you can cherrypick and restore back.
Massgrave site also provides details: https://massgrave.dev/windows_ltsc_links
>>106304228
>>106304965
NP. It's a rather old case - it was like that ever since XP SP2.
Your approach seems overkill desu, you might think of individually blocking applications/services instead of straight-up blocking IP addresses that may harbor other services.
Unless your endgame is some sort of an airgapped system, and are willing to risk any fuckups when something won't work afterwards.
>>106304968
The MSFT Sonderkommando will force you to upgrade to 11 at gunpoint.
Otherwise you'd still be fine, at least for few years guaranteed: with ESU support up to 2028 and IoT LTSC support up to 2032. Third-party application support may vary over time.
