Windows 11, version 24H2 won't install

... I decided to try using Windows11InstallationAssistant.exe again (JariVolanen indicated it worked, but he moved from Win11 Pro 23H2 to 24H2. I have Win11 Home 21H2 and, of course, different hardware and software.) After fifty minutes, I got the prompt "Undoing Changes," like I have in my previous attempts.

After this failure, I decided to run WindowsPCHealthCheckSetup.msi again (today's download from Microsoft shows it was created 10/23/24). Now I get the prompt:

"You’ll need Windows 10, version 1803 or later to install this app."

Control Panel>System shows I have Windows 11 Home...

I'M NOT SURE (?), but I remember reading somewhere: **In order for 24H2 to install, you need to have 23H2 installed on your computer.**🤔

Again, with all due respect, no one should have to do that. All these backward, mystery solving, multi stepped processes only prove that Microsoft and its update are useless. Do this, then do that, then take this, then take that, now do this etc. No. Microsoft has caused unknown damage to millions of computers with no explanation and surely no help. They must be held accountable. It is completely unacceptable to attempt to fix their update. If it was not ready, it should not have been released. It’s a marketing ploy to get people to buy new systems. Inexcusable.

Windows 11 Installation Assistant

I would like to emphasize that this has been for a long time (years) one of the three official installation methods recommended by Microsoft!

Well if you misuse the ISO method and do the "recommended" it updates the drivers then and there and the motto is don't upgrade drivers if your system is working fine. That needs changing to you might need to, but if you do duff drivers may bring you down on the first boot.

Problem with the Windows installation assistant is that it's a slower process than using the ISO. You don't get the error codes out of it but neither with the official Microsoft invite. The two are basically the same. The ISO pulls down the update whilst the variation on the ISO stops you having to answer that language question. Got well versed in this, in that nine week period.

Best to take the official invite if offered. Failing that the installation assistant, if that fails try the ISO for the error code. Then you are in too the logs and Farbar or whatever its called. That identifies non Microsoft anti virus programs. Get rid of them. At that stage knew it was a driver issue and the question of which one. That's when I found that Microsoft utility which pinpointed it.

Again, with all due respect, no one should have to do that. All these backward, mystery solving, multi stepped processes only prove that Microsoft and its update are useless. Do this, then do that, then take this, then take that, now do this etc. No. Microsoft has caused unknown damage to millions of computers with no explanation and surely no help. They must be held accountable. It is completely unacceptable to attempt to fix their update. If it was not ready, it should not have been released. It’s a marketing ploy to get people to buy new systems. Inexcusable.

Windows 11 Installation Assistant

I would like to emphasize that this has been for a long time (years) one of the three official installation methods recommended by Microsoft!

Again, with all due respect, no one should have to do that. All these backward, mystery solving, multi stepped processes only prove that Microsoft and its update are useless. Do this, then do that, then take this, then take that, now do this etc. No. Microsoft has caused unknown damage to millions of computers with no explanation and surely no help. They must be held accountable. It is completely unacceptable to attempt to fix their update. If it was not ready, it should not have been released. It’s a marketing ploy to get people to buy new systems. Inexcusable.

Don't thinks it's marketing, Microsoft management don't understand their products. Reckon Windows 11 24h2 is really Windows 12 24h2. They got everybody bouncing over the tracks into something that was suppose to be a totally new product but hasn't been thought though, the migration. They tightened up on driver and app security which is causing the issues.

It's like they can't decide whether you can put Windows 11 on a non compliant machine. Internally they are squabbling with each other like a college computer class... as it happens Windows 11 24h2 runs dandy on old hardware, it's the new hardware and drivers it fails on since its using the security features of the chipset. Some people on compliant hardware have turned off these features to upgrade but you are told not too. It could get you next time round. That's probably Windows 12 where you'd have to undo the fudge. Best to keep to the features of Windows 11 and sort the drivers out in the upgrade and non compliant programs than fiddle with the security settings.

I downloaded and ran hvciscan_amd64.exe. It identified seven drivers that "failed with compliance failure mask 00000202."
ssudcdf.sys

mbtusbser.sys

ctaud2k.sys

PxHlpa64.sys

rzpmgrk.sys

tifsfilt.sys

timntr.sys

I found details on each (description, company, version, date created, size, and multiple directories) for each and .inf files for five. I was able to delete an older version for ctaud2k.sys, but trying to delete any others said "File Access Denied: You require permission from SYSTEM to make changes to this file." I'm very reluctant to try removing the drivers or any .inf files since some are for Creative, Razer, and Acronis, all of which I use (I keep them all up-to-date). I don't recognize the names or companies for several, but that doesn't mean they aren't in use behind the scenes.

It seems strange, but after I deleted the older ctaud2k.sys, I tried rerunning hvciscan_amd64.exe (as an admin using PowerShell or Cmd) again and got the message "This app can't run on your PC. To find a version for your PC, check with the software publisher." After I rebooted, it worked and gave me the same results.

As suggested by Rodrigo.Queiroz, I also ran Disk Cleanup (Start menu, select Run as administrator) and deselected all options except "Device driver packages." It didn't seem to make any difference in the upgrade, but after rebooting, I haven't encountered any problems as a result.

Each of those apps sound like like candidates for messing the system up. You'd uninstall the apps, then re-innstall once you got into 24h2. Least it's identified something for you to go on and you are now getting some help to take it forward. The rest of the stuff is witchcraft on stop net this that and the other. It's not that, disk clean up is similar. It's the non compliant candidate drivers in the second boot that, that app reports.