Choosing ANY option that makes Cleanstall have to re-sign the driver will break 24H2 support.
If you NEED to choose an option that breaks 24H2, then you will have to stick to 23H2.
Yes, I know that. Here is some background to my problem.
My problem is that I have a well-equipped laptop that is still suitable for my games, but its I7 CPU is no longer officially supported by Windows 11.
I have been using Windows 11 in the Pro version.
But since I have to tinker every year to install the annual update, I switched from 23H2 Pro to the 24H2 IoT Enterprise LTSC version.
Then I always had to change the Nvidia driver (even under Windows 10) because I have to add the Gforce 980m with its hardware ID.
So much for the background.
My question is more in the direction of whether there is still an active search here to solve the current problem of NvCleanInstall and whether there may already be progress.
If so, I can put the laptop aside for the time being and wait for an update.
What surprises me is that disabling driver signing in Windows 11 did not help.