Only by Googling bits of the error report did I come on the tool. Microsoft tightened up backend security in 24h2 so if the driver doesn't pass the test the system rolls back.
You can do this test outside the update, Google
Microsoft readiness integrity scan tool
Download the hvsci exe of choice. How to use it is online you pipe the output to a results file > old DOS command. It will tell you what has failed. You identify the driver or drivers and delete them. Reboot and try the update again. How to delete them is online. I have published it a few times on the net so you might stumble on my posts. Do save your drivers before deleting them in case you need to go back.
Same problem with a laptop dedicated to browse and view Netflix/Prime/... on a HomeCinema.
The system only has Windows11 and a browser, absolutely nothing else installed and yet, this funking update fails at 18% for a year now.It's not up to you users, me or anyone here to do the work.
It's up to M$ to clean its mess on our machines and do what it was payed for.
Not doing it is a severance of contract by M$. Full disrespect of the customer. Simple fact.At least, the update app must revert the update of 24H2 on all machines and wait for a working update to be released to restart the process.
Meanwhile, I'll switch to another OS.
Funk you very much, M$ !!!
The early failure at that stage will be the drivers not being compliant or virus checking software. On the first I did pick up an issue on the "journey" to quote reality TV. That was a driver with known issues picked up during the Insider phase. A nice Mr Muhammad had found it on a driver that was on my system. That version stopped migration at that point. The guy listed off release versions that were fine. I had a fine one but either not un checking the iso box, update driver now... updated mine to one that was not compatible. Hence why going mad on updating drivers isn't a good idea. Funny enough when migration to 24h2 was completed it updated the driver to the one that was not compatible with the 23h2 to 24h2. The question then is what happens when 25h2 comes out. Cross that bridge.
Two HP All in ones here with one year difference in manufacturing. Slightly different components inside and driver was never used on mine but on the other.
The root cause of all these difficulties is suppose to be Microsoft cutting back on development staff and leaving it to the Insider program to do QA. But lessons learnt need to be fed back in and acted on. Probably that which has been missing in 24h2 development. My solution on that memory integrity driver and the one that stopped me at circa 20% was in the Insider programme posts of bug fixing, not the main chit chat which just deals with standard Microsoft Windows update issues not the ones unique to the task in hand. Skilled individuals can read the error reports to sort it out or you have to train yourself up. If I was to charge my partner my old consultancy rates for sorting that one out I'd make a fortune. More cost effective to buy a new PC.