Windows 11, version 24H2 won't install

Hi Terence, No way I will update until Microsoft brings its own mess in order.HK

They got a lot on at the minute. Possible take over of TikTok that will be a nightmare 🤣.

Windows 24h2 is a self inflicted wound. Changing the spec to tighten up security, they would have to untighten it. You got till next year till security updates will run out on 23h2. 25h2 is to continue with Windows 11 so the story goes. They got themselves in a bind.

I have the same problem, 24H2 won't completely update. I get to 100% then, geta message that the update failed. If many people are having issues, why don't you fix the update. Really annoying!!! Please respond.

Didn't have that one fortunately. Would have been upset as we pulled up chairs once it had progressed beyond 70%. The sticking point for weeks. We'd opened the champagne already 🍾 🥂.

I'm pretty sure MS just wrecked my laptop.

Probably got a driver installed by it that needs removing. Mine went into bios rejection melt down a number of times. Mostly in the night that impedes sleep. Produced many boot entrees which you have to remove so it boots up on a working system not one that hangs. Seems to be caused by either the user updating the drivers themselves, people say do it. Reckon it's best not to but if you do keep a very good table of what you had against what you got now, so you can unwind.

Reality to driver got introduced which it turned out was well known for not working with 24h2. That was a problematic driver update. The other one was the pesky memory integrity driver that didn't allow the unit to go into the final installation above 70%. That one was always on the machine, the first it got on there either by Microsoft iso install of allowing it to do driver updates early or I did it. Reckon it was Microsoft. Always toggle off update drivers now in the iso install. Professionals say that. There is a reason. At installation it will do the updates in anycase. The first pesky driver it then updated and works fine but didn't want to go above 30% if did before. Go figure as they say. The one what failed the memory integrity, I deleted. Works without. Was an Adobe DVD driver that had got on it at some stage.

Hi Terence,

Yes, I did run hvciscan_amd64 - with no results, right from the start.

Look what these results are:

VbsGetIssues: 0x00026040

UEFI WX Memory Attributes Table required

Failing to meet 52GB* minimum required volume size

System drive SSD required**

8GB*** RAM required

VbsIsRecommended: 0

HVCI incompatible driver scan start ...

* I have more than 52GB volume size

** My system (C) drive is a SSD

*** I have 8GB RAM

So, what gives?

Anyway, all these Microsoft Windows hurdles and hoops are moot. I have stopped updates for as long as possible, only open them once a week to check if there are other "normal" updates to install, then stop updates again. And I'll wait until Microsoft has cleaned up this unconscionable mess - rumors say, sometime in February. We'll see. How dare such a company have countless users, who have real work to do, wade through such shenanigans, is beyond me or any other common sense person.

Oh, and yes, my device is compatible with Windows 11. Is Microsoft perhaps trying to have us buy new machines? They have really sunk very, very low.

Thanks for trying to help.

H

The partner had a heart valve operation during the 9 weeks I was working on it. The heart operation was more successful than I was getting with 24h2.

It was that HVCI scan that found the one and only driver that was messing up the update. Did have that rogue driver that came in prior which a chap called Muhammed had said in a post a year earlier it was a problem... reverted that back then moving forward the HVCI solution. It had put itself in the UEFI quite a few times.

Basically Microsoft decided, so it appears, to tighten up backend security which rendered the migration for Windows 11 onto 24h2 flawed on many devices. I can't see them issuing a blanket solution without them weakening the security they were trying to tighten up on. Really that should have been done on the next generation of Windows 12 or something. Big bump in the road as it is.

Reckon TikTok users will have a rough time if Microsoft buys it 😉.

I'm pretty sure MS just wrecked my laptop.