The Witcher 3: Wild Hunt Remastered: How to Fix Saves, Audio & DLSS – Hotfixes

After the first post-launch hotfixes, start with the version of the copy you actually launch. An updated Steam installation does not tell you whether your Xbox app copy has received the same fixes. Check that build and restart the game before touching save folders, raising master volume or resetting graphics settings.

For The Witcher 3: Wild Hunt Remastered, three distinctions make troubleshooting much quicker: local saves versus cloud synchronization, dialogue volume versus overall audio volume, and Xbox Play Anywhere PC versus other PC editions. Each points to a different cause — and a different fix.

Table of Contents (6)

Which patch applies to your platform?

Platform or edition	Relevant update	What to check
Steam, GOG, Epic Games Store and Battle.net on PC	5.00c	Saving and loading when the Documents path contains special characters; dialogue volume after pause-menu navigation.
Xbox Play Anywhere on PC	5.00b for DLSS; 5.00c for PC save/audio fixes	DLSS in this edition’s graphics menu, followed by the same local-save and dialogue checks as other PC builds.
PS5 and Xbox Series X|S	5.00b	Lighting and graphics changes. Persistent pause-menu voice-volume problems have a separate console fix.
Previous-generation console versions	Outside this hotfix checklist’s main scope	Use the update information for that console edition rather than applying the next-generation patch expectations.

Let the relevant launcher or console finish installing its update, then fully close and relaunch the game. Testing an already-running session can leave you checking behavior from before the update.

The graphics changes also have different scopes. Patch 5.00b brings lighting adjustments and graphics-parity changes to the supported console and Xbox Play Anywhere builds. PC hotfix 5.00c adjusts Velen’s bloom, vegetation lighting, saturation and path tracing alongside its save and audio fixes. Those changes do not imply identical rendering features or settings across every platform.

PC save/load failures: test local saves before changing folders

Install 5.00c first, then test both a new manual save and an existing save. Try more than one existing slot. This separates a broad save-system failure from a problem affecting one file, without immediately changing your Windows profile or save location.

The Documents-path bug involves special characters anywhere in the full path. An accented or non-Latin Windows user-folder name can matter even when the Documents folder itself has an ordinary name. A redirected or cloud-synced Documents location adds another part of the path to inspect.

Hotfix 5.00c addresses that character-handling failure. A save that still fails afterward needs a narrower diagnosis:

What happens	What to investigate next
Manual saving and loading both fail	Check the installed update, the full Documents path and the game’s permission to access it.
Manual saves work, but cloud saves fail or do not appear	Check launcher synchronization and the signed-in account. Compare local behavior while synchronization is temporarily disabled or bypassed.
One save fails, but other slots load	Test an earlier save. The failing file may be corrupted; changing the entire Documents location is a poor first response.
The game cannot access Documents at all	Check Windows controlled-folder access, antivirus restrictions and whether a redirected Documents location is available.

If Windows security is blocking access, inspect the rule affecting the game rather than disabling protection across the system. If Documents points to an unavailable drive or cloud location, restore access to that location before treating the symptom as save corruption.

Back up existing saves before changing folder locations or Windows account settings. Close both the game and launcher before moving or renaming save folders. Otherwise, the game or synchronization service can write to a location while you are changing it, making the original problem harder to isolate.

Once a manual save can be created and loaded in a freshly launched session, you have a useful baseline. If the remaining failure occurs only during cloud synchronization, focus on the launcher and account rather than repeatedly changing the Documents path.

PC voice volume: reproduce the pause-menu trigger

The audio regression has a specific signature: dialogue becomes much quieter after moving through pause-menu tabs, while music, effects or ambience can remain at their usual levels. Raising master volume to compensate also raises those unaffected sounds.

With 5.00c installed and the game freshly relaunched, listen to dialogue before opening the pause menu. Move through several tabs, return to gameplay and listen again. That before-and-after comparison tells you whether the menu-triggered drop remains.

If voices are quiet from the start, or stay quiet regardless of menu use, check the dialogue/voice-over slider independently of master volume. Then check the selected Windows audio output and the game’s level in the Windows volume mixer.

Headphones or stereo output provide a useful additional test. If dialogue becomes clear through stereo but remains weak through a television or surround setup, investigate output routing and channel mixing. Restart the game after changing the output device, spatial-audio settings or in-game audio options so the next comparison uses the new configuration.

PS5 and Xbox Series: keep the voice fix separate from 5.00b

Install 5.00b and restart the console, then make the same dialogue comparison: listen before opening the pause menu, navigate through its tabs, and listen again after resuming. Compare voices against music and effects rather than judging overall loudness.

Check the in-game dialogue setting, television or receiver audio mode, and headset balance if voices are consistently weak. If they drop specifically after pause-menu navigation, preserve that distinction when describing the issue. A constant output imbalance and a menu-triggered volume change call for different troubleshooting.

The PC voice fix in 5.00c does not mean the console fix has arrived. CD Projekt Red’s console voice-volume fix is on a separate rollout, with no announced release date in the 5.00b/5.00c update window. Record the console model, installed game version and the menu sequence that causes the drop if it persists.

Missing DLSS on Xbox Play Anywhere PC

Patch 5.00b fixes the issue preventing DLSS from being enabled in the Xbox Play Anywhere PC edition. Check the installation launched through the Xbox app: a working DLSS setting in your Steam, GOG, Epic or Battle.net copy does not establish the state of the Xbox edition.

After updating that installation to 5.00b or later, open its graphics settings and inspect the upscaling or resolution-scaling menu. On compatible NVIDIA hardware, select an available DLSS quality mode, apply it and restart if prompted. Then check performance and image quality in gameplay; the menu entry alone does not show how the setting behaves.

If DLSS is still absent, work through the checks that affect this edition:

• Confirm the launcher and installation. Make sure you are testing the Xbox Play Anywhere PC copy and that the Xbox app has completed any pending updates.
• Restart the game and Xbox app. Recheck the graphics menu from a fresh launch after installation finishes.
• Check NVIDIA hardware support and the driver. The patch restores availability in the affected build; the GPU still needs to support DLSS.
• Remove configuration interference. Note your current settings before resetting graphics options, and test without custom configuration files or conflicting overlays.

Check frame generation separately. Its availability depends on GPU and configuration support, so a missing frame-generation option does not establish that DLSS upscaling is broken.

Xbox Play Anywhere also needs a clear platform distinction here: this DLSS fix concerns the Windows installation. Console graphics parity refers to the relevant lighting and graphical changes; it does not give the Xbox console version a PC DLSS setting.

What to record if the problem survives the update

A useful support report connects the symptom to a reproducible trigger. Include the platform, launcher and installed patch, followed by the detail that separates your failure from the others:

• Save/load: whether a new manual save works, whether several existing slots fail, whether cloud synchronization alone fails, and whether Documents is redirected or contains special characters.
• Voice volume: whether dialogue is normal before pause-menu navigation, which tab sequence causes the drop, and the selected output device or console audio setup.
• DLSS: the Xbox Play Anywhere PC edition, GPU model, NVIDIA driver version and a screenshot of the upscaling menu.

The clean troubleshooting order is to update the correct installation, relaunch, test local saving and loading, compare dialogue before and after the pause menu, then check DLSS on Xbox Play Anywhere PC. Change Windows paths only after the save tests point there, and keep console voice-volume behavior separate from the PC hotfix. That preserves your saves and gives each remaining failure a specific next action.