An “Error modifying … content/metadata.store” during a GOG patch is an installation failure, not proof that your saves are damaged. Current GOG reports have mixed reinstall outcomes. Preserve the log and save backup, then choose a storefront repair or a matching full-installer route; do not replace metadata.store with an unknown download.
Check what failed before repeating downloads
Write down the installed source version, updater filename and stated source/target versions, edition, language and game directory. Preserve the exact failing log line privately. Check that the patch actually targets this installation; a full installer and an incremental updater are different packages.
Close the game and its tools. Back up the actual Documents save folder separately from the game installation. Do not assume an installation-folder copy includes your character. If the patch failed, record the version that the game now reports rather than assuming it completed.
Choose a supported installation route
| Setup | Next step | Result to check |
|---|---|---|
| Game managed by GOG GALAXY | Select the game, Customize → Manage installation → Verify/Repair; allow it to finish. | Repair finishes, the intended build is installed and the main menu opens. |
| Offline installation | Check the full installer version offered in your GOG library, and download all parts for that same installer and language. | The full installer completes; the reported game build matches the package. |
| Patch fails again or the package does not match | Stop repeating the same updater; provide GOG the log and source/target package details. | A package-specific support response, rather than an assumed metadata fix. |
Before any uninstall/reinstall, verify the external save backup and preserve user-added files separately. GOG documents that offline installers can appear later than a new client build, so inspect the actual offered version rather than treating an announcement as proof that every download has updated.
Separate a later startup crash
The forum includes both full-install success and continuing 5.00c startup crashes. One NVIDIA user reports that driver 617.14 solved their launch failure; that does not show that this driver fixes the updater's metadata error, nor prescribe it for every GPU.
If installation completes but the game crashes, move to startup checks and record GPU/driver details. If the game opens but cannot save, use save/load troubleshooting. Keep backups through both tests. The same-drive installer anecdote and manual metadata restoration proposal remain unverified causes, so neither is a required fix here.
Sources and version limits
- GOG players: new-install 5.00c patch failure — Read October 6, 2026; OP and replies #4, #6–#8, #10 and #13 describe different outcomes.
- CDPR: verify game files — Official storefront procedures; verification does not remove every added mod file.
- GOG: offline installer publication — Developer documentation describes possible post-launch publication delay; no exact current Witcher package availability is promised.
Sources checked October 6, 2026. These are attributed reports and route instructions, not our own test of your hardware or save. A reported workaround does not establish a permanent fix.