Windows 11, version 24H2 won't install

Obviously many people won't be old enough for them....

Having started coding on ZX-80, I remember the 640Kb base-RAM limit once set by "guess who" on the 90's PC.
But I don't feel like going back to the DOS cave walls where we carved command lines for hours with some sabertooth fang...
What next? Configuring by hand IRQ and DMA? Setting jumpers on card plots? For "security" reasons it would be impossible anyway, for we have less and less control on low-level parameters on each new Win release... why not, but now the thing runs for years, out of nowhere, the machines get stuck loop-downloading updates that won't install and we should light back the torches and venture in DOS again, to try 40 different solutions with no garantee?

Flies can try thousands of times to pass through a window different ways, blocked by the glass 'til they die... Wow... That's maybe what Windows ment from the start: we are flies. :D

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.

Admit faults is more the one. New customers get sold working systems and hope to keep them like that. A few product design mistakes this time round probably hoping to fix them via the monthly fixes but if the basic design has clamped up security they aren't going to be fixed else it would be an insecure system. It's up to the user.

Really the basic mistake was forcing a total effectively new build install with a migration through device drivers thar allowed it. Similar to the W7/8 to W10. People muttered about buying programs which could tell you which driver needed updating to do it. Awful lot of drivers to update without assistance. In this update, you could over update the drivers so the advice to update all drivers wasn't good if you updated one with issues. I found one of those known to the Insider testers.

Then you have the ones that fail memory integrity. That check you can do to weed them out.

Lastly the programs that interfere with Microsoft procedures. Non Microsoft virus checking programs. Resistance to ditch those programs will mean you won't get it installed.

Still for those that remember Digital Research, Microsoft was always a bit quirky. You'd say typical Microsoft with loving words perhaps. Those old DOS commands you still remember come in handy to sort out 24h2 installation :). Obviously many people won't be old enough for them....

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.

The silence of Microsoft support on this subject just proves how the company despises its customers.

I am having the same problem seven months later like **** microsoft!?

I didn't think those people who said wait till May was good advice. Something Microsoft can't fix in the redesign it did in 24h2. Unlikely to give that away. Will be interesting the migration to 25h2. Expect 24h2 to 25h2 will be fine but those stuck on 23h2 will remain.