Windows 11, version 24H2 won't install

i got it working but it resulted in my entire OS to be corrupted and had to reinstall the entirety of Windows 11 i can thank my friend who is a computer techsavvy to fix it.

Was 24H2 Installed Directly or via update after getting corrupted?

Was 24H2 Installed Directly or via update after getting corrupted?

Depends you you define "corrupted". I'd say and it's was my case the ~70% stop is down to the memory integrity of the drivers that have got installed on the system and they don't pass the final test of installation. That's because Microsoft changed the rules of the game of Windows 11 mid way in its development cycle of annual releases putting some users out of the game. The other one stopping earlier on is due to another issue where a driver or drivers get updated for the task either by the system or users. The latter is to follow the instruction in some posts to update all your drivers. There are faulty drivers out there that won't work with 24H2 so if you do that you end up with an early issue. That came up in the Insider programme of testers. I believe the ISO install method where it says update drivers before installation is prone to this, advisor say toggle that box off for a good reason. Repeated failed installations and dropping out can leave you stuck in boot situations and eat up system memory.

A clean install is likely to get you out of the situation since if its a memory integrity driver that's gone onto the system in the lifetime of loading up software it gets left out and so too the duff drivers that don't work with the process in the initial step . The systems website will have a set of device drivers that are clean.

That first paragraph could be defined as what corrupted it. The main issue I'd say is 24h2 installation tightening up security on "memory integrity" (program you can test for drivers on that from Microsoft and remove them) and also drivers being out there which aren't compatible with the install at the early stage. That's the two 70% and 23% circa figures.... not forgetting it doesn't like virus checking programs that aren't Microsoft’s. And yes the error codes are vague.

I've been following the discussion here for many months now about the serious installation problems with 24H2.

Two questions immediately come to mind:

1) How on earth did Microsoft have such a "disaster" with 24H2 --> reliability has completely disappeared?

**2) What happens to the huge number of ordinary users who don't have the necessary know-how or time for complicated fixes that may not even help?**💻🤔😒

I've been following the discussion here for many months now about the serious installation problems with 24H2.

Two questions immediately come to mind:

1) How on earth did Microsoft have such a "disaster" with 24H2 --> reliability has completely disappeared?

**2) What happens to the huge number of ordinary users who don't have the necessary know-how or time for complicated fixes that may not even help?**💻🤔😒

2. They are left dangling unless Microsoft reverses the memory integrity test and tightening up. That's not going to happen I don't reckon since it was a design decision, perhaps not properly thought though.

Then you had those drivers not properly tested.

1. That's 2. There is some thought that Microsoft was developing Windows 12 and what got into Windows 11 was an improved security spec that then undermined the user base since it was not compatible for some users.

Perhaps like the migration from Windows 10 to 11 they may give way on what they deem as an essential of the spec. They could say, OK let's not bother with memory integrity as far as they they have weekend their position on TPM.

Testing and QA is what has been missing and lessons learnt. You get the feeling that the right hand doesn't know what the left hand is doing. We have seen that with published positions and withdrawn on TPM. Now it's weakened again... difficult to keep up.