Windows 11, version 24H2 won't install

To all it concerns (that's meanwhile quite a lot):

Again, Microsoft urges me to do the accursed 24H2 Windows 11 update, which definitely can't succeed, as Microsoft and a huge amount of users know by now. That is, lest one does some time-consuming digital acrobatics, which I am not prepared to submit to and that don't even guarantee a positive outcome most of the time. So, I have decided to stop all updating until Microsoft has sorted out this mess.

Bye,

HKB

I, for one, did run the hvciscan_amd64 tool. Apparently, it found no incompatible drivers To wit:
C:\Temp> .\hvciscan_amd64

VbsGetIssues: 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?

https://support.microsoft.com/en-us/windows/get-help-with-windows-upgrade-and-installation-errors-ea144c24-513d-a60e-40df-31ff78b3158a#WindowsVersion=Windows_11&articleFooterSupportBridge=contactUsBridge

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.

I, for one, did run the hvciscan_amd64 tool. Apparently, it found no incompatible drivers To wit:
C:\Temp> .\hvciscan_amd64

VbsGetIssues: 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?

https://support.microsoft.com/en-us/windows/get-help-with-windows-upgrade-and-installation-errors-ea144c24-513d-a60e-40df-31ff78b3158a#WindowsVersion=Windows_11&articleFooterSupportBridge=contactUsBridge

I, for one, did run the hvciscan_amd64 tool. Apparently, it found no incompatible drivers To wit:
C:\Temp> .\hvciscan_amd64

VbsGetIssues: 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.

Did you run the hvciscan_amd64 tool to identify non compliant drivers, and the farbar tool?

Yes I agree if it gets to 70% and unravels then it's the final boot where it doesn't like things where memory integrity is enforced. Hvciscan will be the point of weeding out duff drivers. Hanging onto non Microsoft programs that do stuff like virus have to be ditched. Farbar will tell you what's on it.

I did have an introduced non compatible driver that blew out at 30%. Basically I never had that driver till I updated the driver which people say do... isn't always a good idea. Lucky I knew which one I'd updated and a Google picking up Insider experience earlier in the year... picked up on the driver being problematic so I reverted back. Was at 70%, then 30%... then got it back to 70% then found the HVCISCAN suggestion from 2023 that did the trick after the surgical removal of the offending driver that had been knocking about from the outset. Just the one. An Adobe DVD driver... it might have got in via Adobe Photoshop.

ISO method don't take the updates, the default, toggle to not now. Those driver updates will be done later within the system. I'm not convinced it wasn't reintroducing the 30% rogue one which I'd found was not compatible In getting beyond 30%.