getting errors installing on 24h2 IoT Enterprise

[cerulliber]

win11 24h2 IoT Enterprise all updates installed
downloaded latest whql driver from nvidia
uset settings here
My settings to fix CS2 performance issues and have a smooth gameplay. (Nvidia Cards ONLY) : r/cs2 (reddit.com)
managed to created driver with recommended settings on select components to install screen, but install failed.
ended up only with settings remove telemetry and rebuild digital signatures.

 

[johngalt]

Interesting. I just upgraded my (home) work PC to 24H2 by (re)joining the IP program and installing it - and an NVCleanStal-derived driver package for 560.94, which installed perfectly fine on stable Win11 (22631.4037) yesterday, failed today to install on 26100.1586. I use many more customizations, though, via NVCS, than mentioned in the Reddit post, but these settings have served me well for a couple of years at the very least.

With my attempt on 24H2, only the stock nVidia driver package would install. I suspect it is the "Unsigned driver" warning, as it never showed, and my install eventually left me with no display access to my machine, forcing me to manually restart, which then loaded the cruddy Win11 default nVidia driver 46x.xx, which won't even recognize multiple monitors. Installing the stock nVidia package fixed my multi-mon issue, but the modded driver package from NVCS is still failing.

If I can provide logs of any type, please let me know. I also have 4 previously created packages I'll try tomorrow, including:

560.81
560.70
556.12
552.44

Again, all packages were built from their respective stock nVidia packages using the exact same options and settings, so I can see if itis a driver issue or if it is a modding issue.

 

[AsadAlrafidain]

I also can't get the driver modified by nvcleanstall to install on 24h2 preview (fresh install), but I don't get any error, the process is silently terminated.....I hope this will change when they release the final version.

 

[johngalt]

After today's (24H2) update, I'm gonna try again. Wish me luck!

 

[AsadAlrafidain]

After today's (24H2) update, I'm gonna try again. Wish me luck!

is it the official release ? or still preview ?

 

[johngalt]

Still preview, just was an update. https://support.microsoft.com/en-us...100-1742-407666c8-6b6d-4561-a982-abce4e7c2efb

I tried with both NVCleanStal'd drivers 560.94 and the new 561.09 - still failed to install, and reverted to the old 460.xx 472.xx (OEM) driver again. This time, though, after a while the old OEM driver not only engaged, but I had my display back, without needing to force a reboot. Had to run the regular installer to get 561.09 installed.

 

[VekyTP9]

I install new driver too on 24H2 Win 11 with A5000 getting error no matter of version. I try old working (in past) NVCleaninstall driver package show error too

I try it on release preview of 24H2 26100.1742 which seems to be final build soon.

 

[johngalt]

This is obviously a problem with 24H2 specifically, for now, so we'll have to wait and see what happens when 24H2 is officially released.

I suspect that if it continues to be a problem after that, then we may see a new version of NVCleanStal. But I certainly do understand why nothing can (or, really, should) be done about it right now.

 

[W1zzard]

If it's in 24H2 final, then I'll update NVCleanstall of course, but wasting time on the beta and the final might be different seems like a bad idea

 

[RJARRRPCGP]

I don't know if 11 24H2 is ready or not and prefer to not be forced to reinstall 11 Pro 23H2 on my daily driver.

 

[johngalt]

If it's in 24H2 final, then I'll update NVCleanstall of course, but wasting time on the beta and the final might be different seems like a bad idea

Exactly. I came here to report a potential problem, and am not all that worried about it, as I am more worried about having my extensive set of options changed if I try experimenting further to figure out if it is a specific option that is causing the issue or not.

If there is a way to save my current config for advanced options that I can later restore to use as my default config (using that button at the bottom), I'm willing to play with it on my end to see if I can narrow it down a bit. I mean, I know I can take screenshots and refer to those, but I'd rather not take the chance of messing something up lol.

I don't know if 11 24H2 is ready or not and prefer to not be forced to reinstall 11 Pro 23H2 on my daily driver.

I don't think it is out officially yet, and I believe thee last I Saw was next month some time, but you can always Google methods to stay on the current build tree, I believe there is an easy method in Group Policy to select branches (versus builds) to continue to stay on.

 

[johngalt]

