For what, your trophy board --- made by MS, evidently SHA256 says . I run german OS. Was on 2021 LTSC IoT and prepared to switch to 24H2 LTSC IoT. Challenge: the MS language barrier for In-Place-Upgrades (no option for programs and settings). Solution (found somewhere here ): Change System-Language and Region to en-US in Settings, completely. Rebbot if needed, is better ten just logging off and back in. [Source: https://forums.mydigitallife.net/posts/1842221] Then in Registry values need to be adapted, especially InstallLanguage --- this is the value the Setup checks . Setup only accepts en-US Installs, so ... In admin CMD: Code: reg add "HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Nls\Language" /v Default /t REG_SZ /d 0409 /f reg add "HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Nls\Language" /v InstallLanguage /t REG_SZ /d 0409 /f REBOOT!!!! MANDATORY!!! Won't work else. Now Setup will offer the once greyed out option .... Profit . Change Language back in Setings ... I already did the switch here on my 2 main riggs .
@Paul Mercer ahh, nice you remember . I edited my previous post . I used your uupdump offline project --- pretty -s-m-r-t- i'd say, but who am i .
dang!!!! missed that completely -- aka forget to test after the dev abandoned his puppie™ --- stupid doggie!!! Any things to know/adapt??? Then my tool can download it from source on command and unpack to its _tools folder. MARVELLOUS™!!!! I had that PHP-Standalone from mkuba once ... unfortunately stopped working .... still have the Files and the GitLab we shared ...
I don't understand what happening - I have the following scenario: (IN THE SAME MACHINE) I'he installed Windows 11 Enterprise 23H2 X64,(Using ISO from MCT) without any problem. When I've tried to install Windows 11 Enterprise IoT 24H2 GE, after the phase of copying files finished, when restart, the machine stuck at the Windows boot logo in an infinite looping... Someone have some suggestion on how to fix this issue? Thank you beforehand!
Hmm, lots of restructuring inside the system - aka Copilot Integration at system level -- 'normal' CUs like regular builds get, that change things before RC and open new gliches and hickups atm. As i see it so far, things are still in flux and RC so far on horizon ... ... Collect reproduceble issues and validate if Rigg or Windows. Then check if changes happen better/worse afte installing KBs, then MS knows the quirks and is testing mitigations ... If i'm right --- it's like @mxman2k hunting quirks in 'Alpha-Flights' --- happen but might be connected to the status of the build --- so RC == no quirks
TL;DR: it's still 'Beta' with bigger changes and was assumed production ready - then a first build for a ltsc is set, if -- remember 2015 was replaced, wasn't production ready (in the end) >> 2016 appeared shortly after (in LTSB/C-Cycles)....
Thing is Copilot was planned differently --- they realised, 2 options; disable and make differences for EU (2 'lines') or make it an APP as Central GUI, can be installed and will integrate, but is not shipped with the build ... think they are still evaluating, if it's doable while Flighting or ... next candidate ... already happend at that stage .
Still the same question, is it about IoT Enterprise 2024 LTSC or about normal IoT Enterprise, which is not a usefull sku when it is not LTSC. You are mentioning MCT so it is will probably not be about any LTSC version.