yes, its not the LTSC experience you had with windows 10, because what you installed is not 24H2 LTSC
Did you try restarting that worked for me. I don't remember if it was the exact same error but I got an error too at first.
from uupdump make 26100.268_amd64_es-es_professional_f801fc1f_convert_virtual.zip --> 26100.268.240408-1720.GE_RELEASE_SVC_IM_CLIENTIOTENTERPRISE_RET_X64FRE_ES-ES.ISO leak winre.wim from sources\install.wim at windows\system32\recovery & replace at yours recovery partition Recovery\WindowsRE no need reagentc thing at all saludos from spain
ltsc build are only leak... iotenterprise on uup dump = windows 11 entreprise ltsc are not avaible on uup dump...
So I'm trying to divine what's going on with the branches right now. Here's my take, based on speculation from myself and an AI fed all the details. 1. The LTSC leak is ge_release_svc_oem, has appended to it the designation marking it for oem preinstallation. 2. Dev and canary have now both forked into 26200 ge_prerelease, which is following my theory 26200+ will remain insider-specific. 3. 26100.268 carries the designation ge_release_svc_im. My digital ally has, with much input, suggested this means "Insider Merge." 4. Provided it does mean "Insider Merge," then it is the legitimate heir to 23H2. It will only receive updates that pass dev and canary scrutiny and no others. 5. If that's all correct, there is no reason not to upgrade to LTSC this very day. It likely contains the improvements of 23H2, the benefits of a branch refresh and base reset shedding built-up funk, and new features that have left the "experimental" stage. It is also likely to accept updates from now until the end-of-life, not requiring further reinstallations, much like 22000.1 before it.
Dev is still 26100, not 26200. LTSC leak is also 26100.1.ge_release, not ge_release_svc_oem CU 26100.2 is ge_release_svc_oem
the leak will still make ya update to 268 so your not getting the actual 1 your after that some think it is
Wrong. Technically it's on both. As if LTSC wasn't patched with WU to oem/im. Bruh why so pedantic? You'll remember I called it. 26100 WhateverSKU is mainline. If you want to install Core go ahead, you'll have it until 24 or 25H2 end-of-life.
Every Year this happens, and I do wonder why people get themselves tied up in knots over this (is it RTM, is it Dev or OEM, etc etc etc. And every year the same answer. So for this year, 26100.xxx can be loaded on your computer AND YOU DONT NEED TO BE ON WINDOWS INSIDER. 26100.xxx RECEIVES ALL WINDOWS UPDATES. What more does a person want.
Seriously, don't install Win11 26100.1 aka 24H2 "RTM"... I just used it to upgrade 2 laptops and 1 Desktop from latest official 23H2 (using an UUPdump to ISO conversion, no Insider enrollment) and...it was a bad idea: UI Animations and graphics performance in general was abysmal on all 3 (lag/stutters everywhere, especially on the 2 laptops including one with a 13th gen Intel i9 13905H + NVIDIA 4060 + 32GB RAM 6400 Mhz + m2 SSD...) Random BSODs for no clear reason CPU/GPU temps were higher (yeah, even after the initial setup when they settled in) Phone Link app was corrupted and there was no way to repair or reinstall it Other Store apps stopped receiving updates When closing the lid of the most powerful laptop of the 2 (see above) it started to overheat almost to a boiling point with the fans not working at all. I luckily noticed it in time to force shut it down Battery life was halved on both laptops Luckily I had recent Macrium Reflect Free system images of 23H2 as a backup which I successfully restored and all 3 went back to normal without a single issue. If 26100.1 was actually chosen as 24H2 RTM, well, may god help us all in the next months...