Windows 11, version 24H2 won't install

i need destop remote support of my problem

i need destop remote support of my problem

Another Microsoft mistake came up yesterday to add to the many. Yep, unless you get someone to read your log files, become an expert on reading them and / or run the utilities, the game changed with 24h2 update it isn't like the previous.

It's not a question of you do it this way or that way since when it fails it fails big time and you get left to pick up the pieces. Why people are saying leave the update to April 2025 after the dust has settled although I can't see that's the solution for everyone. There will be the issues where the drivers are not currently written and debugged correctly, why another three months is being added so people leave it alone. Microsoft can get it's act together.

It's the spurious drivers that aren't being used or could be being used that need picking up and being delt with that fail the memory integrity check that wasn't enforced before but is now in 24h2. That's your problem and that's where historic support fails since it doesn't cover that.

Going to be difficult for Microsoft to deal with those, why you get vague error report codes since the software isn't reporting them very well. You can watch all the recent YouTube videos, they don't have solutions. Safe boot. Split into Microsoft / non Microsoft drivers etc. That one never found my issues. There is even one from Microsoft help page on the continues splitting algorithm. That's Operational Research type of approach. My issue was deemed a Microsoft drivers at fault but I'd have to dice and slice each driver and untill the machine refused to boot. Didn't do that.

Another one where they tell you to remove bits of hardware till you identify the issue. Tricky on a laptop. Didn't do that.

At the end of the day it needs utilities to screen the installed drivers or programs or the update to junk drivers and programs which will fail installation and tell you why they were excluded. Current situation it stops and rolls back.

The situation is like the update from w7 / 8 to w10 with getting the drivers to match but with the new enforced memory integrity at the backend, if that fails security then the whole lot fails. That's my take on this process now. The new enforced security of 24h2 leads to the issues why it was never a problem before.

The Insider programme had picked up these issues but they haven't been resolved. The issue reported that some people were stuck on beta releases and couldn't get off it onto the next release. Ours we can't get on the production release. Once installed, it works well.

If you can't resolve it yourself you need someone to read your log files and they will request the whole lot and the farbar run. I got up to speed on reading the log files. But the memory integrity tool not talked about I stumbled on googling bits of my log file, it worked for me, finding a pesky DVD driver that was incompatible. It only found one driveevand that was it labelled up as Adobe. Removed and installed without any issues 9 weeks later from starting on the mission. Posted up Insider experience with 24h2 was the key from others which problem solved an updated 24h2 driver that never worked, I went back to an earlier release as they had said. That was a duff 24h2 driver which failed at the first boot. The second was the Microsoft memory integrity screening tool which had been recommended to others. That did the trick to identify the pesky driver.

I'm just an ordinary computer user, but I do have about 30 years of experience with Windows operating systems.

Now I have to admit that I don't understand your long texts and very complicated instructions.

**Do you really think that an ordinary user can / is able to implement those and would have enough time for such "experiments"?**🙄🤔

In this context (look my text yesterday), I wanted to highlight a qualified MVP Volunteer Moderator (Kapil Arya) I found, who has **10 years of experience as a Windows expert + he keeps Windows Help.**💻👍

The instructions he gives are easy to understand, logical and contain a lot of pictures.

As a small detail, it can be mentioned that on the shared link under "Method 2: Upgrade to 24H2 from ISO file" also provides instructions on how to use the lesser-known Rufus application **(Create a Windows 11 bootable USB using Rufus).**👍

I'm just an ordinary computer user, but I do have about 30 years of experience with Windows operating systems.

Now I have to admit that I don't understand your long texts and very complicated instructions.

**Do you really think that an ordinary user can / is able to implement those and would have enough time for such "experiments"?**🙄🤔

 

In this context (look my text yesterday), I wanted to highlight a qualified MVP Volunteer Moderator (Kapil Arya) I found, who has **10 years of experience as a Windows expert + he keeps Windows Help.**💻👍

The instructions he gives are easy to understand, logical and contain a lot of pictures.

As a small detail, it can be mentioned that on the shared link under "Method 2: Upgrade to 24H2 from ISO file" also provides instructions on how to use the lesser-known Rufus application **(Create a Windows 11 bootable USB using Rufus).**👍

I got 54 years of computer experience so beat you two. The ISO method or Rufus is not going to solve your issues if you get them. It's not the installation vehicle but the floored product at the minute which is widely known. 24h2 installation issues are not like any previous version of Windows since it's gone further down the road of Windows 11 secure installation. It's a reset of the installation plus added security. You can use any method in the upgrade but if it fails it's roll your sleeves up time to look at the detailed logs and utility programs or pass them onto a Microsoft expert in reading log files, farbar and other utility analysis. All the other help methods published don't help since they are based on previous Windows and they aren't the issues. The Insider posts on 24h2 are useful if you can find them. Often they say... these should not be published here. Hey, ho, that's the good stuff.

If you look at all current YouTube video they all say don't touch Windows 24h2. Yesterday's Microsoft post was they had screwed up the cumulative update of 24h3 so if you had updated prior to December and you don't have the December update... it's not going to update under certain condition of the ISO method to install 24h2. Great. The catalogue msi method does if you know the code of the cumulative update.

BTW I got two degrees in mathematics, pure and applied, management scientist.

Hi everybody (and that's a lot) and to whom it may really concern:

This is getting ridiculous. Everybody has the same problem, has tried the proposed "solutions" - and has suffered the same lack of results. I have been computing since 1981, including programming in Cobol and Pascal, and have never experienced something like this. In my case, the dreadful situation of Windows 24H2 getting stuck on installation (at best!) is compounded with other updates (mainly of 9 Intel drivers) remaining stuck at 0% download because the accursed unwillingness of the Windows 11 24H2 update seems to be blocking everything when one dares to install everything at once. I found a roundabout for the Intel installs by doing them one by one (imagine the time-consuming hassle). In short, a super mess. As many harassed users have exhorted Microsoft, to do something to correct this untenable situation.

Best,

HK