• Welcome to TechPowerUp Forums, Guest! Please check out our forum guidelines for info related to our community.

Win11 24H2 Issue

I will investigate once there's a final version for 24H2, Microsoft will break/fix/change other things until then, so it's a waste of time to do this right now
 
W1zzard said:
I will investigate once there's a final version for 24H2, Microsoft will break/fix/change other things until then, so it's a waste of time to do this right now
Click to expand...
I agree, but wouldn't it be prudent to update the software to either detect it is running on 24H2 and disable the driver signing options in the UI, or make the UI display a warning about using the driver signing button?
 
and again, new update need new update to fix them
 
W1zzard said:
I will investigate once there's a final version for 24H2, Microsoft will break/fix/change other things until then, so it's a waste of time to do this right now
Click to expand...
Thank you
I'm having the same issue with LTSC W11, build 26100.1301
 
I getting same error on 24H2 26100.1742
 

Attachments

  • Screenshot (2871).png
    Screenshot (2871).png
    892 KB · Views: 214
W1zzard said:
I will investigate once there's a final version for 24H2, Microsoft will break/fix/change other things until then, so it's a waste of time to do this right now
Click to expand...
Is the final version going to be released on the 24th of this month?
 
rematb said:
Any tips on how to disable that? I have the same problem also on 24H2 build.
Click to expand...
Settings, System, Recovery, advanced startup, restart then change startup behavior and then select disable driver disable driver signature enforcement but this don't help me with 24H2 26100.1742 still get same error
 
rematb said:
Any tips on how to disable that? I have the same problem also on 24H2 build.
Click to expand...
My solution has been to simply not select the options in NVCleanstall which trigger the necessity of having to re-sign the driver.


Personally, I'm not sure it's worth disabling security on your computer to cover the fact that Windows 24H2 seems to have come as a surprise to the makers of this utility, despite the issue persisting without change for nearly 6 months now.
 
phaolo said:
Is the final version going to be released on the 24th of this month?
Click to expand...

Microsoft started last week sending out 24H2 so we will get there but it will take time.
 
I just installed 24H2 on a test machine. Confirmed, the problem is with some digital signature that NVCleanstall updates. Will investigate further
 
W1zzard said:
I just installed 24H2 on a test machine. Confirmed, the problem is with some digital signature that NVCleanstall updates. Will investigate further
Click to expand...

Is that the setting that allows for the driver's signature to be rebuilt and work with games that have anti-cheat, or something else entirely?
 
EeK said:
Is that the setting that allows for the driver's signature to be rebuilt and work with games that have anti-cheat, or something else entirely?
Click to expand...
Read the thread dude. This problem was identified in this 2-page thread 7 months ago.
 
W1zzard said:
I just installed 24H2 on a test machine. Confirmed, the problem is with some digital signature that NVCleanstall updates. Will investigate further
Click to expand...
Have you made any progress with the investigation?
I have an HP notebook with a PCI Express slot in which I have installed a GForce 980m. Since the driver does not recognize this combination, I have to add the card.
When I do this, I cannot install the generated setup.
It doesn't matter whether I disable telemetry or not.
The problem has only occurred since I started using Windows 11 24H2 IoT Enterprise LTSC.
But since this is the only version that runs on the laptop without tricks, I can't switch to the normal version without getting update problems every year.
 
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.
 
Last edited:
StimpsonJCat said:
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.
Click to expand...
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.
 
cathal said:
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.
Click to expand...

One question does your 24H2 IoT Enterprise LTSC also have issues "Remember window locations based on monitor connection" ?

I didn't give it much thought on my L14 G2 where I been running this version for a couple of months now but it also does it :ohwell:

My freshly installed version OS Build 26100.261 have this issue which is really annoying because I am use to have my windows in the upper right corner so this here annoys the hell out of me.
 
cathal said:
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.
Click to expand...
Google this... Win 11 Boot And Upgrade FiX KiT v5.1f

I also think I heard of a solution for adding hardware support for older GPUs, but I'm not sure its still active anymore. If I find it, I'll post back.

There is nothing worse than when you have fully capable hardware artificially blocked for support... But it does get to a point when you have to just give in and bite the bullet on a new one. It's sad but true, and have been there myself.

UPDATE:
Have a watch of this...
How to Modify INF File for nVidia Driver Installation
 
Last edited:
W1zzard said:
www.techpowerup.com

[Test Build] Fix for Driver Signing on Windows 11 24H2

Please test and feedback - Attachment with beta build removed - This is now part of the public v1.17.0 release: https://www.techpowerup.com/download/techpowerup-nvcleanstall/
www.techpowerup.com www.techpowerup.com
Click to expand...
Thank You, that worked for me.
I could build a package for the latest 566.03 Notebook Driver and added the Hardware Id for my Gforce 980m

After that I could install that Package under Widows 11 24H2 (Build 26100.2033) IoT Enterprise LTSC
 

Attachments

  • IoT.jpg
    IoT.jpg
    58.4 KB · Views: 89
  • nvidia.jpg
    nvidia.jpg
    69.1 KB · Views: 79
You must log in or register to reply here.
Back
Top