War in the North PS5 0KB Save Bug and Fixes
Handle a PS5 0KB save warning in War in the North Legacy Edition: preserve usable backups, record the failed step and distinguish Patch 2 gear fixes.
What Patch 2 repairs, and how to handle a 0KB save
Patch 2 repairs a respec-related equipment loss and improves co-op loading and hub stability. Those are different symptoms from a PS5 save shown as 0KB. The notes do not describe rebuilding an empty save file, so do not overwrite a surviving local or cloud copy while trying to apply the gear fix.
If the warning appears, stop the long run, note the displayed save time and size, and preserve the last usable copy before changing anything. Report the edition, installed patch, last successful save and whether the failure followed a join, checkpoint, town return or respec. Continue through the backup-first steps below rather than combining save deletion, reinstall and database changes into one attempt.
Quick answer
August 2026 PS5 player reports describe saves appearing as 0KB. If that warning appears in your game, stop before overwriting a surviving local or cloud copy and follow the backup-first steps below.
First response: protect usable saves
- 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 | Risk to existing saves |
|---|---|
| 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
Recommended guide route