nVAppAppApp - workaround NVIDIA DLSS4 whitelisting

nVAppAppApp.ps1

<# Workaround for NVIDIA's DLSS4 whitelisting
DLSS4 was launched alongside the RTX 5000 series and comprise several new and interesting
features, f.e. additional presets for Super Resolution, using a newer Transformer model.
Arguably these features increase image quality significantly. To various degrees these 
features are also available for older RTX cards, and older games using DLSS3/2.

Using third party apps like DLSS Swapper etc remains a convenient way to, on a manual basis, 
swap out DLLs which contain the above mentioned functionality, per game. Downsides to this is 
primarily that swapping out DLLs for online multi-player games may trigger an Anti-Cheat
system, and there is of course also some manual work of updating to newer versions/DLLs.

With the launch of DLSS4 nVidia has taken steps to integrate some functionality in their 
NVIDIA App to also let the user "swap" DLSS versions manually. This is in theory nice as it 
allows for games to automatically be updated to the latest and greatest by driver updates.
Plus, it means that DLLs aren't actually "swapped" since it is done by a dynamic loading 
mechanism, which shouldmean that DLSS versions CAN be switched for (many) online multi-
player games.

BUT their implementation is too restrictive.

You may have noticed how DLSS4 needs to be enabled on a per game basis in NVIDIA app, and 
also how the feature can not be enabled for all games using DLSS3/2. This is because 
nVidia decided to implement the features using a whitelisting mechanism. I.e. the feature 
can only be enabled on games deemed "supported" by nVidia. There are actually good reasons for 
nVidia to implement a whitelisting system, for example to ensure that DLSS4 provides a good 
image quality in "supported" games, and to avoid potentially triggering Anti-Cheat systems
for online multi-player games. 

Using nVidia Profile Inspector, and similar tools, it is nevertheless possible to set the 
global profile, or per game, to use the updated DLLs and thus force DLSS4 features on all/
select games. However NVIDIA App is actually rather controlling about this and will reverse 
these changes for "unsupported" games when the app is launched or when an unsupported game 
is launched.

A workaround currently is to not install NVIDIA App, and instead use nVidia Profile Inspector. 
But I personally find the overlay and RTX HDR worth keeping NVIDIA App installed for. It may 
eventually also become mandatory to have installed.

Going through some hoops it is fortunately possible to override the whitelisting and keep 
NVIDIA App installed. The script below is a powershell (v5.1+) script which the user should 
run once, and then potentially before driver (re-)install to allow the driver installer to 
update a write-protected file (fingerprint.db). 

So what does the script do:
A) Present the user with a menu with three options:
   1. Driver upgrade - run this before updating nVidia driver and follow instructions
   2. Run script - same functionality as previously (patch files)
   3. Quit - Exit the menu and quit the script
   
Both options 1 and 2 will do the following:
1) Remove "ReadOnly" property on two files. 
 - ApplicationStorage.json which contains  the settings for detected games on the system 
 - fingerprint.db which is the origin file for all override settings
2) Modify the files to remove the override restrictions put in place by NVIDIA App.
3) Set the origin file (fingerprint.db) to "Read Only"
4) Restart two nVidia services <- this require admin rights for the script. Otherwise you 
need to restart the computer for it to take effect.

PLEASE NOTE THE FOLLOWING! 
1) This script should run as administrator to be able to restart two nVidia services
2) This script will/may allow for updating your online multi-player game's DLSS versions 
which may or may not trigger Anti-Cheat systems. I tried it with Space Marines 2 
successfully (totally worth it) but YMMV. 
3) The screen will blink/black out twice when the services restart
USE AT YOUR OWN DISCRETION! Be careful with online multi player games with Anti-Cheat systems!

