No, even IoT Enterprise LTSC 2024 requires full SSE4.2 CPU support. IoT just skips the arbitrary requirements like CPU and TPM.
2 great fixes. [sfc /scannow command] Fixed: You get errors every time you run the command. [Web sign-in] Fixed: You cannot sign in to your account from the web because the screen stops responding. This last one was stopping me using PIN to enter on Safe mode boot.
https://forums.mydigitallife.net/posts/1856490 And i have never used online accounts, when win 10 IP program started some releases to be able to get the IP builds but that was over when whatever127 made offlineinsiderenroll on @tistou77 his install it seems fixed, not on my fresh Enterprise 2024 LTSC install. EDIT: https://forums.mydigitallife.net/posts/1856501
@Paul Mercer I just finished in place upgrade to 1742.Now I should try manual or windows update to install kb5044284? I tried also the repair recovery option through windows settings but it didnt proceed because I dont have TPM and I couldnt install it with the /product server cmd like I installed the isos, because the setup through recovery starts automatically. Some said recovery option fixed the problem, but they had min requirements it seems.
@Paul Mercer It succeeded! I Installed manually kb5043080 and then kb5044284 and it worked. So for anyone who cant install kb5044284, I performed an in place upgrade with version 26100.1742 and then installed the aforementioned updates. Thanks Paul much appreciated!
24h2 is getting there slowly I might try again in few weeks. main bug i need fixing is the easy anti cheat not working If anyone can report back will be much apreciated
I managed to get around by removing the old easy anti cheat map in C:\Program Files (x86) leave the EasyAntiCheat_EOS map other wise the games that use it won't work
24H2 is really bad, for once I can not clean install it without formatting all disks via BIOS, since the setup fails when scanning disks, but reports suggest rufus/ventoy might be at fault. Secondly, I can not enter safe mode, OS reports that the PIN is invalid, but it can not be reset even with network and the only way to recover is to restore a system image, PIN is suddenly valid, that would not be possible if TPM was reset, system backup is unable to restore an invalid PIN. Strange things.
Some of the problems seem now fixed in 2152 Release Preview at least the sfc and pin problems. Let's hope this update soon gets to the retail channel
Thanks, then again, I am sort of glad, it seems that Defender can be disabled without safe mode again.