Fix NVIDIA App Unable to Retrieve DLSS Settings

If the NVIDIA app cannot retrieve settings, update the app, refresh the game profile, and check the game's Driver Settings before reinstalling your graphics driver. The warning can concern the app's ability to read or recommend in-game settings. It does not, by itself, establish that DLSS overrides are broken.

How to Fix NVIDIA App Unable to Retrieve DLSS Settings
That distinction matters because the same Graphics page contains several different controls. Native DLSS belongs to the game, automatic optimization manages its configuration, and DLSS overrides change supported features through driver settings. Start by identifying which part actually fails, then follow the relevant checks below.

First, check what the error is stopping you from doing

Open Graphics > Program Settings, select the affected game, and scroll down to Driver Settings. Check whether the DLSS controls exist, whether you can apply a choice, and whether that choice remains after selecting another game and returning.

What you seeWhat to investigate
Optimization warning, but DLSS controls workGame configuration or optimization support; verify the override in-game
The game is missing or incorrectly identifiedScan location, executable, and installed edition
A DLSS option is unavailableSupport for that feature, GPU, and game
Apply fails or the selection immediately revertsThe exact save error and whether other supported games are affected
Settings fail across the libraryApp version, connectivity, and installation state

This table is a diagnostic starting point, not proof of a particular cause. For example, one affected game makes a title-specific problem worth investigating first, but does not completely rule out an app bug.

1. Update the NVIDIA app and restart it

NVIDIA documented a particularly relevant fix in app version 11.0.3.232: the settings-retrieval warning could misrepresent the state of driver settings. Its release history also records fixes for unavailable DLSS overrides in supported titles and missing overrides in manually added games.

These are historical fixes, not a recommendation to install those old versions. Use the current official NVIDIA app release. Updating the display driver alone does not confirm that your app has also been updated.

  1. Close the game and record your NVIDIA app version, driver version, and GPU model.
  2. Allow an offered app update to complete, or obtain the current installer from NVIDIA's official app download page.
  3. Restart Windows if an installation is pending or you have just updated the driver.
  4. Reopen the same game's page and test the affected control.

Do not judge success only by the disappearance of a warning. Check whether the setting you need is accessible and can be saved.

2. Refresh the library and confirm the correct game

In the Graphics section, open the program-list three-dot menu and choose Refresh. If the game is absent, check the scan locations and include its actual installation directory. The Graphics menu also provides options for adding programs manually.

Pay attention to what you add. A launcher, updater, benchmark executable, and the main game executable may sit in the same folder. Use the program that runs the game. Check the edition as well: a remaster, an older release, and a separate multiplayer client should not be assumed to share one profile.

If you previously hid the game, inspect the Hidden filter. Adding its executable repeatedly will not fix a hidden entry or grant unsupported features.

Compare with another installed title whose relevant override support is confirmed. If that title works, keep investigating the affected game's installation and profile before resetting settings for the entire library.

3. Launch the game once and let it save its settings

This step matters particularly when the warning appears in the optimization area. NVIDIA's optimization feature modifies game configuration files, and some games create those files only after their first launch.

  1. Finish installing the game's current official updates.
  2. Launch it normally through its usual launcher.
  3. Open the graphics menu, review the settings, and use Apply or Save if available.
  4. Exit normally to the desktop, then refresh the NVIDIA app.

Reopen the game and check whether your choices persisted. If they did not, investigate that saving problem first. A configuration file that never gets created or updated gives the optimization feature little useful state to read.

Do not delete the game's entire settings or save-game folder to force regeneration. If its developer recommends resetting a specific configuration file, back up that file and your relevant settings first. A profile-retrieval warning is not a reason to risk saved progress.

4. Separate optimization support from DLSS override support

A game offering DLSS does not automatically support every app override. NVIDIA maintains compatibility information for RTX features and overrides; its optimal-settings support is a separate question. Check the particular feature you want, rather than treating any mention of DLSS as blanket compatibility.

Hardware requirements also differ between Super Resolution, Ray Reconstruction, and Frame Generation. An unavailable Frame Generation option does not demonstrate that an otherwise supported Super Resolution override is broken.

For a supported override, enable the corresponding feature inside the game, save the change, and exit. Then return to the game's Driver Settings, select the desired override, apply it, and relaunch. An override is not a universal switch that adds DLSS to games lacking the underlying integration.

Check Global Settings if you previously configured overrides there. For diagnosis, make the intended choice explicit for one game and record both configurations. Changing every title at once makes it harder to trace an unexpected result.

5. Check connectivity when several profiles fail together

NVIDIA says the app can take a few minutes to download game settings and screenshots on its first run. It also notes that server maintenance can interrupt availability. A new installation that has not finished loading its data should not immediately be treated as corrupted.