ADDITIONAL NOTE ON HOW TO RUN POWERSHELL SCRIPTS (added 2025-02-25)
By default an unsigned script (like nVAppAppApp.ps1) downloaded to your local machine can 
not be executed - for security reasons. It is possible to workaround by starting powershell 
with a temporary bypass or by setting a permanent override. To do a temporary workaround 
you would press WIN+R to get the Run-dialog and execute:
`powershell -executionpolicy bypass`
To set a permanent override you type "powershell" on the start-menu, right click and select 
"Run as administrator" and once you are at the PowerShell command prompt execute:
`Set-ExecutionPolicy unrestricted`
In either case you now have a PowerShell prompt open that can/will run the script.
 Version 2
  - UTF-8 w/o BOM
  
 Version 3
  - Modify the override origin file (fingerprint.db)
  - Changed modus operandi - run the script after reinstalling driver
 
 Version 4 (2025-02-25)
  - No change to the actual script. It works good and the effects seem to persist even 
  through driver installs.
  - Added notes on how to allow PowerShell to run local scripts
  
  Version 5 (2025-03-10)
  - Added a user friendly menu with three options. 
    1. Driver upgrade. Run the script before installing a new driver and follow the isntructions. 
    2. Run the script (same functionality as before)
    3. Quit  
#>

#Requires -Version 5.1
$AppStorageJsonPath = "$Env:USERPROFILE\AppData\Local\NVIDIA Corporation\NVIDIA app\NvBackend\ApplicationStorage.json"
$FingerprintPath = "$Env:USERPROFILE\AppData\Local\NVIDIA Corporation\NVIDIA app\NvBackend\ApplicationOntology\data\fingerprint.db"
$Utf8NoBomEncoding = New-Object System.Text.UTF8Encoding $False

#region Initial Checks
function Check-AdminRights {
    $currentPrincipal = New-Object Security.Principal.WindowsPrincipal([Security.Principal.WindowsIdentity]::GetCurrent())
    return $currentPrincipal.IsInRole([Security.Principal.WindowsBuiltInRole]::Administrator)
}
$isAdmin = Check-AdminRights
if (-not $isAdmin) {
    Write-Host "`nWARNING: Not running with administrator privileges" -ForegroundColor DarkRed
    Write-Host "Service restarts will fail. To ensure full functionality:" -ForegroundColor Gray
    Write-Host "Right-click PowerShell and select 'Run as administrator'`n" -ForegroundColor Gray
    Start-Sleep -Seconds 5
}
#endregion

function Show-Header {
    Clear-Host
    Write-Host "`n"
    Write-Host "========================================================" -ForegroundColor Green
    Write-Host "        NVIDIA DLSS4 Whitelist Workaround Script        " -ForegroundColor Black -BackgroundColor Green
    Write-Host "========================================================" -ForegroundColor Green
    Write-Host "`n"
}

