On the last two... it took my nine weeks to install Windows 24h2 on one laptop. Memory integrity of a driver was the issue on that. Mentioned that n ' th times. Happens at 70 percent when the final system is being made. If an existing driver fails the test it blows out. You can do the test outside, isolate driver, delete it and go for another update.
The early ones at 20 percent are drivers that aren't compatible with 24h2. That's like Windows 7/8 migration to Windows 10 will only cross the boundary on a set of drivers.
The error reports if you learn how to read them will tell you what's going on but a skilled task to read them. There are experts.
On fixes you got all the normal ones published that are regurgitated by "experts" which tend to be pre 24h2. You get use to quickly reading those... no, no, no. Those fixes in anycase are built into 23h2 where you can do an inplace update to 23h2. Resets everything back before you attempt to do the upgrade.
If you aren't seeking outside help with the error reports you have to be methodological in your working, keep a copy of the drivers. Don't update all the drivers, all together. Only use the manufacturers published drivers they can be modded. Driver changes can introduce issues which were not the original issue etc.
Ditch all non Microsoft virus checking programs and low level stuff.
Best of luck.