Windows 11, version 24H2 won't install

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.

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

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

I'd go along with that. Witchcraft AI isn't going to be it. Just poor testing and processes in Microsoft as evident in issues picked up by the Insider program, not acted on and the release made just the same. The backend issue of memory integrity of tightening up how 24h2 is is manufactured in the final boot isn't going to be fixed by Microsoft unless they undo the revised spec that they put in with 23h2->24h2 or they dump offending drivers from your system and tell you or alternatively you have to run that check yourself that I did when I discovered that was the cause from looking at fragments of the log file.

Others drivers in the system may cause it to stumble at the first boot which need sorting out but here again it doesn't tell you what they are unless you look at the log file. It is like the w7/w8 -> w10 upgrade there is a migration path but only with the right drivers on the machine. The latest are not always the right drivers. They tell you to update all drivers but that can be a fools errand if they are defective in the migration.

Then lastly (but probably isnt) is the beloved programs on the system Microsoft says remove. Non Microsoft virus checking programs. Get rid of those and any other fancy low level stuff.

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.

The boots and braces approach of a clean install.