Beginner , I select and choose Windows 10 IoT Enterprise LTSC installation but why does it only show Windows 10 Enterprise LTSC on winver ? Spoiler: win10 Apologize for beginner question.
Why would you need to remove the HWID activation? You can simply generate a new one for any future windows install when needed.
If my question is off topic - excuse me. Do I understand correctly (hypothetically asking) - if we have "en-us_windows_10_iot_enterprise_version_22h2_x64_dvd_51cc370f.iso" and we install IoT Windows 10 directly - then to be actually IoT with the longest support life - then is this possible only through HWID only or is it also possible through KMS38 method?! Last year when I was experimenting I also came across the exact same case study by @NewbWin described here: https://forums.mydigitallife.net/th...prise-n-ltsc-2021.84509/page-194#post-1827152. As a memory from last year, when I tried to activate it via MAS with "HWID" - it gave some error and I activated it with KMS38 method, but the installed version changed from LTSC 10 IoT to LTSC (no IoT). My question which I wish to clarify for myself is - when using "en-us_windows_10_iot_enterprise_version_22h2_x64_dvd_51cc370f.iso" and to be via "winver" an actual IoT Windows 10 - with the longest support - is this ONLY possible via the KMS38 method?! To be more clear - is it possible to have Windows 10 IoT installed and through "winver" to be reliable that it is exactly that (having support until the year 2038) but to activate Windows 10 IoT only with the KMS38 method ? (Let's say I also have personal considerations against activating with the HWID method).
IoT Enterprise 202x LTSC can be HWID, KMS or KMS38 activated, KMS(38) starting with build 19044.2788. Enterprise 202x LTSC can only be KMS or KMS38 activated. From MAS website: Code: Difference between Iot and Non-Iot Windows Enterprise LTSC 2021: Licensing - Non-Iot version supports the KMS license but not the Digital license. Iot version supports the Digital license and after the update 19044.2788, it supports the KMS license as well. Sandbox - Initial release (19044.1288) of Iot LTSC didn’t have sandbox but non-Iot version had. Later updates enabled it in Iot as well, so there is no difference anymore. Reserved storage feature - Iot doesn’t have reserved storage feature and it’s install takes less space in installation. (Feature is not much important for LTSC release) Windows Update - Iot is supported till 2032 and Non-Iot is supported till 2027. Conclusion, Iot LTSC is better. You can change the editions to each other (Iot and Non-Iot Windows Enterprise LTSC) only by inserting corresponding edition key.
Possible ? I reinstall everything without activation again. From the video you posted , did you install windows 10 IoT on VM ? does activating the HWID on VM will affect other VM installation on other Windows 10 version ? Apologize for beginner question. Which update ?
So the short answer is that it is possible to enable IoT with KMS38, but it is conditional on reaching a certain version, which the official ISO is not. Then "en-us_windows_10_iot_enterprise_version_22h2_x64_dvd_51cc370f.iso" is certainly not "19044.2788". (It appears from your previous comment that this official ISO is "19041.2006" posted here: https://forums.mydigitallife.net/th...prise-n-ltsc-2021.84509/page-136#post-1760679). In that case, how do we "move" through this official ISO to "19044.2788" without having to indiscriminately download updates?! I mean which specific files do we need to manually download to be able to reach "19044.2788" to enable IoT with KMS38? Thanks.
That post you link at is not LTSC but normal useless IoT Enterprise. This is (IoT) Enterprise 2021 LTSC: https://forums.mydigitallife.net/th...ot-enterprise-n-ltsc-2021.84509/#post-1705449 And these updates will update it to the latest publicly available build: https://forums.mydigitallife.net/th...h1-22h2-vb_release.80763/page-16#post-1571109 What do you mean by this? Yes and no it doesn't affect anything, you can generate all possible HWIDs on all systems or real hardware as many times as you want.
What I mean was , if I install window 10 IoT activate with HWD in VM. After sometime passed , I delete the windows 10 IoT on VM and reinstall again , will it auto activate as it remember my VM hardware ? What about an actual installed IoT on the Computer with HWD ? will it auto activate and remember if I do a format or reinstall in future ?
It should, not on vbox but on vmware it should. No difference, it will pick up the HWID when the retail key is installed (IoT Enterprise 2021 LTSC has that key pre-integrated).
As long as the UID+MAC of the VM stays the same, it should always reactivate. Creating a new VM actually changes both in VBox.
Yes, but pleas assess the convo (+ the one about installing updates) and get why i didn't want to overcomplicate this, in short, on vmware a new VM should pick up the old HWID (with default settings) and on vbox it doesn't by default.