Hello! I have a couple of questions. This is the OS I am running now: "Windows 10 Pro 22H2 x64" (activated with KMS_VL_ALL). This is the OS I want to convert to: "Windows 10 IoT Enterprise LTSC 2021 x64" (and I would like to activate it with KMS_VL_ALL too, if possible). I would prefer to upgrade my existing Pro version, with all programs and files intact, to the IoT Enterprise LTSC 2021. If I do it this way, will there be any Pro "remains", in terms of settings etc.? Can there be any problems? How can I do it exactly? And with the IoT Enterprise LTSC 2021, would I be able to disable the telemetry, as in set it to 0 - Security level etc.? If the in-place conversion fails somehow and I have to do a clean install - do I need a generic key for a clean install? Which one for the Windows "10 IoT Enterprise LTSC 2021 x64"? Do I need a key for an in-place conversion from Pro to IoT Enterprise 2021 LTSC as well? Also, how to tweak IoT for personal use, ie. set Windows IoT for "regular" (Enterprise/Home) use? I mean Group Policy setting changes etc., so it's a bit more like the regular Enterprise version (minus privacy intrusion). Are there any guides for that? Has anyone here made an in-place version conversion from Pro to IoT LTSC? Is this a good way to do it? I have a ton of programs, settings and tweaks as I use the computer for audio production, that's why I'd rather do it this was and not a clean install. Thank you in advance.
https://forums.mydigitallife.net/posts/1846462 In your scenario you can try to set EditionID IoTEnterpriseS, but EnterpriseS is ok too, you can always switch to IoT Enterprise 2021 LTSC (IoTEnterpriseS).
Thank you for the reply. So, I should get the IoT Enterprise 2021 LTSC ISO and extract it, then run "reg add "HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion" /v EditionID /d IoTEnterpriseS /f" in my Pro, then run Setup and install the IoT LTSC. Should that work without a problem? Should I uninstall KMS_VL_ALL before the update/conversion and then reinstall it after? And do I need a generickey to enter in order to do this kind of update/conversion? And what about a clean install, would I need a generic key to enter? It there any tweaking required to make the IoT LTSC more into a regular/user type of OS, is there a guide or something maybe? Again, thanks.
hey im quite a beginner to this, i decided to change to win 11 but it sucked so i want to return to windows 10 iot ltsc 2021, but i would like to already have the iso updated to the latest update from windows update, how do i do that? i dont understand... i know there seems to something like that here but i dont get it...
Now I tried converting my "test VM OS", Windows 10 Pro x86, to Windows 10 IoT Enterprise 2021 LTSC x86. But I was only able to get the non-IoT version for x86 so I installed that and Windows is now Enterprise 2021 LTSC. Then I tried converting it to IoT by changing the key, and it succeds. But when I then try to activate it again, the activation changes is bact to non-IoT version -> Activating: Windows(R), EnterpriseS edition Code: Running KMS_VL_ALL v53 Activation Mode: Auto Renewal Activating: Windows(R), EnterpriseS edition Product Activation Successful Remaining Period: 180 days (259200 minutes) Why so and how can I make it so it actvates the IoT version and not changes it back to non-IoT?
IoT Enterprise 2021 LTSC did initially not support KMS. It should succeed after it has been updated, though.
From 19044.2846 forward, it is OEM and VOL for IoTEnterpriseS. 19042.572-20H2 19044.1147-21H2-SAC 19044.1149-21H2-LTSC-Partial-17763 19044.1200-21H2-LTSC-Full-19041 19044.1263-21H2-LTSC-Full-ChromiumEdge 19044.1288-21H2-LTSC-Full-Win32Calc-x86-x64-GA (Public Release) 19044.1415 19044.1737-21H2-LTSC-Full-Win32Calc-a64-Selectability 19044.1741-21H2-LTSC-Full-Win32Calc-a64-Selectability-arm64 19044.1806-22H2-LTSC-Full-x86-Compatible (with my VMware) Code: 19044.2846-22H2-LTSC-Full-OEM-VOL-for-IoTEnterpriseS 19044.3448-22H2-ue3393-WindowsBackup-amd64-Compatible (with my PC. So, my daily OS is always 19044.3488.) 19044.3930-22H2-ue3758-EdgeAI-OEMDefaultAssociations . . .
Code: 19041.1151: Win 10 RTM IoTEnterpriseS OEM 19041.2788: Win 10 RTM IoTEnterpriseS Volume 19041.4239: Win 11 RTM IoTEnterpriseS all (to support Downgrade Rights)
You guys are right! I changed it to IoT LTSC by changing the key and then updated it from v19044.1288 to v19044.5011. After that I tried activating with KMS_VL_ALL and it worked like a charm. Thank you and thank you abbodi1406 for the activation tool. For everyone who's running the 2021 LTSC version - have you ever run into a problem where some software wouldn't get installed, because it would demand the latest Win10 version (22H2)? Or any other problem? I'm thinking of switching OS on my main PC, from 10 Pro to 10 IoT LTSC.
Sadly, MS is starting to crack down on users using LTSC and have started to block some MS apps from working properly on LTSC. The two apps that I know of that have stopped (or will stop) working properly in LTSC are: 1) Teams app 2) XBOX app For example, with the XBOX app, if you run it on an LTSC version of Windows, you'll get a message in the app that states that this version of Windows is no longer supported. I've seen some reports on Reddit that some newer games that depend on the XBOX app will no longer run on LTSC as well. I think MS is aware some people are going to switch from 22H2 to LTSC over the coming months and they may continue to crack down by locking down additional Microsoft Apps from running properly on LTSC.
The 2 apps are "Metro" apps, right? I don't use those. I don't need xbox and if I'd need teams I'd install the "normal" desktop verstion (at least I think it exists). But thank you for the comment, much appreciated.
Yes these are only being applied to Store apps, which is not really much of a concern for most LTSC users since they install LTSC to avoid as many store apps as possible. LOL
Hi I remember several Software demanding 22h2, Steinberg Wavelab for example, Is there a solution to bring LTSC 2021 to 22H2 offline as ISO ?
But.. who knows what games/apps out there that will collaborate with MS.. and implement features in their installers where it can see if you are running "LTSC" and not install. Gotta remember... they will collude with each other to their benefit.
I've read somewhere that some Adobe software also won't work on LTSC versions. Would such softare's installation fail because it's a LTSC version of Windows or because it's the older 21H2 version? I hope there's a way to trick such software.
All Adobe software actually works on LTSC (21H2), but Adobe added blocks to prevent installation of certain apps to be installed on LTSC. There are ways around this block, but it mainly involves using pirated versions of the apps. All software that works on 22H2 would work on LTSC 21H2 as they are essentially the same build. The issue is that some app developers believe their apps should not be installed on LTSC versions because LTSC was not meant for general usage, so they add these blocks.