Windows 11, version 24H2 won't install

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 need destop remote support of my problem

Kapil Arya, MVP Volunteer Moderator

Microsoft MVP (Windows IT Pro), since 2014 · Windows Insider MVP, since 2016 · Windows Help (**www.kapilarya.com**)

wrote on Nov 26 ON THE SAME TOPIC PROBLEM in another discussion on this forum:

“Try upgrading via Windows 11 24H2 ISO file:

 

https://www.kapilarya.com/how-to-upgrade-to-windows-11-version-24h2#method-2-upgrade-to-24h2-from-iso-file

 

Note: Included link in this reply refers to blog post by a trusted Microsoft MVP.”

 

**That link above explains all 4 different installation (update) options VERY WELL.**🤔👍

It's step 7, not right now is the one to take if using the ISO. If you do take the updates that will be slow and introduce potential driver issues. Let the end point do the updates or tinker with the drivers outside of this. There are free library driver programs or you go to the manufacturer website.

Why it's important to see the Microsoft error code to determine which stage it's going wrong and to read the log files. How to read those log files can be found online. Those are put in different places on the drive subject to the error. Then there are summary tools.

The experts like to read those log files since they do point to issues. Question is whether there are the number of experts out there to debug all failed updates... we'll see, why you are told not to attempt the update untill you are officially offered it. That's Microsoft’s view.

I'd got to the stage where it was OK for me to use the ISO files since it started offering me the update through the update channel. Mind you by then I'd tinkered with the drivers and found the duff one which produced the failed first boot which was suppose to be an update. No don't update that driver. It was memory integrity on the 70% plus boot it was failing at, different. That Microsoft tool was the answer (Google it). My belief some people reading reports turn off the security to bypass the memory integrity check than rather sorting out the drivers that are failing memory integrity since they say, I don't know whether it worked due to that or not...

So my message from all of this is take a copy of your drivers before you start. Don't go updating the drivers on mass since that can cause more issues than solve. Beware of the Microsoft error code the ISO file gives you, but dont take the default route, use change the default so it doesnt. Use the Microsoft memory integrity tool that finds incompatible drivers that fail the final upgrade, 70% if it stops at that. Your issue may not be that, it was mine. Don't forget to ditch all non Microsoft anti virus programs before you start this.

Best of luck. Personally for the difficult equipment I can't see Microsoft finding a solution due to the way 24h2 update is engineered unless they have another suite of fix it programs they haven't released yet. Currently it's inspection of log files, Farbar and the memory integrity tool. Lot of witchcraft out there that doesn't work on the 24h2 update and you get use to reading it and going round in circles on these so called easy fixes.

Kapil Arya, MVP Volunteer Moderator

Microsoft MVP (Windows IT Pro), since 2014 · Windows Insider MVP, since 2016 · Windows Help (**www.kapilarya.com**)

wrote on Nov 26 ON THE SAME TOPIC PROBLEM in another discussion on this forum:

“Try upgrading via Windows 11 24H2 ISO file:

https://www.kapilarya.com/how-to-upgrade-to-windows-11-version-24h2#method-2-upgrade-to-24h2-from-iso-file

Note: Included link in this reply refers to blog post by a trusted Microsoft MVP.”

**That link above explains all 4 different installation (upgrade) options VERY WELL.**🤔👍

I also facing same problem

24h2 not installing

Please provide me solution

We try all thing and i am trying from last 7 days still not reslove

Please please support me

7 days that's not long at all. I was at it for 2.5 months. There are many causes why it won't install and most of the simple solutions offered don't work.

Officially you are told not to attempt the update unless you have been offered the update via the normal invitation. That can then fail which puts you in the same place whether you'd used the download screen.

There are two mains boots the first on the drivers you have got and the final boot at circa 70%. If you aren't at 70% you are well back. Where I say you end of playing snakes and ladders between the two. Once you slip back down you have to get back up. My experience was that some of the update drivers were a problem. You are told to update the drivers, don't at first and if you do keep a copy of the previous one. There are driver free tools available but they can cause more harm than good.

As far as errors are concerned you don't see the full error code untill you use the ISO method but Don't take the recommended option to update the drivers in that since it can introduce problematic drivers. You need the error codes to place you where you are when it failed. Snakes and ladders bit.

The log files if read correctly will help. The final boot at 70% plus is where the memory integrity test is applied on the drivers. There is a separate tool which will tell you which drivers may fail this. If hitting above 70%, failing and it's a possible driver issue then well worth running the memory integrity tool. I just had one driver than failed this that caused me two months of grief... just one duff driver that wasn't being used but the software

As far as I can see what Microsoft has done is reverted the update to how it was in Windows 7/8 to 10. Drivers had to match to cross that bridge then the added complication is memory integrity on the drivers. Old ones without the appropriate security won't pass beyond 70%.

You must also remove all anti virus software other than Windows Defender and any other low level non Microsoft smart software for doing clever stuff. That's bound to fail. It will trip up on that. The log files if read correctly point that out. That's what the Microsoft help experts find on here when you share your log files if it comes to that.

Farbar tool is the other one the experts like you to run. You eyeball the output. It was at that stage I concluded it wasn't a rogue program but some driver that was proving impossible to find.

The cyclical stuff you read to do made no difference. They all say the same. Stop this service, start this service. Clear this, clear that.

After all of this 24h2 will update your drivers.