Star Wars Zero Company Not Saving: What to Do

If Star Wars Zero Company is not saving, regain control of Hawks, wait a few seconds, then quit normally; EA identifies quitting before this point as a cause of lost recent progress. If manual saving is unavailable, check whether the campaign uses Beskar Mode. If progress is missing only on a second PC, check the first PC's cloud sync before starting another session.

Match your symptom to the right fix

Progress disappears after you quit

EA's saving advice applies when you quit while you are not controlling Hawks. Use this short check before leaving an important session:

1. Finish the current transition and wait until you control Hawks again, or until the next mission has begun.
2. Wait a few seconds. In a campaign with manual saving, use a new named slot if the Save option is available, preserving your previous working slot.
3. Note the current mission, objective and save time. Check the save list for the new entry if you made a manual save.
4. Quit through the game menu. On Steam, allow synchronization to finish before shutting down or moving to another device.
5. When you next launch, compare the loaded objective with your note. A new save entry confirms a write was attempted; successfully loading the expected progress is the useful final check.

The wait in step 2 is EA's documented advice. The named-slot and comparison steps are our troubleshooting method: they help distinguish a missed checkpoint from opening an older save.

Why Beskar Mode has no manual save

EA's campaign rules specify one save and no manual saving for Beskar Mode. Use that campaign's automatic save system and the same wait-before-quitting habit. If you want separate manual restore points for future play, start a separate campaign with Beskar disabled; changing graphics or repairing files will not change the existing campaign's save rules.

Keep this separate from Permadeath and other campaign modifiers. A deliberate single-save restriction and a failed save write need different responses.

Steam Cloud conflict or missing progress on another PC

These steps apply to Steam Cloud. EA app and Epic players should use their own client's sync controls rather than Steam's menu path.

1. Close the game on the second PC. Open Steam on the PC where you last saw the correct campaign and let it finish synchronization.
2. For the game's cloud setting, open Library → right-click the game → Properties → General. Check the Cloud Synchronization control; when it is disabled, progress stays local to that device.
3. If Steam reports that synchronization failed, resolve that message before launching another session. Repeatedly choosing to play anyway can create competing local and cloud progress.
4. If a conflict window appears, match its timestamps to your actual last session and device. A newer timestamp from an unwanted test is less useful than the copy containing the campaign you intend to keep.
5. After resolving the conflict, launch on one device and verify the mission and objective before playing on another.

Valve explains these behaviors in its Steam Cloud guide. For an example, if you completed a mission on PC A last night but only opened an older campaign on PC B this morning, choose by the progress you need, not just the calendar date.

A save crashes on loading

Install the current game update and verify or repair the game files. Then compare the affected save with another existing save, keeping the original intact. If every save fails, follow the PC crashing guide; if only one fails, report that narrower trigger along with the mission, installed version and mod list.

If the campaign used mods, check their current compatibility before testing a different mod configuration. Preserve a copy of the campaign before any restore, removal or file edit. File verification repairs the installation; it does not establish that an individual save can be recovered.

A loaded save is stuck at an objective

Patch 1.2 fixes progression blocked after saving in the Retake Luunata elevator, an unusable console in that mission's third exploration phase, and an unresolved Speak with Kabb objective when its conversation was unavailable. Update, load the affected campaign and retry the named interaction. If it still fails, record the displayed objective and the action that fails.

Those are progression fixes, distinct from recovering a missing file. The selected 1.2 fixes help identify which problem the update actually addresses.

Sources and review

Checked October 26, 2026: EA's troubleshooting and campaign guidance, Valve's Steam Cloud instructions and EA's Patch 1.2 notes, linked at the relevant steps. The symptom table, session comparison and test order are our editorial synthesis of those rules. Use them to isolate the failure and preserve a useful support report; they are not a promise to recover overwritten progress.