Windows 11, version 24H2 won't install

I reset my PC from the settings app. Took hours but it solved the problem. I selected the option to install from the cloud. It worked 24H2 was installed during the process.

Don't think this is the case. I spent an entire month trying to get the update installed and the only thing that worked was a fresh install. If ACPI was the issue then this would not have worked

Hi,

All the 24h2 install and compatibility issues look power management related to me. I think these are issues arising from acpi calls that 24h2 can't handle correctly with all systems, especially ai controls for atk and pm.

So, it stands to reason the biggest problems are then with devices that rely on power management features heavily.

I've seen this before with Linux systems using nvidia kernel module, but only a decade ago at the soonest.

The fix on a case by case basis might be disabling the ways in which windows can interface with the atk and acpi on board. For the system I experienced this with, it's the software from windows trying to change settings for the non-standard acpi controller. So, if you're going to keep trying to get the update 24h2 to work that might at least be a place to start.

Just... the firmware pm systems are probably several years newer than the windows code base, is all.

The problem is that we are the ones that are coping it. Not Microsoft!

Indeed. Problem is suppose to stem from staff cuts and relying on the Insider program to pick up bugs. Off the two issues I had, the bugs had been flagged up but nothing done about it. The solutions were on posts of people testing the software. All the red herrings were people posting the same old stuff with long lists of clear this that and the other.. rename etc. All of that can be done by a simple in place reset that's in 23h2, on the menus. Takes a time but quicker than all the commands.

Tightening up the backend security on memory integrity halfway through Windows 11 development isn't a good idea if there isn't a plan to pickup rogue drivers and deal with them rather than just bombing out installation without reporting the issue or dealing with it. That latter I think people got round by relaxing the backend security which defeats what Microsoft were intending to do unwisely. You see that in posts from the technically minded. 99.99% of users aren't too technically minded. Not sure of what % of people haven't been able to upgrade that wanted to. That would be an interesting figure.

The problem is that we are the ones that are coping it. Not Microsoft!