Leave the app online long enough to finish its initial work, then refresh once. If several previously working profiles fail together, check NVIDIA's official support communications for a matching service notice. Without such a notice, call an outage a possibility rather than a confirmed explanation.

A useful comparison is to retry on another trusted internet connection, if available. If the profiles load there, investigate the original connection or its filtering rules. If nothing changes, that comparison has not established a network cause. Avoid changing DNS, router rules, and app files simultaneously.

6. Investigate file access only when there is evidence

Security software becomes relevant when the game cannot save its preferences or you see a notification about a blocked file change. A retrieval warning on its own is not evidence that antivirus protection caused the problem.

Microsoft Defender's Controlled folder access can prevent untrusted applications from changing files in protected folders. Review the blocked-app notification or protection history and match its executable path to the program you were using. This helps distinguish a real access restriction from a guess.

If a different security product is installed, first identify your antivirus, then inspect that product's relevant activity log. Resolve a confirmed block through its documented process, allowing only a verified, trusted application where appropriate. On a managed computer, ask the administrator to review the restriction.

Blanket antivirus exclusions and disabling the firewall are poor first steps. They change unrelated protection without showing why the game profile could not be read.

7. Reinstall the app if the problem remains widespread

If updating, refreshing, and checking supported profiles do not help, reinstalling the NVIDIA app is a reasonable next experiment. It is not a guaranteed repair for an unsupported game, a blocked configuration file, or a service problem.

Save screenshots of custom app settings you want to retain. On Windows 11, close the app, open Settings > Apps > Installed apps, find NVIDIA app, and choose Uninstall from its menu. Install a fresh copy from NVIDIA's official download page.

After installation, let the app load its data, refresh the game list, and retest the same title. Keep the display driver unchanged during this comparison if it is functioning normally. That gives you a clearer answer about whether reinstalling the app helped.

8. Reserve driver repair for a driver-related problem

If the controls disappeared immediately after a driver change, the separate troubleshooting sequence for missing DLSS overrides can help distinguish a reset preference from a profile or installation problem.

A clean driver installation makes more sense after an installation failure or broader driver malfunction than after one game's optimization warning. Save custom graphics settings first because a clean installation resets driver configuration.

Use the correct official NVIDIA driver package for your GPU and Windows version. Close games and GPU monitoring utilities, run the installer, select Custom (Advanced), and enable Perform a clean installation. Restart afterward and test the original symptom before restoring custom settings.

Third-party driver removal, registry edits, and replacement DLSS files are not necessary starting points for this error. They add changes that can make the original failure harder to diagnose.

Verify the override inside the running game

A saved app preference establishes what you requested. Runtime status is the stronger check of whether the game is using it.

  1. Enable the NVIDIA overlay and launch the game with the relevant DLSS feature active.
  2. Press Alt+Z and open Statistics > Statistics View > DLSS.
  3. Use Alt+R to display the configured statistics overlay.
  4. Check the override status shown for the feature you changed.

If the override is active but optimization still reports a problem, you have narrowed the unresolved issue to a different part of the app. If the preference saves but remains inactive in-game, revisit the selected executable, compatibility, and in-game feature setting.

Once retrieval and activation work, you can evaluate image quality and performance separately. A broader guide to NVIDIA app settings is useful for that next stage; tuning every option is not required to resolve a retrieval error.

Frequently asked questions

Does this warning mean DLSS is disabled in my game?

No. Check the game's own graphics menu and the runtime overlay. The warning alone does not establish the state of native DLSS or a driver override.

Do I need to log into an NVIDIA account?

Signing in is optional for the app's general features. NVIDIA associates account login with benefits such as redeeming rewards; creating an account is not a required repair for settings retrieval.

Will clearing the shader cache fix it?

The official steps discussed here do not establish shader-cache deletion as a repair for this warning. Start with the failing profile, saved game configuration, and app state instead of deleting unrelated caches.

Why does only one game show the error?

That pattern makes the game's configuration, detected edition, and support status useful starting points. Compare it with a confirmed supported title before attempting a system-wide repair.

What should I send NVIDIA if the problem persists?

Use the app's feedback or issue-reporting control. Include the exact warning, app and driver versions, GPU, game build, launcher, executable path, and screenshots. State whether other games work, whether settings save, and whether runtime verification succeeds. Those distinctions make the report much more actionable.

Choose the next action from the failed check

If DLSS works, address the remaining optimization warning separately. If a supported override cannot be saved across games, investigate the app installation. If the game itself cannot retain settings, fix that configuration problem first. Stop once the required feature works and you have verified it in-game.