Win11 24H2 Issue

[M3TALH3AD]

None of the drivers are installing for the latest version of Win11 24H2.
I get an error during the installation process and it fails.
The normal driver from nvidia works fine but I'd rather use the cleaned up driver from this awesome tool.
Please look into this and run a test, this is happening on a GTX1080, RTX3080ti and RTX4060ti.

 

[P4-630]

I get an error during the installation process and it fails.

Screenshots?

 

[W1zzard]

I assume this is some insider build for 24H2?

 

[iaTa]

It's happening on all builds of 24H2, from 26100.1 to 26100.712 Release Preview.

Releasing Windows 11, version 24H2 to the Release Preview Channel

UPDATE 6/15: We have resumed rollout of Windows 11, version 24H2 (Build 26100.863) to the Release Preview Channel. UPDATE 6/7: We are temporarily pausing the rollout of Windows 11, version 24H2 to the Release P

blogs.windows.com

The issue is related to driver signing. If I untick 'disable telemetry' and the required driver signing, the driver installs Ok.

 

[R-T-B]

It's happening on all builds of 24H2, from 26100.1 to 26100.712 Release Preview.

Releasing Windows 11, version 24H2 to the Release Preview Channel

UPDATE 6/15: We have resumed rollout of Windows 11, version 24H2 (Build 26100.863) to the Release Preview Channel. UPDATE 6/7: We are temporarily pausing the rollout of Windows 11, version 24H2 to the Release P

blogs.windows.com

The issue is related to driver signing. If I untick 'disable telemetry' and the required driver signing, the driver installs Ok.

Sounds like fun changes coming down the pike from MS.

 

[W1zzard]

The issue is related to driver signing

Interesting .. does anyone know if Microsoft is making changes to driver signing? Seems unlikely given this is not a major release? Maybe just a bug that they'll fix at some point

 

[iaTa]

I've also tested with and without the EAC compatible method, both fail.

Is it possible to enable logging? I've tried with "setup.exe -log:"C:\NVlog" -loglevel:6" but no luck.

 

[W1zzard]

After installation, do you see the certificate in (certlm) Computer Certificates -> Trusted Publishers -> Certificates?

After installation, when you go to the install files -> Display.Driver and check the signature of nv_disp.cat, does the cert check out?

You have to at least start the installer for the certificate magic to happen, so don't just look at the generated files

 

[iaTa]

'NVCleanstall Driver Modding Authority' gets installed into trusted root certs when running setup.

nv_disp.cat shows 'NVCleanstall Driver Modding Authority' embedded signature and is shown as Ok on the details panel.

 

[W1zzard]

Then installation should work fine. Microsoft just doing Microsoft things I guess

 

[iaTa]

If I try to update manually via device manager I get a 'The hash for the file is not present in the specified catalog file' error.

From setupapi.dev.log:

Driver package INF file hash is not present in catalog file. Filename = nvltig.inf, Error = 0xE000024B
Driver package appears to be tampered, and Code Integrity is enforced.
Driver package failed signature validation. Error = 0xE000024B

 

[ColdFlo]

Yes it looks like nvcleaninstall needs an update to get around some new ms security feature blocking nvcleaninstall drivers from installing they get like a third of the way in and crash out.

 

[W1zzard]

some new ms security feature

Have you seen this documented by Microsoft anywhere?

 

[ColdFlo]

No but it seems like the security is upped when i drop my tweaks in I get a annoying bluescreen(lightblue not bsod, partial launch brick light bluescreen) on launch my tweaks are so lengthy that its gonna take a long time to halfsplit and narrow it down. Seems like sensitive registry tweaks or messing with system files may cause things to bsod or not work. It definitely feels faster, but I dont think its daily driver ready. Ive read they have cutoff all support for cpus older than nehalem because of instruction POPCOUNT says SSE4.2 and SSE2 are required now? Im about to get into all this had to reinstall 4 times now, the first install I got everything in only for it to bluescreen not of death i think its just a partial launch light blue screen on the final restart. Also it doesnt like when you delete the mcupdate dlls from system32 to get rid of those cancer cpu slowdown "spectre and meltdown mitigation" microcodes that I tweaked around to stop them from nerfing my older 4930K by 40% to force upgrades. Im not an windows internals guy but I suspect some subsystem they use for system file security has been increased if I had to guess, likely you guys could recall that faster than I can.

 

