Hello everyone, a question for the audience: changing the image edition of Windows Enterprise LTSC to Windows IoT Enterprise LTSC is very simple, Spoiler Code: echo. ECHO. ECHO ============================================================= ECHO Upgrade to IoTEnterpriseS ECHO ============================================================= dism /Image:"%~dp0mount" /Set-Edition:IoTEnterpriseS but can anyone tell me what command to use to change the image edition of Windows IoT Enterprise to Windows IoT Enterprise LTSC ?
You cannot directly upgrade from non-LTSC to LTSC or vice versa, at least with official commands. LTSC is an independent branch and excluded from the regular Edidtion upgrade matrix, as well as the other way around. Or, in other worlds, you can only switch between regular Editions, OR, between LTSC Editions. You can't make regular to LTSC and you can't make LTSC regular, without some black magic (which belongs to the Reconstruction thread, I guess).
Got it, thanks, then I'll have to resort to black magic. I'll have to get out my old "tambourine" and dance around the SKU with it.
The Reconstruction topic (just next to this one) might have some of this magic. Asking doesn't hurt, I guess. But MS definitely decided to strictly separate the two (with LTSC not really being for the common public).
Actually, that's why I asked: in order to change the edition from IoT to IoT LTSC on the installed OS, it's enough to change the product key. That's why I thought that maybe they'd share a script here for changing the edition from IoT to IoT LTSC on the connected image. Well, if not, then no, I'll figure it out myself...
No, you can only switch between LTSC and IoT LTSC and back, using key. Switching from regular IoT to IoT LTSC only by key,even online, would be news to me.
I'll tell you more: I've been doing PCs for a long time and my first OS was Windows 98. I've been building Windows builds since Windows 10. So I have some experience in this business. As a test, I tried changing the product key in the installed OS and in other editions (except Home) to the IoT LTSC key and they activated as IoT Enterprise LTSC. Therefore, I think it is still possible to change the edition from IoT Enterprise to IoT Enterprise LTSC in the connected image. I will think, experiment, and I think I will solve this problem. While I'm looking for ...
There are only two answers: either they don't know it can be done that way or they just don't need it. Personally, I like the IoT Enterprise LTSC version, that's why I'm doing this. While I'm looking for a solution ...
Image with UUP DUMP - 26100.3476.250305-1650.GE_RELEASE_SVC_PROD1_CLIENTMULTICOMBINED_UUP_X64FRE_RU-RU_FIX.ISO processed by script from SunLion + NTLite (Presets from bendeyar).
Ah, so, this is NOT "by key only". It is already a Frankenbuild, with supplying files from LTSC, as you are not supposed to do that. Not anticipated by MS, not tested at all, and can lead to problems later. Not to mention that most user won't have these files, either. I'm out.
==================== 24H2_Integrator_10.0 ==================== Updated to version 26100.3476 https://forums.mydigitallife.net/th...ic-legacy-windows.86552/page-120#post-1872013 Enjoy
hi sun lion. am using this script you made 24H2_Integrator_7.8.7_31-Defender i want to keep defender is it posible to update that script to this version.? what should i do.? another question why changes in versions number .? you had 9.0 then 7.8.7_31 and again 10.0 the number 9.0 and 10.0 seems obvious but why that jump to 7.8.7 are they 2 different scripts.?
I've skipped to 10 so there's no doubt about the progress. The other versions are old and no longer in use. I'll delete them soon. They are not different scripts, just updated ones. I'll try to adjust this new one with Defender for you. From now on I'll try to always post in the same topic to make searching easier.
SunLion, Just one question: you refer to .reg files in your preset, but where are these files themselves or what is in them? Spoiler Code: <File>E:\[_W11_]\Slipstream\BypassTPMCheck.reg</File> <File>E:\[_W11_]\Slipstream\UAC.reg</File>