Windows 11, version 24H2 won't install

I think Microsoft have failed big time by not providing advance warning of the significance of the changes that 24h2 introduces.

Yes, make things more secure, yes make PCs more stable and resistant to poorly written code. But don't just drop this on us. I had to remove over 14 drivers, and six pieces of software before standing a chance of getting this to install. Oh, yes, plus removing my 'third party antivirus product' from that fringe company (Norton).

Webcam had to go.

Oracle virtualization software had to go

Ironically, I had already built a VM in virtualbox, with windows 23h2, and upgraded it to 24h2.

Registry editing. Several thirds party tools to identify rogue drivers.

Yes, this will really encourage users to move forward and keep their machines up to date with these latest releases

NOT

Ah now that's the universe behind the door I recognise 😉. Reckon it was going to be Windows 12 but they somehow decided they would keep it at 11. Suppose to be for Co-Pilot button machines or something so rushed out early without any thought. Still we must feel sorry for all those accredited Microsoft people they left standing 🤫.

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

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.

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.

Get multiple error codes - telling I have too little space (which was true, but have cleaned up and still not working) - and telling I don't meet the requirements. Your suggested program ran a check first that told I did meet the requirements, so this is also just bullsh*t.

And yes. I am sure I have 23h2. 100%. The suggested solutions on any pages does not work. I resign.