Yes they do say do 2. I did a bit of that for a bit of that. I might have had that connected after I did the HVCI fix.
Others in posts say remove boards and it starts to get silly with a laptop.
There is the dice and slice method where you disable everything that isn't Microsoft on the drivers. Mind you that didn't find the troublesome Adobe DVD driver that wouldn't have been Microsoft. You'll find on Microsoft guidance the dicing method. It's like a routing method.
I can say the same about you. If you think that your problem is global, you're wrong! A lot of people do not have any problems with the installation of Windows 11 24H2. I just had the same problem as yours and found a solution for myself. If this solution doesn't work for you, look for another one.
For information about USB port compatibility problems, you can find more details in this paper: https://www.usb.org/sites/default/files/327216.pdf
And if you don’t want to read about people's experiences to find a solution, just leave this forum and look somewhere else.
A lot of people do have a problem why Microsoft pulled the update soon after they released it then started to slowly issue the update invitations again. They were specific issues on their help page but other issues are more global than those. The Insider Programme identified the issues but it was still issued irregardless. The solutions are in posts from people on the Insider programme at the time plus a blanket of people posting the same old stop and start this etc stuff. Some experts you'll find ask for the full log report being use to reading them can isolate the issue. Incompatible drivers.
The memory integrity one isn't going to be fixed by an automated approach else you'd have to disable memory integrity which I've seen people do (UEFI) or disable the driver and flag up at installation that, that had been done. The average user isn't going to sort that one out for themselves and will go to PC support who will do a clean install. If I'd charged my old consultancy rates out to the partner they would have owed me a lot. We were working on the basis of taking it to 18 months of Windows 11 23h2 support then do a re-install or bin it, try 25h2 in October next year.
Found a solution HVCI scan, the knowledge hidden in a corner of the Internet in amongst all the other normal repeated trash solutions. Goggling a fragment of the log code brought that one up. The other non compliant driver that stopped it at 30% the same.
Most of the YouTube Internet channels are saying leave it to April for Microsoft to sort out but personally I doubt they will. Manufacturers would need to update their supported drivers then you still got incompatible programs and other drivers that have got on the system that aren't part of the manufacturers release or Microsofts. Comes of changing the rules of Windows 11 mid play. That is what they did. Tightened up backend security.