I, for one, did run the hvciscan_amd64 tool. Apparently, it found no incompatible drivers To wit:
C:\Temp> .\hvciscan_amd64VbsGetIssues: 0x00020040
UEFI WX Memory Attributes Table required
8GB RAM required
VbsIsRecommended: 0
HVCI incompatible driver scan start...
HVCI: Driver scanning complete
HVCI incompatible driver scan passed!
And still, the dreadful update won't install. This little game has now lasted far too long. Let Microsoft sort that boo-boo out until one can install the thing without all those convolutions it has put its users through.
The whole caboodle is a digital scandal. Meanwhile, let whoever is in charge include me out. I'm giving up.
I studied Microsoft's guide: "Get help with Windows upgrade and installation errors" - it was horrible reading for a normal user.
It contains more than 30 possible error codes and suggested remedies if the update fails - several of which have been featured here as well.
And they also say that "common errors can be fixed with a few steps (??) that you can do on your own"
It came to my mind that "does Microsoft now live in the same world as millions of users?"
Does Microsoft really think that someone could follow these massive and time-consuming instructions - after all, it's often a user, not an IT engineer?
Is 24H2 already too big and ambitious update for Microsoft --> it doesn't seem to be now under "anyone's control" anymore?
Is Microsoft trying to pass on fixing their own errors to users by releasing such a massive number of possible error codes --> this causes a large number of users to be in such a "distress" due to lack of knowledge?
Certainly seem to be duff drivers that don't pass the first boot at 30%. Found one of those. I suspect the bulk updating of drivers in 23h2 prior to the update is where people go wrong. You are told you need to update drivers that are old but they can fail in the upgrade which stops at 30%. There are sticklers that won't unload low level programs.
The most frustrating thing about sorting out the update was reading the same old fixes that didn't fix it. They might have fixed getting to 23h2 but don't fix to getting to 24h2. Hvciscan was the one that fixed mine after nine weeks of trying. The memory integrity at the end of all this was the one. The error code was too general,
Personally I can't see Microsoft sorting it out since they have changed the installation rules unless they go back and weaken what they are trying to do in making the installation more tight... tight it is. Thus the clock is running till when support ends.