[Xteamlyer]

Have you seen this documented by Microsoft anywhere?

Maybe this?

 

[iaTa]

If I try to update manually via device manager I get a 'The hash for the file is not present in the specified catalog file' error.

From setupapi.dev.log:

Driver package INF file hash is not present in catalog file. Filename = nvltig.inf, Error = 0xE000024B
Driver package appears to be tampered, and Code Integrity is enforced.
Driver package failed signature validation. Error = 0xE000024B

It's weird, I checked the error of the hash of nvltig.inf not being present in the catalog file and it is present and valid:

signtool.exe verify /v /pa /c C:\NV\Display.Driver\nv_disp.cat C:\NV\Display.Driver\nvltig.inf

Verifying: C:\NV\Display.Driver\nvltig.inf
File is signed in catalog: C:\NV\Display.Driver\nv_disp.cat
Hash of file (sha1): 2DF5A3A3970C9F04C77FC71BBB6839D797903D91

Signing Certificate Chain:
    Issued to: NVCleanstall Driver Modding Authority
    Issued by: NVCleanstall Driver Modding Authority
    Expires:   Wed May 23 00:00:00 2029
    SHA1 hash: 0ACD206E0B4018092E24BBDD185C2059B2DDEC0E

File is not timestamped.

Successfully verified: C:\NV\Display.Driver\nvltig.inf

Number of files successfully Verified: 1
Number of warnings: 0
Number of errors: 0

 

[W1zzard]

Maybe this?

Not seeing anything relevant in there

 

[iaTa]

Unsure if this is related but I found this: https://x.com/thiojoe/status/1793694960174473464

When I check the official unmodded driver all of the inf files show a catalogue signature of 'Microsoft Windows Hardware Compatibility Publisher' and 'oem93.cat'.

When I check the modded driver none of the inf files show a catalogue signature.

EDIT: In case there was an issue installing the catalogue file I tried manually installing with signtool and the modded infs now show a catalogue signature, however installing the modded driver still fails with the same error:

Driver package INF file hash is not present in catalog file. Filename = nvltig.inf, Error = 0xE000024B

 

[commission3r]

None of the drivers are installing for the latest version of Win11 24H2.
I get an error during the installation process and it fails.
The normal driver from nvidia works fine but I'd rather use the cleaned up driver from this awesome tool.
Please look into this and run a test, this is happening on a GTX1080, RTX3080ti and RTX4060ti.

"The normal driver from nvidia works fine" the clue you missed!
I would try restarting in safe mode then disable driver signing

 

[Zorak]

"The normal driver from nvidia works fine" the clue you missed!
I would try restarting in safe mode then disable driver signing

Yes, you're right you corrected the problem ! please disable driver signing for the installation, good job !

 

[iaTa]

That's not fixing the issue, that's a workaround and I would assume not a long term solution for NVCleanstall.

The issue seems to be that that Windows is unable to see or accept the signed catalogue file or the file hashes within it.

 

[AleXXX666]

None of the drivers are installing for the latest version of Win11 24H2.
I get an error during the installation process and it fails.
The normal driver from nvidia works fine but I'd rather use the cleaned up driver from this awesome tool.
Please look into this and run a test, this is happening on a GTX1080, RTX3080ti and RTX4060ti.

patience, my friend, wait till the final, it's half a year run

 

[Nearest0858]

This was confusing me for a long time, thought I was doing something wrong since I switched to Win11 from Win10. Good to know it's not an issue with my machine, hopefully it's fixed soon! Until then I'll go back to NVSlimmer.

 

[W1zzard]

Until then I'll go back to NVSlimmer.

Just don't use options that require the driver signature to be rebuilt and it should work fine? NVSlimmer doesn't even have such a feature

 

[stimpy88]

Just switched to Win11 24H2 build 26100.1000 and just found out the hard way that this doesn't work anymore. It's a shame, I've been using it for years.

EDIT:
So it's just the driver signing that's breaking this?