New nVidia driver out, as well as official release of 24H2 today. I'm going to try NvCleanStall on the new driver using my old settings and my upgraded 24H2 install. I'm also considering cleanly installing 24H2 now that I have an official ISO from Microsoft, and may try to use the NVCStall-derived installer on it after, to see if it still breaks or not.

 

[johngalt]

Still broken, though there is a plot twist - instead of reverting to a really old Windows-11 compliant driver, this time it reverted to 560.94, though, since this is from Windows, not directly from nVidia, it still would not recognize my multiple monitor setup.

Had to manually install 565.90 using the regular nVidia installer.

 

[W1zzard]

I'm also considering cleanly installing 24H2

I'll be gone this week, but that's on my list for next week. Clean 24H2, verify NVCleanstall is working correctly, and fix if it's not working

 

[johngalt]

No rush - 24H2 just came out lol.

If I get a chance to clean install before you get back, I'll report back with my results.

 

[jUNiORCS]

Hello, i just found the issue.

Dont select "Disable driver telemetry", thats the option causing the issue to fail the installation.
I enabled everything else as the reddit post.

 

[johngalt]

Nice. I'll build a new version on the current drivers and test it out.

 

[AsadAlrafidain]

Hello, i just found the issue.

Dont select "Disable driver telemetry", thats the option causing the issue to fail the installation.
I enabled everything else as the reddit post.

It works.. but isn't disabling driver telemetry one of the major reasons we are using nvidiacleanstall?

 

[johngalt]

Agreed. It does work if that one setting is disabled.

At the same time, I'm with Asad. I suspect Wizard will need to take a look at the coding as well as the pre-reqs for the nVidia drivers, as nVidia may have changed something that conflicts with that setting, or else Windows 24H2 changed something about the installation parameters that blocks anything that tries to undermine telemetry.

I really suspect that last one, as Win11 is notorious for its own telemetry also. It wouldn't surprise me if they have coded the OS to not allow telemetry blocks in some way, manner, or fashion, for their own data collection, and it tangentially affects other installations like nVidia's driver package.

At any rate, though, I'm still able to run a cut-down driver package again, so I'm a lot happier now lol.

 

[VekyTP9]

It works.. but isn't disabling driver telemetry one of the major reasons we are using nvidiacleanstall?

Agreed. It does work if that one setting is disabled.

At the same time, I'm with Asad. I suspect Wizard will need to take a look at the coding as well as the pre-reqs for the nVidia drivers, as nVidia may have changed something that conflicts with that setting, or else Windows 24H2 changed something about the installation parameters that blocks anything that tries to undermine telemetry.

I really suspect that last one, as Win11 is notorious for its own telemetry also. It wouldn't surprise me if they have coded the OS to not allow telemetry blocks in some way, manner, or fashion, for their own data collection, and it tangentially affects other installations like nVidia's driver package.

At any rate, though, I'm still able to run a cut-down driver package again, so I'm a lot happier now lol.

I think that rebuilding also trigger problem with install not just telemetry at least for us who relay on rebuild because I add support for RTX A5000 to Game Ready Drivers + PhysX and Optimus
PCI\VEN_10DE&DEV_24B6&SUBSYS_22DD17AA

So I must wait for fix

 

[VekyTP9]

It works.. but isn't disabling driver telemetry one of the major reasons we are using nvidiacleanstall?

I think main reason why we need and using nVidiacleanstall is add support of unsupported devices into driver (old GPU or professional to NEW Game Ready Driver)

 

[AsadAlrafidain]

I think main reason why we need and using nVidiacleanstall is add support of unsupported devices into driver (old GPU or professional to NEW Game Ready Driver)

I guess to each his own reason

 

[johngalt]

My use is simple - get rid of the unnecessary stuff, and enable some tweaking features.

I just updated to 566.03 using NVCS with that one option disabled, and it installed fine in 24H2.

 

[AsadAlrafidain]

My use is simple - get rid of the unnecessary stuff, and enable some tweaking features.

I just updated to 566.03 using NVCS with that one option disabled, and it installed fine in 24H2.

I did the same, but noticed that nvidia control panel wouldn't open, so I'm reverting to using untouched drivers for now....can you see if nvidia control panel is working for you?

 

[johngalt]

It's the first thing I do, because I opt for a clean installation, so I have to go back and set the resolution options from default to NVIDIA color settings. Didn't have an issue.