DLSS 5 Swapper Not Working: Find the Failed Step

Quick fixes to try first

What you see	Most likely cause	Fix
Install stops with Windows will not let this app write to the game folder, or fails with EPERM	The game is running, or it sits under Program Files	Close the game; run the app as administrator or move the game (details)
Installed, but nothing changes in game	Launcher .exe selected, or the add-on is not enabled	Re-add the game using the real rendering .exe; in game press Home → Add-ons and enable the DLSS 5 add-on
Worked once, then stopped	The game or its launcher restored the original files (the developer confirms this for the Rockstar Games Launcher)	Check whether the add-on is still in the game folder; RDR2 and GTA V through that launcher are out of scope (RDR2 page)
Crash or black screen at launch	Overlays such as MSI Afterburner / RivaTuner, or Smooth Motion	Close overlays and turn off Smooth Motion, then retry (crash guide)
Neural pass faults on driver 616.64 or newer	The game was set up with v2.2.7 or earlier, whose RenoDX v4.7 consumer faulted on those drivers	Update to v2.2.8 or later and reinstall that game’s route; no driver downgrade needed
The installer closes at once with 0xc0000005	An installer bug fixed in v2.2.9	Use v2.2.9 or later, or the portable build
Windows blocks the app	Unsigned app flagged by Defender	Verify the file, then read the Kepavll guide

If none of these match, work through the stages below in order.

Start with the symptom

What do you see?

Choose the first thing that goes wrong. Change one thing at a time and keep the result.

Prefer the written checklist?

F8 does not open the overlay

1. Check the route, API and bitness. The compact F8 overlay needs a 64-bit DX11/DX12 game on the Feeder or native RenoDX route. Multipass uses Home and OptiScaler is not supported. Other APIs cannot be diagnosed by F8 alone.
2. Keep Swapper running and check the configured hotkey. A closed app, remapped hotkey or preview panel is different from a connected in-game overlay. Since v2.2.8 the panel names the reason it cannot attach, and the game's ReShade.log has an NR_LAB line saying what it found.

The game crashes

1. Save diagnostics, then restore originals. Close the game before restoration. If the restored game also crashes, isolate that baseline before blaming the new route.
2. Compare the actual EXE, API and existing loaders. Use one route at a time. Check other injectors and overlays, then compare one change against the working baseline.

Effects or a DLL are missing

1. Read the exact missing filename and selected route. Native DLSS and Feeder do not need identical files. A generic no-effects message is not a reason to fetch a DLL from an unrelated site.
2. Check the completed install and matching component paths. Inspect the log and the expected effects/add-on paths. Obtain matched files through the official project workflow; stop if the package or checksum differs.

The overlay opens, but nothing changes

1. Separate a visible panel from a loaded consumer. Check the component list and log. Swapper's preview panel, a slider moving or GPU load increasing does not prove the game completed a neural pass.
2. Check inputs and compare the same scene. Native games need the expected DLSS setting; Feeder needs usable depth or motion inputs. Keep camera and settings fixed for an enabled/disabled comparison.
3. Record the driver and changed components. If the game was set up with v2.2.7 or earlier and your driver is 616.64 or newer, reinstall its route on v2.2.8 or later: the old RenoDX v4.7 consumer faulted on those drivers. Otherwise save the exact versions and diagnostic status instead of stacking components.

The game slows down or runs hotter

1. Compare one repeatable scene against the baseline. Record resolution, settings, GPU, driver, consumer and frame time. Neural processing and generated-frame counters measure different things.
2. Change one setting and measure again. Try fewer passes or the relevant quality controls, then compare frame time, image quality and response. Keep a change only if it improves your repeatable result.

Install fails or the app will not open

1. Separate application startup from game installation. For startup, verify the official Windows x64 package and the exact security alert; an installer that closes at once with 0xc0000005 was fixed in v2.2.9, and the portable build was not affected. For installation, confirm the actual game executable and close the game.
2. Read the final log and the denied path. EPERM can identify a protected folder. An Installed message before completion is insufficient; use the release's documented permissions advice for that path.

Save a configuration record

Record Swapper version, game build, GPU, driver, rendering API, executable path and bitness, selected route, and known component versions. Include existing mods and overlays. Capture the exact error rather than replacing it with “not working.”

The project documentation describes Save diagnostics. Save that bundle before reinstalling or restoring so the failed configuration remains available for investigation. Review logs before sharing; remove personal paths and account information.

Follow the first failing row

What you observe	Check next	Where to continue
Application will not launch	Official package, Windows x64 requirements, specific alert	Download and source checks
Install ends with an error	Target EXE, folder access, completion log	Installation checks below
Game crashes at launch or during play	Whether the restored game works	Crash isolation
F8 or controls do not connect	Hotkey, process, route, API, add-on	Overlay checks
No effects or a missing DLL	Native versus Feeder route; exact filename	Missing-file diagnosis
Components load but image is wrong or unchanged	Inputs, consumer, model, runtime evaluation	Rendering checks below
Image works but the game slows down	Fixed-scene comparison and processing cost	Performance measurement

Did installation finish in the right place?

A launcher and the rendering executable may live in different folders. Confirm the actual target and the game’s active API. If a game changes between DirectX and Vulkan, the installed route may no longer match.

For EPERM, read which location could not be written. The v2.2.7 notes explain the protected-folder permission message and fix an earlier premature installation-success message. A status shown before the operation finishes is insufficient evidence.

Close the game before repairing an installation. Follow the first-use sequence and keep the restore files. Do not repeatedly layer new routes over a failed one.

Did the right consumer load?

Check the component list and log. The ordinary native / Feeder consumer and Multipass consumer differ. If the ordinary native route was installed with v2.2.5, v2.2.6 corrected an incorrect consumer; the affected game requires the documented reinstall, not only a desktop update.

For a non-native game, validate Feeder’s inputs. For a native game, check its DLSS setting. A panel appearing, a configuration value reading back, or GPU activity increasing does not by itself establish a completed neural pass.

If the image flickers or changes incorrectly

Compare the same scene with the effect disabled and enabled, then check the selected consumer and input data. If flicker starts only after installing a route or adding a pass, return to the previous configuration before changing another component. For Silent Hill 2 Remake, record the game build and whether flicker also occurs without Swapper; these checks help isolate the problem but do not establish a game-specific fix.

Avoid treating warnings as universal causes

Older guides treat driver 616.56 as a ceiling. Since v2.2.8 the publisher lists any current driver: the faults on 616.64 and newer came from the RenoDX v4.7 consumer, and its replacement, 6.5.3, is reported upstream to complete on 617.14. A newer driver is therefore not a cause in itself; a game still carrying the old consumer can be. Likewise, one issue report involving an overlay or an injector does not explain every crash.

Change one variable at a time and keep each result. If the evidence remains inconclusive, the useful outcome is a reproducible report with an exact failing stage, not an unsupported universal fix.

Return to a working game

Save diagnostics, close the game, and choose Restore originals. Verify normal launch and the baseline scene. If the button is greyed out while modded files are still in the game, update to v2.2.9 or later, which offers the newest backup record whose files are still present (issue 325). Follow complete restoration if application removal is also intended. If the restored game still fails, investigate that baseline before another injection attempt.