Sorry to push in, but if I created an autounattend.xml file with the code you showed, placed it in the \sources folder, then the oobe will not ask to setup an online account at all (I understand I can skip, but the iso would be for non tech savvy people)? Will the rest of the oobe run as normal?
so far so good, although i had to redo path variables to %systemroot% , they got changed to C\windows etc etc
why do i have dev version installed after this update Microsoft.SecHealthUI_8wekyb3d8bbwe 1000.25305.100 Anyone else had dev build of security setup pushed after beta update? So eventually it started working, had to add [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa] "RunAsPPL"=dword:00000002 "RunAsPPLBoot"=dword:00000002 to lsa but the UI is kinda ugly Update: health service crashes randomly when accessing the UI, thankyou very much Microsoft This is a mismatch problem, dev builds of defender/security on beta build system32 applications/services
1 and 2 was already released on the Retail channel in 22621 build no one knows about Moment 3, but we should get all new 23H2 build in Autumn, so I'm expecting Moment 3 release sometime in Summer
yep, moment 3 August 2023 and 23/H2 October 2023 then that be the last Windows11 now they move on to Windows 12 what may be part of the canary channel.
If I'm not in the Insider Program and install 22624 I should receive drivers thtough Windows Update, app updates from Windows Store etc... but no Windows "Windows" updates? Am I correct? Without setting it in autounattend.xml there shouldn't be any difference between VM and real "physical" computer? And is the 22624.1465 amd64 officially available, as a legit ISO, verifiable via checksums etc.... or the only way is to build it on my machine from UUPDump script?