War in the North PS5 0KB Save Bug and Fixes

Quick answer

If Legacy Edition reports a 0KB save on PS5, stop treating the next save as disposable. Preserve any cloud or USB backup from before the failure, record the chapter and trigger, and contact support. The current discussions contain mixed reports about reinstalling, rebuilding the database, vendor saves, and deleting older saves; none was verified as a universal repair on 14 August 2026.

Status: community-reported and unresolved. A reported workaround is not the same as a safe recovery procedure.

First response: protect the evidence

Stop playing past the warning if the game is still attempting to save.
Do not delete local saves or cloud saves to “force” a new file.
Preserve the oldest known-good copy before opening another campaign.
Note the exact chapter, last successful checkpoint, menu or transition that preceded the warning, free storage, and whether the session was solo or co-op.
Photograph the 0KB entry and write down the game version and PS5 system version.

The purpose of this order is recovery protection, not a promise that the backup will restore correctly.

Why common advice is inconclusive

Suggested action	Why it is not a verified fix
Reinstall the game	Replaces program files, not necessarily a damaged save record
Rebuild the database	A system-maintenance step does not prove the game save is repairable
Delete old saves	Can remove the only surviving backup and is irreversible for that copy
Buy a vendor item or change a chapter	A different trigger in one report does not establish causation
Turn off cloud sync	Can prevent a good cloud copy from being preserved

Do not perform several actions together. If support later asks what happened, a clean timeline is more useful than an unrepeatable chain of destructive experiments.

Controlled comparison after a backup

Only if a safe copy exists, test one new slot or a short fresh session. Record whether the game creates a non-zero file, whether the warning appears after a checkpoint, and whether the same failure occurs in solo and co-op. Do not use a valuable completion run as the experiment.

The PS5 launch discussion is the current community lead for this page. It is not an official incident report, and the absence of a reproducible trigger means the page cannot name a guaranteed chapter, boss, or repair sequence.

What to send to Aspyr

Include the platform region, Legacy Edition product, game and system versions, save-slot size, free storage, cloud-sync state, chapter, last good save, session mode, and a short timeline. Ask whether the team wants the affected file or a diagnostic package before removing anything.

Use Aspyr support and keep the ticket number with the save notes. If a later patch publishes a recovery instruction, update this page with the version and the exact scope of that instruction.

Sources and evidence boundary

PS5 0KB save discussion — reported symptoms and mixed attempts.
Legacy Edition Steam listing — product identity only.
Aspyr support — escalation route.

This page intentionally refuses to label deletion routines, database rebuilds, or reinstalls as a confirmed fix.