function Run-Script {
	# Remove Read-Only from both files
	Set-ItemProperty -Path $AppStorageJsonPath -Name IsReadOnly -Value $false
	Set-ItemProperty -Path $FingerprintPath -Name IsReadOnly -Value $false

	# Modify ApplicationStorage.json
	Write-Host "`n Modifying ApplicationStorage.json..." -ForegroundColor White
	$contents = (Get-Content $AppStorageJsonPath )
	$contents = $contents.Replace('"Disable_FG_Override":true', '"Disable_FG_Override":false')
	$contents = $contents.Replace('"Disable_RR_Override":true', '"Disable_RR_Override":false')
	$contents = $contents.Replace('"Disable_SR_Override":true', '"Disable_SR_Override":false')
	$contents = $contents.Replace('"Disable_RR_Model_Override":true', '"Disable_RR_Model_Override":false')
	$contents = $contents.Replace('"Disable_SR_Model_Override":true', '"Disable_SR_Model_Override":false')
	[System.IO.File]::WriteAllLines($AppStorageJsonPath, $contents, $Utf8NoBomEncoding)
	
	# Modify fingerprint.db
	Write-Host "`n Modifying fingerprint.db..." -ForegroundColor White
	$contents = (Get-Content $FingerprintPath )
	$contents = $contents.Replace('<Disable_FG_Override>1</Disable_FG_Override>', '<Disable_FG_Override>0</Disable_FG_Override>')
	$contents = $contents.Replace('<Disable_RR_Model_Override>1</Disable_RR_Model_Override>', '<Disable_RR_Model_Override>0</Disable_RR_Model_Override>')
	$contents = $contents.Replace('<Disable_RR_Override>1</Disable_RR_Override>', '<Disable_RR_Override>0</Disable_RR_Override>')
	$contents = $contents.Replace('<Disable_SR_Model_Override>1</Disable_SR_Model_Override>', '<Disable_SR_Model_Override>0</Disable_SR_Model_Override>')
	$contents = $contents.Replace('<Disable_SR_Override>1</Disable_SR_Override>', '<Disable_SR_Override>0</Disable_SR_Override>')
	[System.IO.File]::WriteAllLines($FingerprintPath, $contents, $Utf8NoBomEncoding)

	# Set fingerprint.db to Read-Only
	Set-ItemProperty -Path $FingerprintPath -Name IsReadOnly -Value $true

	# Restart services (requires admin rights)
	if ($isAdmin) 
	{
		try {
			Write-Host "`n Restarting NVIDIA services..." -ForegroundColor White
			Restart-Service -Force -Name "NVDisplay.ContainerLocalSystem" -ErrorAction Stop
			Restart-Service -Force -Name "NvContainerLocalSystem" -ErrorAction Stop
			Write-Host "`n Services restarted successfully" -ForegroundColor Green
		}
		catch {
			Write-Host "`n ERROR: Failed to restart services" -ForegroundColor DarkRed
			Write-Host " Details: $_" -ForegroundColor DarkRed
		}
	}
	else {
		Write-Host "`n WARNING: Services not restarted" -ForegroundColor DarkRed
		Write-Host " Run as administrator for complete functionality" -ForegroundColor DarkRed
	}

	Write-Host "`n Operation completed!`n" -ForegroundColor Black -BackgroundColor Green
}
# Display menu
do {
    Show-Header
    Write-Host " MAIN MENU" -ForegroundColor Green
    Write-Host "--------------------------------------------------------" -ForegroundColor Green
    
    Write-Host " 1. Start driver upgrade mode" -ForegroundColor White
    Write-Host "     - Prepares for driver update" -ForegroundColor DarkGray
    Write-Host "     - Patches files after confirmation" -ForegroundColor DarkGray
    
    Write-Host "`n 2. Run script immediately" -ForegroundColor White
    Write-Host "     - Patch files directly" -ForegroundColor DarkGray
    
    Write-Host "`n 3. Exit" -ForegroundColor White
    Write-Host "     - Quits the tool" -ForegroundColor DarkGray
    
    Write-Host "--------------------------------------------------------" -ForegroundColor Green
    $choice = Read-Host "`n Please enter your choice (1-3)"
    
    switch ($choice) {
        '1' {
            Show-Header
            Write-Host " DRIVER UPGRADE MODE" -ForegroundColor Green
            Write-Host "--------------------------------------------------------" -ForegroundColor Green
            Set-ItemProperty -Path $FingerprintPath -Name IsReadOnly -Value $false -ErrorAction SilentlyContinue
            Write-Host "`n Read-only attribute removed from fingerprint.db" -ForegroundColor White
            Write-Host "`n Perform your driver upgrade now!" -ForegroundColor White
            Write-Host "`n Press any key AFTER the driver is installed..." -ForegroundColor White
            $null = $Host.UI.RawUI.ReadKey('NoEcho,IncludeKeyDown')
            Run-Script
            pause
        }
        '2' {
            Show-Header
            Write-Host " PATCHING FILES" -ForegroundColor Green
            Write-Host "--------------------------------------------------------" -ForegroundColor Green
            Run-Script
            pause
        }
        '3' {
            Show-Header
            Write-Host " Exiting... Thank you for using the tool!" -ForegroundColor Gray
            Start-Sleep -Seconds 2
            exit
        }
        default {
            Write-Host "`n Invalid selection. Please choose 1, 2, or 3." -ForegroundColor DarkRed
            Start-Sleep -Seconds 2
        }
    }
} while ($true)

can you do this for other setting as well? like multe frame generation and smooth motion?

can you do this for other setting as well? like multe frame generation and smooth motion?

you can already enable MFG and smooth motion via latest nvidia inspector version 2.4.0.11.

For testing purposes I'm still keeping fingerprint.db write-enabled and nothing has overwritten it so far in a couple of days. Installation of most recent driver 572.42 went well and did actually not overwrite fingerprint.db either. So did noit have to re-run the script and/opr redo any settings after installation of the driver. Just letting you know

OK Thanks.. then I guess that file only get updates by new nvidia app version maybe?
edit: its in the nvidia driver installation folder under nvBackend.

