Windows 11, version 24H2 won't install

This is a community forum which is a user-to-user support space. Microsoft does monitor the forum. Some guidance and occasional official responses are provided. Also to identify any emerging issues. But in the scheme of things, they see the issues being created as “minor distractions.” I think despise is too strong a word. I think “don’t care” is a better description.

It's ridiculous that end users are forced to jump through these sorry if his just too run the update to the new windows version. Microsoft really need to sort this out

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

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

Funny that is some people say there are no problems... a break through from an alternative universe... it happens.😉

The secret I reckon is not to go mad with driver updates because if you do you don't know what issues you are creating yourself. It's to gauge where you are on the update when it bails out. Only the ISO method gives you those Microsoft codes and Don't take the suggested updates. Toggle that off. That's the preferred method. Then you got those two main boots. 30% and 70%. If you don't get beyond 30% then yes you do need to tinker with the drivers. 70% is where the new action starts. The latter is where the memory integrity of the drivers can cause it to stumble. That was my issue.

There seems to be too much of update all drivers etc before you start. There are drivers that are newer that don't work with 24h2. Been there, done that. Found by an Insider person. Had to wind that back.

The fun thing about all of this is when it's successful it will / may update all the drivers including in my case the one that doesn't work from 23h2 to 24h2. Weird.

There is a chart that shows the stages of the Windows update process. It's placing yourself in that, that's important, dropping back, you got to sort out what you did and move forward. The restore windows 23h2 seems to fix everything so all the netstop, restart stuff you don't have to do. That's just parroted across the net.

Some people fiddle the TPM stuff, the security for the final boot. I didn't touch that on the basis I didn't want to move the system away from a fully compatible Windows 11 machine. You do see people doing that...but as said they don't know whether that did the trick - they say that. Indeed a few don't know how they got it working in the end.

Important stuff is to ditch non Microsoft virus programmes. Fancy drive utilities and the like. If all fails restore the manufacturers drivers if you haven't taken a copy of them before you start. Then start again. You have to work carefully.

One laptop I had updated first time, it was the other that gave the nine week run around when in reality it turned out to be just one non compliant driver that failed the memory integrity test in the final stage that can be checked with the Microsoft memory integrity driver test utility. A few Googles to find out how to remove the driver from the system having established it wasn't required. Strangely few "experts" talk about that tool. I stumbled on it with a fragment Google of the error log and yes... when someone said you need to run the said tool. Part of the Insider program.

They only had 8 bit computers when I started and a PDP8 running Focus but things have come along. 🤣 BTW Anybody in the UK can re live their associated computer life at Bletchley Park, side computer exhibition where the hardware is displayed. There is an ICL2900 which represents the death of British mainframe... as the world moved on. You got to love core memory. Ofcourse you got the Brits claim of inventing computers on cracking German war time codes. Hence the side exhibition of the British Computer Society.

Hi,Fonzeh

Hello, thank you for your reply and feedback, can I ask you very much encountered in the in-place upgrade any error report can be shared here.

In addition, you can check the installation error message: C:$WINDOWS.~BT\Sources\Panther\setuperr.log file to see if there is any specific error message.

Best regards

Bobhe | Microsoft Community Support Specialist