PC hotfix 5.00c addresses save/load failure when the Documents-folder path contains special characters. If your symptom and older build match that case, update through your storefront to its current supported release, then test without overwriting your working saves. Cloud sync failure, one damaged save and a loading hang need their own branches.
Which version does this fix cover?
CD PROJEKT RED's October 1, 2026 5.00c announcement covers Steam, GOG, Epic Games Store, Battle.net and Xbox Play Anywhere on PC. It is not a claim about the PS5 patch number.
Record the installed build and storefront before updating. The official news index checked October 4 still listed 5.00c as the newest visible PC hotfix. Check the current official announcements and your storefront when following this guide later; do not downgrade a newer supported installation to match this article.
Choose the branch that matches the failure
| Symptom | Next step | What remains unknown |
|---|---|---|
| Local saving or loading fails on an older PC build; the Documents path includes special characters. | Back up accessible saves, update the game and run the local test below. | Whether your failure is caused by that path issue; the symptom alone is not a diagnosis. |
| The same failure persists on 5.00c or a newer release. | Record the full build, path and error; submit a support report. | Cause and recovery. Do not rename your Windows profile or move Documents based solely on this article. |
| Local saves work, but a cloud or cross-platform copy is missing. | Preserve the local copy. Record the source and destination accounts, platforms and sync state for support. | The local Documents-path fix is not proof of a cloud-transfer fix. |
| Only one save fails while another loads. | Keep both files; test a copy of the last known working save. | We cannot establish that the failing file is corrupt, or promise that a patch repairs it. |
| The game stays on a loading screen, or crashes during loading. | Capture the behavior, wait time, build and mod setup for support. | No universal hang or crash solution is established by the path fix. |
A safe local test after updating
- Preserve the evidence. Quit and copy accessible local saves to a separate backup. Note whether sync is enabled; do not let a test replace your only good copy.
- Update through the storefront. Let the update finish and confirm the installed build changed. Record the exact error if the game cannot start.
- Load a duplicate of a known working save, if one is available. Make a new manual save in a separate slot. Return to the menu and try loading that new save.
- Compare the result. A successful save-and-reload confirms that local operation in this test. It does not validate every old save or prove a cloud copy has arrived on another device.
If you cannot safely make this comparison, keep the files and go directly to support. There is no need to experiment with deleting saves, editing profile paths or switching to Classic.
Make the support report useful
Include Windows version, storefront, full game build, the exact save/load action and error, whether all saves or one file fail, your Documents path's special-character status, and your mod list. Share paths and files privately with support; public screenshots can expose your Windows account name.
For cloud cases, add the two platforms, account connection state and whether the source file loads locally. For hangs, add how long you waited and whether the application responded. Use the official Witcher 3 support portal. These details narrow the problem without asserting an unverified repair.
Sources and version limits
Primary evidence: PC 5.00c patch notes, published October 1 and checked October 4, 2026. The backup and comparison sequence is our diagnostic organization, not a claim that CD PROJEKT RED prescribed those steps. No firsthand reproduction is claimed.
Classic (1.32), the 2022 Next-Gen release and 2026 Remastered are separate version contexts. A Classic launch fix does not establish two-way save compatibility. If your game loads but a monster's trophy is missing, use the monster-loot guide.