Windows 11, version 24H2 won't install

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

I installed the big 24H2 update on my computer (HP 470 G9 laptop, Windows 11 Pro).

It failed several times at first, when I tried to install it in several different ways!

Here are the different steps:

1) It originally appeared for download on Windows Update on Nov 22. I tried to download it 2 times – the download always stopped at 8%

2) It appeared again on Windows Update on Dec 15. Now the download and installation proceeded to the end – but then the installer started automatically undoing the changes made to the computer --> reverted back to v. 23H2

3) I then tried installing from the ISO file --> failed (for some reason it reported a problem with the installation language (?) --> could not select the option at all: “Keep my files and apps”

**4) The update finally went well and without any problems with this method:**💻👍👍

Windows 11 Installation Assistant

I would like to emphasize that this is one of the three official installation methods recommended by Microsoft!

Microsoft: This is the best option for installing Windows 11 on the device you’re currently using.

---

https://www.microsoft.com/en-us/software-download/windows11/

 

Note! It is important to note that in order to proceed the installation process, everyone must first pass the WindowsPCHealthCheck (which can be launched from the link at the top of the downloaded Windows 11 Installation Assistant -application window)

HERE IS A GOOD YOUTUBE VIDEO OF USING THAT! I hope this will help somebody:

https://www.youtube.com/watch?v=xxr2fkOKfm0&ab_channel=Pureinfotech

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.

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.**🤔👍

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.