can you do this for other setting as well? like multe frame generation and smooth motion?

you can already enable MFG and smooth motion via latest nvidia inspector version 2.4.0.11.

Yes but that doesn't enable it in the Nvidia app tho (smooth motion) as for the mfg i also tested it and games only run at 2x . Profile inspector options are rtg 50xx only

So today the file (fingerprint.db) was overwritten when I started the PC. Nothing special, just waking up from sleep.

Keeping the file "read only", like what the script already does, seems to be needed then.

yeah but if the update is necessary then its no use of what we are doing..
anyways, I went back to the minimal package of nvidia driver installer. bf2042 kept crashing with nvcontainer.exe and nvidia app is trash with this whitelisting besides no other point of using it with all these bloatware.

inspector 2.4.0.16 works for DLSS override which I needed.

We're still learning. I'd like to keep NVAPP installed due to RTX HDR, but otherwise I agree. Did nvcontainer crash because of the write protected fingerprint.db you suspect? I actually have bf2042 installed so might as well try it myself...

bf2042 was crashing each and everytime in the menu, regardless dlss override. event logs showed only nvcontainer.exe crashing during this time. I was using second version of your script. idk whether that related to json file being read-only.

Thanks for feedback. I can't confirm on my system - BF2042 seems to run as per normal. No crashes of BF2042 or nvcontainer and the DLSS SR overrride work as expected in the game. fingerprint.db is at the moment write protected (the default from the script).

I'm going to try keep using this method until NVIDIA changes the whitelist for the better. Fingers crossed it'll be sooner rather than later. Til then, or until an even better approach come along. I'll report any findings here.

