Did you try the download section at the OP? And no, the IoT versions, LTSC and non LTSC don't require the windows 11 hardware requirements.
This thread has been a delight to read through. Enjoying the forum very much. Appreciate your help! Seems on my next install I should use the Windows 11 IoT Enterprise LTSC 24H2 OEM (en-US only) iso instead? Wondering why the ISO file size is smaller though? Also is there a way to to change my displayed member name? I don't see where I can change it in my profile settings. Didn't realize when signing up to the forum it was going to use my name as my displayed member name.
Yeah, there are good people that post really useful stuff, like Updates, ISOs and tools (scripts and more) Well, first, do you have a "Win11 Hardware Compatible" device??? If not, you only can (officially) install Win11 IoT (GAC/Non-LTSC or simply LTSC). The IoT LTSC ISO is smaller because it only has one or two editions, it doesn't have the latest monthly cumulative update, and most important, it doesn't have the Bundle Apps like a "normal" GAC ISO (No Store, Mail, Calculator, Clock, and the rest of the apps). If you have a CPU that were made several years ago, for example Intel 8th Gen or old, it's recommend to stay in Win10. Although, even if you have an Intel 14th Gen (the latest until 2024), you will notice the same slowness and buggy general performance in Windows 11 (even on the latest v24H2).
@P40L0 LTSC was never about features. It will not receive EP through windows update, nor would you be able to manually install it via conventional means. You could force it onto an LTSC build, but all you'll really do is change the build number.
Yeah I know, but I mainly use IoT for removing the bloat since the beginning and use it mainly for gaming. But let's say MS will add useful gaming stuff in 25H2 EP, is there a way to get that also in IoT or do I have to wait for next IoT ISO build in 2 years or so?
You're circling around the same answer. LTSC editions do not get feature updates and even if you were to force the EP onto your build you wouldn't be changing anything apart from a few digits. I don't know why you keep referring to LTSC as IoT, when the two are separate things and one is not descriptive of the other.
Because Windows 11 IoT Enterprise LTSC 2024 is too long but I was obviously referring to that as we're in this topic Anyway, no way to force EPs (and their features) there, got it.
With such specific ISO filenames and SKU names it is best practice to type the full names, to reduce the confusion.