Windows 11, version 24H2 won't install

It’s not published more because that’s Microsoft’s job to NOT have users do that. With all due respect, you wrote five miles of instructions and expect people to do that? There are operating systems crashing everywhere, “ Oh, let me basically rebuild my entire computer because of Microsoft’s ineptitude.” No, this is wrong. If you bought a car and the dealership told you to remove all four tires, wait 2 hours and put them back on for it to run correctly, would you do that? I appreciate your knowledge and sharing, but this is Microsoft’s mess and surely a class action suit to follow.

Depends whether you want to get 24h2 installed or sit on your hands waiting for Microsoft to fix it. They aren't going to fix it since they have changed the security model in Windows 11 during the development cycle, hence the issues across the board. For people that don't make the upgrade onto 24h2 the clock is ticking.

Now a number of people have taken this worked example and they have got off the error code and into installation. It's apparent those people on the many threads which have been tinkering with their drivers turned off the memory integrity check as the Windows text says you can (within UEFI). Obviously, the average person isn't going to do that, or you screen the drivers for memory integrity yourself using the Microsoft tool. Average person isn't going to do that either.

It's apparent not to over sweat on driver updates but check integrity if you get that far. Insider program found updated drivers that didn't work in the migration, as I found at one point.

One of the drivers identified by hviscan was for some audio capture software I use. I uninstalled the software and drivers, and then tried to reinstall it after the successful w24H2 update finished.

Nope. Windows installed the software, but declined to install that driver since it violated the Memory Integrity checks introduced in that release of Windows.

The software still seems to work without it, so I'm not too bothered. I did raise a ticket with the publishes of the software....... Their response? Just disable memory integrity checks in Windows and it should work 🫣🫣🫣

Yes I reckon that's what some people were doing that got their stuff installed. They said they had been in UEFI and disabled the backend but didn't know whether that's why it worked. If you move away from the new enforced 24h2 model you never know whether it will bite you in the future with 25h2 say. Best I reckon not to play about turning off stuff in UEFI but fix the drivers identified by HVISCAN by leaving them out. Software vendors must get their act together.

Terance ...AMEN !

👍 I do moderate a board so you get use to sifting the good stuff from the bad stuff to get the end result from advice given. Plenty of bad stuff in getting the desired result. My scientific training. This one is an example of the principle of optimality 😉. Just needs a bit of decision theory to upgrade to 24h2. Easy. 🤫 when it drops back to going wrong on the first boot you know you aren't on the right course. You need to take it through the stages. But those log files you have to get up to speed on reading them. As said eventually found the Microsoft memory driver integrity program being recommended with the text string I'd got then it fell out. Other than that either a complete reinstall which I didn't want to do.

Well thank you Geo for thanking me... once you get to that error code and you have screened for everything else that's the one to do. I found that tip in a small corner of the Internet... everybody else was just advising the same old. Memory integrity on that final boot is what it's failing on and hvciscan is like the external scan of what its tripping on. Then you do the manual Google to see what they are. Rename and purge the drivers.

In my case only one... there was no reason why it was on the machine and it works without it... it's an example of why Microsoft should not have changed the security rules on the drivers in the like of W11. Pretty clear to me that they can't automate the removal of these or if they did would have to warn after the event that these drivers were removed and you may wish to check whether you needed them 🤣. Only way they would be able to do it. However given other people's issue on other programs they would be ditching a lot.

One of the drivers identified by hviscan was for some audio capture software I use. I uninstalled the software and drivers, and then tried to reinstall it after the successful w24H2 update finished.

Nope. Windows installed the software, but declined to install that driver since it violated the Memory Integrity checks introduced in that release of Windows.

The software still seems to work without it, so I'm not too bothered. I did raise a ticket with the publishes of the software....... Their response? Just disable memory integrity checks in Windows and it should work 🫣🫣🫣