Oh, I see. Yeah, identifying the culprit / solution won't be easy, since, based on your experience with it, it seems to be related to one of the many package differences between a "normal" and a LTSC installation (or worse, the settings applied to an otherwise identical package included in both). Nevertheless, I wish you luck in investigating this, maybe it won't be looking for the needle in the haystack, after all. Keep us posted on your findings, if any.Thanks for the reply! I'll continue tinkering with both a fresh Windows 10 LTSC VM and this new Windows 11 LTSC version, and hopefully I'll be able to figure it out - in response to your question about a custom ISO - this is the genuine Microsoft OEM version downloadable here: https://www.microsoft.com/en-us/evalcenter/download-windows-11-iot-enterprise-ltsc?culture=en-us&country=us
So it's definitely not a concern of custom ISO's, but I take your point that custom ISOs could have been tampered with, thereby impacting this issue.
More to come

Statistics: Posted by Yincognito — Today, 7:17 am