I followed the VRDad video to install this (https://www.youtube.com/watch?v=hZC83zTVfXk) including applying unblock to script, running script from download folder with admin rights, and rebooted but Skyrim VR still says unsupported on the override settings and is grayed out (when it works in the video). I noticed I have 2 Skyrim VR entries in the nVidia app, so I also tried uninstalling nvidia app and reinstalling and Skyrim VR, which clears it from nVidia app. I then reinstalled and 2 identical entries appeared again in the graphics settings for Skyrim VR. Selecting either one says unsupported. I appear to have the latest nVidia as it says "up to date.". I also tried running the script and rebooting 2 more times and verifying I have administrator rights. The very first time I ran the script with powershell I noticed it flashed some red text for a millisecond but could not read what it said before the window closed. Now when I download script again and repeat, I notice no red text when running. When I check file properties on the script it no longer shows an unblock box. Another person commented on video with same problem. What might the problem be?

Hi @BrentW89,

I have a a few clarifying comments which should help you troubleshoot. My apologies for a long post but I figure it might help others too with running the powershell-script. There are some hoops to go through to run PowerShell-scripts.

1. VRDad mentions in the mentioned video "unblocking" the script (right-click file in windows explorer, select properties, find the "Unblock" checkbox). This was necessary since the script was downloaded from the Internet and Microsoft/Windows "marks" files like this and subsequently won't allow them to run easily otherwise. This is part of Microsoft's Smart App Control. If you've "Unblocked" the file once, no need to do it again.

2. Running the script with admin rights is not strictly necessary (this is mentioned in the readme section of the script too) but it saves a reboot since the script can immediately restart two services when run with admin rights. Your call.

3. By default an unsigned script (like nVAppAppApp.ps1) residing on your local machine can not be executed. For security reasons. I suspect this may be your primary issue @BrentW89. It is possible to workaround by starting powershell with a temporary bypass or by setting a permanent override. To do a temporary workaround you would press WIN+R to get the Run-dialog and execute:
   powershell -executionpolicy bypass
   To set a permanent override you type "powershell" on the start-menu, right click and select "Run as administrator" and once you are at the PowerShell command prompt execute:
   Set-ExecutionPolicy unrestricted
   In either case you now have a PowerShell prompt open that can/will run the script.

4. Now you can run the script from the PowerShell prompt and clearly see what the output of the script is and determine if anything goes wrong. First though, you need to navigate to the folder of the script. by using the "CD"- command (acronym is for Change Directory). Once in the correct folder execute the script by typing ".\nVAppAppApp.ps1" (without quotes) or type"nv", hit the TAB-key for it to autocomplete and press ENTER.

5. When the script has run, you can now restart the machine. Or if the script was run with admin rights, the screen will blink black twice. 👍

6. An optional step is to verify that the two required files (ApplicationStorage.json and fingerprint.db) were actually updated/patched. The first one is found here:
   C:\Users\<YOURUSERNAME>\AppData\Local\NVIDIA Corporation\NVIDIA App\NvBackend\ApplicationStorage.json
   and the other one is found here:
   C:\Users\<YOURUSERNAME>\AppData\Local\NVIDIA Corporation\NVIDIA App\NvBackend\ApplicationOntology\data\fingerprint.db
   Easiest way to tell if the files were updated is to check the time-and-date-stamp of the files in windows explorer. It should be the time that you ran the script. And fingerprint.db should be write protected (right-click file in windows explorer, select properties, find the "Read Only" attribute to verify). In case you want to dig deeper you can also inspect the files by using something like Notepad++ to review the contents and ensure that the replacements the script does (review the script and it should be self-explanatory) were actually done.

Once you have looked into the above, and ensured that the script runs nicely, you can repeat as needed. On my machine I have set the permanent execution policy override and created a normal windows shortcut to the script and set the attribute to launch as administrator (right-click shortcut in windows explorer, select the "compatibility"-tab, check the "Run as Administrator" checkbox). I just double click the shortcut when I need to run the script. The script works wonders for me.

Following these steps fixed the problem. Thank you!

Hello. I'm having an unusual issue with this script.

After running the script, nearly all the titles listed in NVIDIA App have the expanded options for DLSS Override, even ones that do not support DLSS,so I believe it was successful.

However, the main title for which I was interesting in using the forced override, FF7 Rebirth, does not show the expanded options below the standard ones.

Is it possible to modify the ApplicationStorage.json or fingerprint.db to whitelist a specific title? Or could there be some other reason that this specific title is not updating along with the rest?

Thank you for your work on this script.

hi @Dougdoesnt. I've no ready answer but here is a possible hint. I see that FF7 rebirth lacks the keys that are modified by the script, i.e:

<Disable_FG_Override>0</Disable_FG_Override>
<Disable_SR_Override>0</Disable_SR_Override>
<Disable_RR_Override>0</Disable_RR_Override>
<Disable_RR_Model_Override>0</Disable_RR_Model_Override>
<Disable_SR_Override>0</Disable_SR_Override>

Since I don't have FF7 Rebirth I cannot try this myself, but I would love your input as it might be possible to automate this in the script if it works.

• Backup fingerprint.db.
• Remove Read-only from the file.
• Open it in notepad++, CTRL+F to search and find FF7 Rebirth
• Add the above in a similar place that they are found in another game. It seems to be right before the ending "Version" tag. Note that there may be several ending "Version" tags, one for each distributor (steam, Epic etc). Like this:

Link

• Save the file
• Make it write protected again.
• Restart the system (or run the script as admin so the two services can be restarted).
• Let me know how it goes please

And then, after doing the above, since you have FF7 Rebirth installed which I don't. Check if the following are present in ApplicationStorage.json for FF7 Rebirth after rebooting the system.

"Disable_FG_Override": false,
"Disable_RR_Override": false,
"Disable_SR_Override": false,
"Disable_RR_Model_Override": false,
"Disable_SR_Model_Override": false

Otherwise maybe experiment in a similar way to what was done for fingerprint.db. This file should not be write protected once you are done.

And again, backup the files beforehand please. And share the process and findings please :)

I will follow your instructions this evening and edit this reply with my findings.

EDIT:
@JPersson77

I followed your instructions and edited fingerprint.db.
I restarted the system and found no change in the NVIDIA App.

I then confirmed the presence of the string mentioned in the ApplicationStorage.json. it is present as expected.

This is the only title in the "Graphics" category of the NVIDIA App that does not have the "Driver Settings" section underneath the "In-Game Settings" section.

Is there some additional edit to fingerprint.db necessary to enable the "Driver Settings" section?

Hi thanks for testing! I'm currently at a loss then. Maybe compare the XML for FF7 Rebirth with another game and see if you can see any other indicative differences

