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

STRANGE!

First - read my text Dec 17 --> I successfully, without any problems updated my laptop to version 24H2 with (official) Windows 11 Installation Assistant!

I did not remove any drivers or any software.

I did not remove my "third party antivirus product" (F-Secure).

I did not edit the registry.

I did not use any thirds party tools.

And - I did not change anything else on my laptop.

How do you comment this?

Because there is a given percent that install without an issue. That's is why. I've found that figure to be a staggering 50% on fully compliant W11 hardware. That's why. That figure has obviously dropped from all past releases. Sample size of two.

It's widely known that Microsoft has an issue with 24H2. They effectively admit it with their holds on the roll out and bug reports.

My hardware was 'fully compliant'.

It was the non compliant drivers from things like a Logitech webcam, asrock motherboard and Norton antivirus that clobbered mine.

Hardly unusual.

Despite the publicised problems with specific Asus machines, and audio issues, there was little warning that things would be this difficult. And the log files once found weren't much help in pointing to t the actual cause of the issues

Because there is a given percent that install without an issue. That's is why. I've found that figure to be a staggering 50% on fully compliant W11 hardware. That's why. That figure has obviously dropped from all past release ...

If what you wrote is true🤔--> a lot of ordinary Windows 11 users will have "hard times"😒in the future if there are the same extensive (for example, installation) problems as 24H2 has now!

It comes to mind that this huge 24H2 update (which was initially planned to be called Windows 12) was TOO BIG even for Microsoft?

It's the biggest update since 2021.

It is worth remembering that there were over 1.4 billion monthly active devices with Windows 10 or Windows 11, for example, **in 2022 according to Microsoft!**🤔😮

Because there is a given percent that install without an issue. That's is why. I've found that figure to be a staggering 50% on fully compliant W11 hardware. That's why. That figure has obviously dropped from all past release ...

If what you wrote is true🤔--> a lot of ordinary Windows 11 users will have "hard times"😒in the future if there are the same extensive (for example, installation) problems as 24H2 has now!

It comes to mind that this huge 24H2 update (which was initially planned to be called Windows 12) was TOO BIG even for Microsoft?

It's the biggest update since 2021.

It is worth remembering that there were over 1.4 billion monthly active devices with Windows 10 or Windows 11, for example, **in 2022 according to Microsoft!**🤔😮

And combined with that Windows 10 users that have got to come off or else pay an annual charge, so the timing of 24h2 with its upgrade issues isn't good. Generally felt by many that it was rushed out. Still if it's really Windows 12 alot will be happy knowing their current hardware does not need to be junked once they get onto 24h2 given they got 25h2 to look forward too.😁 I trust that won't have the same update issues.

I have saved my own notes and old driver that bridged into 24h2 given they put the new one back that never worked in 23h2>24h2 🤮 . Mystery of 24h2.

Anybody with issues and sorts it out needs to make their own notes. I do each year on the unsupported hardware, I've added the supported hardware to my notes now. Such is life that Microsoft update isn't straight forward dependant on "rogue" drivers and common non Microsoft apps. Just two rogue drivers got me on one laptop. The other no issues. One unsupported tower unit no issues with the server method, The other virtual bios issue that needed to be switched back off, then an update bug that everyone had. Fixed with resetting the update and using the cumulative msi update - same issue as present for some dependent on their starting point and upgrade method.

moi c'est la meme chose tout esseyer il indique KB50488667 x800f0983 ?