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.

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....

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

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

The shell in Windows is the DOS box. So when you shell out and there are two ways of doing that are into the DOS box. They dont tell you that. So all your old DOS commands works, CD, DEL etc.

The Microsoft Memory Integrity Program that saved my bacon is run in the shell saving the results with the piped command ">"... obviously the youngsters think this is all new. No, old as the hills. 1980s DOS commands.

Cut my teeth on Fortran, Basic, ICL George 3 operating system. PDP 8s, ICL 1904s, IBM 360 long before personal computers and microprocessors had been invented. Mathematical modelling and scientific computing had been invented or the idea of writing code to say hello world. Did solder some systems up from board level as a hobby. Nascom something or other. Was asked to test to see whether the BBC could launch the BBC computer as a DIY kit rather than pre built. The 1980s period of training up youngsters. My old Senior Research Fellow guy from University after I started my career was doing a contract for the BBC. Not many mathematicians could solder or something like that. The Nascom people wondered how I'd got hold of a board configuration never sold, think I had a solder bridge or something. TTL logic chips of old. I'd been doing taxonomical analysis on telecomm futures with him. Teleworking v taking a flight. Big in 1970s telecommunications planning. Fibre was being field trialed in Cambridgeshire on 10 miles or something. Now it's too the home.

Listening to programmers talking on trains in an excited fashion you wonder whether to chip in. Did computer science as a minor. Hated quantum mechanics... mumbo jumbo. The minor and major was a good mix. Once computers hit modelling, computer skills with the scientific languages and knowning the mainframe operating systems used on remote terminals gave you a head start. You were programmer and operator in research units. Then ofcourse microcomputers took off and people thought they could do everything themselves....

So yes DOS skills are handy when Microsoft support people have you in the DOS box shell... but only us old timers know it's DOS.

So yes DOS skills are handy when Microsoft support people have you in the DOS box shell... but only us old timers know it's DOS.

We know it's DOS, but if we wanted to stick to command lines, we would be on Linux (that's why we elders still have multi-boot).

And I confirm it's despise and not some other mild term, for if there was a minimum of consideration, they would address the issue at least for base configurations. And it's precisely the case for one of my machines: a constructor laptop with an embedded Win10 version graded to 11 without any application on it that consistently fails to update.

Plus I'm not paid to search for a solution, while they are.

So yes DOS skills are handy when Microsoft support people have you in the DOS box shell... but only us old timers know it's DOS.

We know it's DOS, but if we wanted to stick to command lines, we would be on Linux (that's why we elders still have multi-boot).

Or try to install 24h2 and find it gives you multi boot into many versions of 24h2 which hadn't installed. Had that one. Had to delete them all. One was the original 23h2 all the rest failed installs.

No dabbled with Linux but sudo commands too much you might just as well use DOS. Still Huawei have some very good OS coming along... we might be using Chinese OS systems if Microsoft keeps messing stuff up. Probably only if you live outside America. Huawei is banned in America.