ntdevlabs
Windows 11 installation has failed
When i try to install tiny 11 it goes normally until the large blue screen with the installation it gets to 5% and then crash saying Windows 11 Has Crashed. here is some pics for help
i also tried to open the setup file in the sources folder and i get this error
PS:i ran it as an administer and this is the second time i download it incase of corruption,im running the setup from my pc because i don't own a USB,also tried restarting and trying multiple times
try to test in a vm see if it gets installed or no. if no, then you have to create tiny11 again
I recently experienced this, I also experienced it on the 24H2 Tiny11 ISO that's out there.
The issue is due to 24H2s changed to the WinPE client, I discovered it because I usually do my modifications from a VM and then use DISM to capture an image and integrate it with an ISO. This now causes the mentioned error.
The solution/workaround is to copy out the contents of the ISO to a folder, say "ISO_Files" for example and perform the following modifications.
(Replace the paths with your equivalents)
DISM /Mount-Wim /WimFile:D:\UUP\ISO_Files\sources\boot.wim /Index:2 /MountDir:D:\UUP\Mount
reg load HKLM\TEMP D:\UUP\Mount\Windows\System32\config\SYSTEM
reg add HKLM\TEMP\Setup /v CmdLine /t REG_SZ /d "cmd /c start /min wpeinit && \sources\setup" /f
reg unload HKLM\TEMP
DISM /Unmount-Wim /MountDir:D:\UUP\Mount /Commit
What this does is forces the WinPE to use the legacy/23H2 version of the client, which allows installation to proceed as normal, looks like they borked all the old methods with the new 24H2 client.
Once the modification is made use ADK to re-create the ISO with the changes:
oscdimg.exe -m -o -u2 -udfver102 -bootdata:2#p0,e,bd:\iso_files\boot\etfsboot.com#pEF,e,bd:\iso_files\efi\microsoft\boot\efisys.bin d:\iso_files d:\Win11-24H2.iso
Again, make sure to change the paths according to your setup.
You could use the 23H2 DISM to capture, but the UEFI bootloader has been invalidated as secure, so you'll have to turn off secure boot to install.
This happened again with 25H2, and this workaround works well, so I request to re-open this issue
