Monday, February 3rd 2020

TechPowerUp Releases NVCleanstall 1.3.0

TechPowerUp today released the latest update to NVCleanstall, our lightweight utility that lets you heavily customize your NVIDIA GeForce software installation, letting you choose not to install a lot more components than what NVIDIA's installer allows. You can disable installation of components you probably don't need, such as telemetry. Version 1.3.0 introduces the ability to install the NVIDIA Control Panel app from Microsoft Store without needing to log-in with a Microsoft account, for the DCH version of GeForce Software. This is particularly useful for those using the DCH version of GeForce software without wanting to log into Microsoft Store.

TechPowerUp NVCleanstall Version 1.3.0 also introduces a tweak that makes the driver use message-signaled interrupts (MSI). We have reorganized the user interface to move a large selection of advanced tweaks to their own page. As part of the driver customization process, you can make advanced tweaks in this page, or move on to building your custom driver package. We've also added the ability for you to drag-and-drop downloaded driver files onto NVCleanstall for them to be used as installer source. Lastly, we fixed background driver update check not getting disabled when its checkbox is unchecked. Grab NVCleanstall from the link below.

DOWNLOAD: TechPowerUp NVCleanstall 1.3.0
The change-log follows.

  • Added tweak to install NVIDIA Control Panel app from Microsoft Store (without Microsoft account), DCH drivers only
  • Added tweak to enable Message Signaled Interrupts
  • Tweaks section moved onto its own page
  • Fixed background driver update check not getting disabled when its checkbox is unchecked
  • Downloaded files can now be dropped onto the NVCleanstall window to automatically use them as driver source
Add your own comment

10 Comments on TechPowerUp Releases NVCleanstall 1.3.0

#2
Ed_1
Great addition "Added tweak to enable Message Signaled Interrupts "
Posted on Reply
#3
C1ff0
Thank you staff!
Posted on Reply
#4
Ed_1
I tried msi mode with driver 442.19 but it didn't enter MSI mode, IRQ still 16 had to manually enable it.
Note my GTX970 was in MSI mode when installing the driver if that matters.

How I installed driver, Run NVcleanstall 1.30, use DL method and enabled Clean install plus tweaks MSI mode option only.
Installed option next and after update close NVcleanstall window.
Check IRQ, reboot and recheck IRQ just in case.
Posted on Reply
#5
W1zzard
Ed_1
I tried msi mode with driver 442.19 but it didn't enter MSI mode, IRQ still 16 had to manually enable it.
Note my GTX970 was in MSI mode when installing the driver if that matters.

How I installed driver, Run NVcleanstall 1.30, use DL method and enabled Clean install plus tweaks MSI mode option only.
Installed option next and after update close NVcleanstall window.
Check IRQ, reboot and recheck IRQ just in case.
Can you check the value of the MSI registry key?
Posted on Reply
#7
W1zzard
Ed_1
You mean after running the update?
I enabled MSI mode after I saw it wasn't enabled.
I used a tool MSI_util_v2 to do it so I didn't see the value in reg key.
Device manager for sure shown 16 for IRQ of the card after the install.

Info on tool and reg keys it changes.
forums.guru3d.com/threads/windows-line-based-vs-message-signaled-based-interrupts-msi-tool.378044/
I tried to reproduce it. The underlying reason is that NVCleanstall will set MSISupported to 1 only when the key exists and is set to 0.
With the latest driver the key doesn't get added in the first place, so NVCleanstall can never set it to 1.

I'll implement a different approach and send you a test build
Posted on Reply
#8
Ed_1
W1zzard
I tried to reproduce it. The underlying reason is that NVCleanstall will set MSISupported to 1 only when the key exists and is set to 0.
With the latest driver the key doesn't get added in the first place, so NVCleanstall can never set it to 1.

I'll implement a different approach and send you a test build
I looked at a few other drivers reg key ID's and if I am seeing right, the whole " \Interrupt Management\MessageSignaledInterruptProperties" doesn't exist if MSI is not enabled.
It only goes to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Enum\PCI\VEN_1B21&DEV_1042&SUBSYS_84881043&REV_00\4&d432303&0&00E2\Device Parameters for example.

Edit: some do have "\Interrupt Management" key but w/o the "MessageSignaledInterruptProperties" key, so I don't see any MSISupported to 0 enties.
Posted on Reply
#9
R-T-B
Yeah, I'll own up for letting this bug through. W1zzard conscripted me for testing this feature. Given I only have a Navi now, I used my brothers system. He has set the key in the past though, so I probably got a false positive from that.
Posted on Reply