When I try to update to Windows 11 24h2, the installation always freezes with a black screen.
After hard power off, everything was undone on next boot.
The solution was to set the iGPU to GAMING in the BIOS. With the GAMING setting, I was able to successfully update to 24h2.
Thank you for sharing this. I have asked internally about pinning this for anyone else experiencing update issues on their AMD based Framework product.
In the meantime thanks again!
Hi @Heinz-Willi_Eichmeye, our engineering team has posted an update to this thread with an updated driver bundle. With the Windows update installed (which you have sorted with the tweak to BIOS, you can use the updated driver installer here.
The direct exe download for the compatible driver bundle is here.
I upgraded my FWLT13 (AMD 7840U) from W11 23H2 to W11 24H2 without setting the iGPU to GAMING.
I downloaded a W11 ISO, mounted it, and then opened the mounted ISO which autoran the setup.exe on the ISO.
My wallpaper did get set to solid black, but I easily set it back to the custom slideshow I prefer.
It also forgot the Wi-Fi passphrase needed to autoconnect to my Wi-Fi, so I just re-entered it.
Why wont 24h2 boot without the igpu in gaming mode? I’ve applied the driver bundle above.
That’s odd. It works fine for me in productivity mode.
But I have updated all AMD drivers (chipset and graphics) from the AMD website.
Still issues in 2025 with the latest driver bundle (including ancient video driver).
Trying to upgrade from 23H2 to 24H2:
This happened to me too. I left for a while and came back to the screen being black and the CPU fan blowing. The only thing I could do is a hard power off. It rolled back the update and does not give the option for 24H2 anymore. I have the latest driver package. I did not change anything with the iGPU.
in my case, it was =0x80070002 and 0x20007 (Inplace Upgrade via ISO and Windows Update with no difference).
Solution: incompatible Drivers from X-Rite Colormanagement (installed via BENQ Palette Master). Deinstallation of Palette Master and FTDI doesn´t do the trick, i had to erase the Drivers in Windows FileRepository… (Take ownership of files from the system to users and then full access to files and then delete them)
This happened for me several times, Windows has offered the update to 24H2 several times, each time after a break of about a week. Each time the update started and was reversed by the system. A concrete clue to the cause was in the error log, but as usual well hidden.
See my answer to the contribution of voltagex above…