Funnily enough, Rebirth got added to NVIDIA's whitelist for DLSS Override today.

Good things come to those who wait 😄👍

Oddly enough this doesn't seem to work for MFG. It does make the MFG part visible in the NvAPP sure, but it does not apply unfortunately.

I have also set a global 4x scale via NVPI, if the game is not in the whitelist for MFG, it doesn't seem to trigger. (Yes, i have 5090)

I updated the script with some user friendly stuff, including a menu option for driver upgrades allowing the NVIDIA installer to upgrade fingerprint.db with every new driver. Run the script before you install a new driver and follow the instructions please.

Thanks for the update!

Thanks for your hard work! I got everything running and was able to modify my SkyrimVR settings to enable the latest DLSS. However, I’m now running into an issue.

I updated my drivers before you released the latest update to the tool, so I didn’t have the option to upgrade fingerprint.db at that time. Now, the Nvidia App no longer allows me to change the DLSS Override - Super Resolution and DLSS Override - Model Presets settings. Instead, it displays a "Support not detected" message.

Do you have any advice on how to resolve this? And obviously I reinstalled the script after the driver update.

Thanks in advance!

Thanks for your hard work! I got everything running and was able to modify my SkyrimVR settings to enable the latest DLSS. However, I’m now running into an issue.

I updated my drivers before you released the latest update to the tool, so I didn’t have the option to upgrade fingerprint.db at that time. Now, the Nvidia App no longer allows me to change the DLSS Override - Super Resolution and DLSS Override - Model Presets settings. Instead, it displays a "Support not detected" message.

Do you have any advice on how to resolve this? And obviously I reinstalled the script after the driver update.

Thanks in advance!

Nvapp is riddled with bugs. Recent NVapp update did this to me and completely borked Smooth Motion in a way where enabling + disabling it was no longer possible.

I would suggest DDU your drivers. Which will get rid of Nvapp too. Go ahead and install it fresh. Ideally with Nvcleaninstall.

During Nvcleaninstall installation DO NOT install Nvapp. (It installs an older version then updates it which we are trying to avoid)

Instead, go to Nvapp page on Nvidia's website and download and install it separately. I should download the latest version.

After doing all this run this script.

Give it a go. It fixed my issues.

However it's clear that we are a long way away from a proper working Nvapp.

Regarding section "ADDITIONAL NOTE ON HOW TO RUN POWERSHELL SCRIPTS (added 2025-02-25)"

I just clicked "edit" the file and saved it under a different name. That was enough to run it.

Thanks for your hard work! I got everything running and was able to modify my SkyrimVR settings to enable the latest DLSS. However, I’m now running into an issue.
I updated my drivers before you released the latest update to the tool, so I didn’t have the option to upgrade fingerprint.db at that time. Now, the Nvidia App no longer allows me to change the DLSS Override - Super Resolution and DLSS Override - Model Presets settings. Instead, it displays a "Support not detected" message.
Do you have any advice on how to resolve this? And obviously I reinstalled the script after the driver update.
Thanks in advance!

Nvapp is riddled with bugs. Recent NVapp update did this to me and completely borked Smooth Motion in a way where enabling + disabling it was no longer possible.

I would suggest DDU your drivers. Which will get rid of Nvapp too. Go ahead and install it fresh. Ideally with Nvcleaninstall.

During Nvcleaninstall installation DO NOT install Nvapp. (It installs an older version then updates it which we are trying to avoid)

Instead, go to Nvapp page on Nvidia's website and download and install it separately. I should download the latest version.

After doing all this run this script.

Give it a go. It fixed my issues.

However it's clear that we are a long way away from a proper working Nvapp.

Do you have the links of NvCleanInstall? I wanna try this

Thanks for your hard work! I got everything running and was able to modify my SkyrimVR settings to enable the latest DLSS. However, I’m now running into an issue.
I updated my drivers before you released the latest update to the tool, so I didn’t have the option to upgrade fingerprint.db at that time. Now, the Nvidia App no longer allows me to change the DLSS Override - Super Resolution and DLSS Override - Model Presets settings. Instead, it displays a "Support not detected" message.
Do you have any advice on how to resolve this? And obviously I reinstalled the script after the driver update.
Thanks in advance!

