is Windows 11 IoT Enterprise LTSC 24H2 OEM activate-able with KMS or what version is need to make it run full, forever? I would like to give a try.
Windows 11 IoT Enterprise LTSC 24H2 OEM est activé avec HWID (Digital License) Method to Permanently Activate Windows or if it is not activated using the activation tool from massgrave the one that is not activated is Enterprise LTSC 24H2 if you activate with the HWID tool from massgrave it converts it to Windows 11 IoT Enterprise LTSC 24H2.
Kms38 only works for Windows 11 Enterprise LTSC 24H2 and not for Windows 11 Enterprise LTSC 24H2 IoT, right? Thank you
I think if Kms38 only works for Windows 11 Enterprise LTSC 24H2 I have never tried it I put Windows 11 IoT Enterprise LTSC 24H2 OEM which is activated with HWID (Digital License) Method to Permanently Activate Windows, with HWID only activates Windows 11 IoT Enterprise LTSC 24H2 OEM not Windows 11 Enterprise LTSC 24H2 OEM and activate it with HWID makes it Windows 11 IoT Enterprise with permanent Digital license while Kms38 is not permanent Digital License.
Everything worked out, thanks again! It is funny that the IoT ISO also includes non-IoT edition either, thought they will need more time for it. Wild. Does those versions have any impact on running games or RAM-intensive programs, btw? Some sources say its better to use home/pro than enterprise, especially LTSC IoT, but I can't really find any reason against it. Basically same just debloated, more security and remote things (corporation needs), but nothing that could cause disadvantage. Is there any important to know about?
Actually LTSC edition is not for gamers but AFAIK part of them is used Win 10 LTSC + MS Store installed on gaming laptops/PCs... You may try using Win 11 LTSC for a such purposes as well...
I know we can use massgrave to activate the IoT version, but would a windows 11 enterprise key activate the non IoT version, or this needs a special key?
All SKUs need their own key, KMS_VL_ALL and MAS can do all. All possible (IoT) Enterprise 2024 LTSC activation options: Code: 1. "Win 11 (24H2) Enterprise 2024 LTSC x64 en-US (26100.1)" 2. "Win 11 (24H2) Enterprise 2024 LTSC x64 en-US (26100.1 - MRP)" 3. "Win 11 (24H2) Enterprise 2024 LTSC x64 en-US (26100.1 - MRP - KMS_VL_ALL)" 4. "Win 11 (24H2) Enterprise 2024 LTSC x64 en-US (26100.1 - MRP - Online KMS by MAS)" 5. "Win 11 (24H2) Enterprise 2024 LTSC x64 en-US (26100.1 - MRP - KMS38 by MAS)" 6. "Win 11 (24H2) IoT Enterprise 2024 LTSC x64 en-US (26100.1)" 7. "Win 11 (24H2) IoT Enterprise 2024 LTSC x64 en-US (26100.1 - MRP)" 8. "Win 11 (24H2) IoT Enterprise 2024 LTSC x64 en-US (26100.1 - MRP - HWID by MAS)" 9. "Win 11 (24H2) IoT Enterprise 2024 LTSC x64 en-US (26100.1 - MRP - KMS_VL_ALL)" 10. "Win 11 (24H2) IoT Enterprise 2024 LTSC x64 en-US (26100.1 - MRP - Online KMS by MAS)" 11. "Win 11 (24H2) IoT Enterprise 2024 LTSC x64 en-US (26100.1 - MRP - KMS38 by MAS)"
When 26100 is finally released, will the 26100.1 component store packages finally be cleaned up? Every version of 26100 that has been released so far, still has the 26100.1 packages in the component store of the install.wim of the ISO, or after the ISO has been installed, these packages stay in the online image. 26100 runs great, but the residual 26100.1 packages are a bit annoying.
they changed the SSU to leave those packages/components to avoid (or reduce) PSFX errors if you installed the new checkpoint LCUs (26100.1252 or 26100.1330), the base LCU packages/components (26100.961, or 26100.1252) are the ones left, .1 will be removed https://forums.mydigitallife.net/threads/abbodi1406s-batch-scripts-repo.74197/page-153#post-1846116
So if I'm already at 26100.1301, then I am presuming that I only need to install windows11.0-kb5040543-x64_LCU_1330.1.0.msu. I can run cleanup after that, but the 26100.1 packages will be retained in a staged "State". Also, when I've used Rufus to create a bootable 26100.1301 USB, I can't boot to a normal install screen. Instead, I get a setup screen that asks me what language I want to install. I can't get to a "Command Prompt". Is this normal for 26100?
They only keep the latest checkpoint as staged, so there will always be two versions of packages installed - staged checkpoint and current lcu as "installed" For retail builds the checkpoint is still base 26100.1 because nothing else has been released yet 26100 has two installers, the modern one which acts as in-place upgrade and the old legacy installer
What will be the differences between the IoT 2024 General evaluation, and the IoT 2024 that will be released in October this year... ?
what is "General evaluation"? evaluation editions can't be activated at all (except server, you can upgrade your edition there) the final 26100 build was released months ago, nothing new will be released when it goes GA this fall also, this thread is about LTSC editions, and you ask about IoT, so wrong topic
I'm sure hes asking about the IoT LTSC. I don't get it either.... the linked OEM ISO has already IoT and non IoT LTSC 24 (build 2600), so what they gonna release? I could imagine a higher build that runs over normal VL channel (as normal enterprise does) but this IoT seems already fine enough, no need for any extra lol. Easy activating, see above. So yea.. I'm happy with that as windows base, rest doing tools.
Reason why i type out the full name every single time it is needed, to avoid all possible confusion. 26100.1 Enterprise 2024 LTSC in all 38 languages and maybe IoT Enterprise 2024 LTSC too this time? Fingers crossed