agreed. mine has been trying to update since that aswell and it fails after 10% installation. microsoft needs to fix issues with or polish up the update before releasing so it doesn't cause problems.
Afraid Microsoft changed Windows 11 between 23h2 and 24h2 tightening up security in the backend. Memory integrity tool pointed out the driver mine was stumbling on. A Google of the Microsoft integrity tool is the one for that. That's if it stops at greater 70%, could be that. I've gone over that quite a few times so I won't again.
Going wrong early on might pass on that. Updating the drivers for no good reason can land you with an incompatible driver. I had that. That one was well known it didn't work with 24h2 in the testing of it.
If you start experimenting then you need to take a copy of the drivers and release so you can get back. Fortune on the one that got updated and was incompatible with 24h2 update I would it back.
The ISO method is the best for manual updating but you click don't update the drivers now... if it installs it will update the drivers. Gives you better error codes.
Farbar gives you an analysis of your system. All virus checking programs other than the Microsoft one should be removed since it can stumble on them.
A current reinstall of 23h2 can be done via the built-in menu that negates pages of stop, start etc you read on the net. I ended up doing that after each "experiment". The Farbar analysis and getting use to reading the log files is the key. Googling bits of the error log file pointed me to the Microsoft memory integrity tool. A magical moment 9 weeks down the road.