Nvapp is riddled with bugs. Recent NVapp update did this to me and completely borked Smooth Motion in a way where enabling + disabling it was no longer possible.
I would suggest DDU your drivers. Which will get rid of Nvapp too. Go ahead and install it fresh. Ideally with Nvcleaninstall.
During Nvcleaninstall installation DO NOT install Nvapp. (It installs an older version then updates it which we are trying to avoid)
Instead, go to Nvapp page on Nvidia's website and download and install it separately. I should download the latest version.
After doing all this run this script.
Give it a go. It fixed my issues.
However it's clear that we are a long way away from a proper working Nvapp.

Do you have the links of NvCleanInstall? I wanna try this

NvCleanInstall > https://www.techpowerup.com/download/techpowerup-nvcleanstall/

DDU > https://www.wagnardsoft.com/forums/viewtopic.php?t=5210

NvApp Standalone > https://www.nvidia.com/en-us/software/nvidia-app/

Hello, nvidiaApp do not launch correctly after aplying this script ... I got always an error saying I must restart and reinstall ...

Hi @AlexandreBourrieau assuming you are using the "Driver upgrade mode" of the most recent script. NvApp crashed for me in relation to installing 572.83 as well. NvApp automatically launched after installation finished, but with a blocking error message (a dialog). Since NvApp launched immediately after driver install I did not have the the time to reapply the patch before NvApp launched.

It is unclear why the error message appeared at this point as the relevant files were at this time write-enabled (and they were indeed overwritten by the installer). My next step was to manually install NVIDIA_app_beta_v11.0.3.213, while still not having let the script patch files. I then received a similar error message while installing NvApp manually. However closing the error message etc and launching NvApp manually worked fine after this with no adverse effects noted. At this point I applied the patch again. It was now too late though for the patch and so I had to redo all my custom settings in NVPI (which is mostly just restoring the profiles NvApp creates to default)

So yeah I have a similar experience. I agree it seems plausible the script may have something to do with it, but then I don't know how/why since the idea of the "driver upgrade mode" is to remove the write-protection and ensure that the nvidia/nvapp installer can overwrite the files (which it did)

Hi @AlexandreBourrieau assuming you are using the "Driver upgrade mode" of the most recent script. NvApp crashed for me in relation to installing 572.83 as well. NvApp automatically launched after installation finished, but with a blocking error message (a dialog). Since NvApp launched immediately after driver install I did not have the the time to reapply the patch before NvApp launched.

It is unclear why the error message appeared at this point as the relevant files were at this time write-enabled (and they were indeed overwritten by the installer). My next step was to manually install NVIDIA_app_beta_v11.0.3.213, while still not having let the script patch files. I then received a similar error message while installing NvApp manually. However closing the error message etc and launching NvApp manually worked fine after this with no adverse effects noted. At this point I applied the patch again. It was now too late though for the patch and so I had to redo all my custom settings in NVPI (which is mostly just restoring the profiles NvApp creates to default)

So yeah I have a similar experience. I agree it seems plausible the script may have something to do with it, but then I don't know how/why since the idea of the "driver upgrade mode" is to remove the write-protection and ensure that the nvidia/nvapp installer can overwrite the files (which it did)

Thanks you, it's a bit confusing for me I do not know how to do but thanks for taking time to reply ;)

My driver 572.83 is already installed, I have uninstall all other nvidia stuff using BCU, and I will try to :

1. Apply your patch (press 1)
2. Install Nvidia App : NVIDIA_app_beta_v11.0.3.213
3. Manually add the game for which I want to enable DLSS4 to nvidia App
4. Quit nvidia app
5. Apply your patch to get DLSS4 enable (press 2)
6. Launch nvidia app and activate DLSS4 for the game in nvidia app

Seems correct to you ?

EDIT 1 :

So I tried what I wrote above.

I managed to launch NvidiaApp, but in the game I added, I couldn't change the DLSS (everything was blank : This game cannot be optimized... ).

After a while, I got an error message, and now NvidiaApp isn't working at all even if I quit and re-launch it...

So it seems that if we apply a patch after adding a game manually, NvidiaApp is not functionnal anymore... weird...

EDIT 2: Back to NvidiaApp v11.0.2.341 and all is OK now...