not here, started from 26100.1 - removed it then updated all the way to .994, it didnt installed for me. so try the same maybe
found something interesting, in windows 11 22h2 to disable autoupdates i normally removed UsoSvc from netsvcs in svchost Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Svchost autoupdates were paused windows wont update itself but i could still use wumt to download and install updates i want. in 24h2 if i remove UsoSvc from netsvcs in svchost autoupdates will be disabled but installing updates manually or using wumt wont work either. sneaky Microsoft lol
Long time lurker... Spotted ya can activate on original build... But if you update it to....863 it refuses to activate and I can no longer check activation status...
just installed, real HW (vhd, multiboot) it goes automatically to .863 during OOBE successfully HWID activated (MAS)
Just finished installing and updating IoT LTSC. No signs of Co-Pilot here (used a local account, UK region). Gotta say though, the UI animations are somehow much worse than 23H2. Didn't think it was possible for Windows 11 animations to get worse, but here we are. Opening the Start menu over top of a few other windows causes it to lag like crazy. Same for minimizing and maximizing windows with others behind it. Just awful Question: anyone know how to enable Windows Spotlight on the lock-screen? The only options I have are Picture and Slideshow.
Iot ltsc 2024 is still full of bugs wait for a few months then try again. Myself I will stick with 22h2 untill next year
Fixed it. I used geek uninstaller to remove the microsoft edge update program. Hasn't been back since. So if anyone hasn't make sure you remove the microsoft edge update program as well only listed in the apps section & not the control panel programs & features section.
Me too, 24h2 - 26100.994 - Same attempt, same message after the update reaches 100% and the device reboots.
Drivers are not available to download however accordingly to reliable sources, the stock image has drivers in this location C:\Recovery\OEM Wondering if I can extract them to a safe location and inject them to boot.wim and install.wim of iot enterprise USB key