Do these 3 things before closing this tab:
1Clear out junk files and repair common Windows errors2Fix the driver behind crashes, sound loss and screen glitches3Repair Windows errors before they cause bigger problemsUpdate Star Wars Zero Company to version 1.2 before trying workarounds. Electronic Arts released 1.2 on October 15, 2026, after version 1.1 addressed several save and progression failures. Then protect your next save by quitting only after you control Hawks or a mission has started, wait a few seconds, and use the platform troubleshooting steps for crashes, freezes, or damaged files. Campaign Modifiers can also change rules deliberately, so check the campaign’s Difficulty Settings before treating an unexpected result as a bug.
Start with the current build
As of October 16, 2026, version 1.2 is the latest listed update for Star Wars Zero Company. Install every update offered for your platform before loading an affected campaign. A workaround cannot reliably correct a defect that the game update already fixes, and continuing on an old build can make later diagnosis harder.
As an Amazon Associate I earn from qualifying purchases.
| Version | Release date | Why it matters for this problem |
|---|---|---|
| 1.1 | September 9, 2026 | Addressed temporarily deleted Beskar saves, corruption after a sudden or forced shutdown, and a progression block in inspection mode. The notes also include graphics-driver guidance. |
| 1.2 | October 15, 2026 | Addressed save-reload modifier and ability failures, the Double Down Defense bonus disappearing after reload, the Retake Luunata elevator progression block, the Speak with your Other Companions epilogue block, utility-tutorial and inspection softlocks, and a crash when closing from the main menu. |
On PC, use the EA app’s update control for the game. On PlayStation 5 or Xbox Series, use the console’s normal game-update check. The exact menu wording can vary by system software, but the requirement is the same: confirm that the installed build is 1.2 or later before testing the save again. If your platform offers a newer build after 1.2, install that instead; the version number shown by the platform is the one to record in a support report.
Windows Errors? Fix Them Before They Spread
Repair common Windows errors and clear accumulated junk for a smoother, more stable PC - no reinstall needed.Free scan · no reinstallCrashes, No Sound, or Screen Glitches?
Random freezes, missing sound and display glitches usually trace back to one bad driver. Find and replace yours safely.Free scan · under a minuteProtect saves when you leave a session
Save timing is a separate issue from a corrupted file. EA Help states: “If you quit the game while you’re not controlling Hawks, your latest progress might not finish saving.” The practical rule is to regain control of Hawks, or wait until the mission has actually begun, and then allow a few seconds before quitting.
#1 Best Overall
- Standard Edition for PlayStation 5 (disc) includes the full Star Wars Zero Company game. Single-player turn-based tactics set in the twilight of the Clone Wars—lead Hawks and Zero Company in an intense campaign.
- Build your squad from clone troopers, scoundrels, astromechs and even a Jedi—combine abilities and gear in deep Tactical-Strategy combat.
- Plan at your base, adapt on dynamic battlefields and make decisions that shape missions and replayability in this cinematic Star Wars story.
- Customise Hawks and your operatives, tailor loadouts and unlock powerful squad synergies designed for Strategy, Turn-Based and Sci-Fi fans.
Use this exit sequence
- Finish the action you want recorded and wait for control to return to Hawks.
- If a mission is loading or transitioning, wait until the mission begins instead of closing during the transition.
- Remain in control for a few seconds so the save write can complete.
- Quit through the game’s normal menu rather than powering off the device, suspending the title abruptly, or terminating the process.
Do not force a shutdown while the game is saving. Version 1.1 specifically fixed corruption that could follow a sudden or forced shutdown, which means that an interrupted write is a documented failure mode rather than a harmless shortcut.
If you already quit at the wrong point, reopen the game and check the affected campaign before making additional changes. Avoid repeatedly launching and closing the title while testing; each abrupt exit can create another incomplete save attempt. When checking a suspected missing save, first note the last objective or room that definitely loaded. That gives you a clear comparison instead of relying on memory.
Match the symptom to the documented fix
The table below separates issues that have a listed patch fix from issues that call for the general platform workflow. Use the symptom that most closely matches what you see, then perform the action in the last column.
| What you see | Documented context | What to do |
|---|---|---|
| A Beskar save disappeared, or Beskar caused a crash | Version 1.1 lists fixes for temporarily deleted Beskar saves and a Beskar-related crash. | Update to at least 1.1, preferably 1.2, then relaunch and check the campaign. |
| A bonus, modifier, or ability changes after saving and reloading | Version 1.2 lists the Double Down Defense bonus disappearing after reload and several save-loaded ability failures. | Install 1.2 or later. Reproduce only after confirming the update, and record the modifier and ability settings if the mismatch remains. |
| Retake Luunata stops in the elevator | Version 1.2 lists a progression fix for the elevator section. | Update before replaying or retrying the mission. If the block persists on 1.2 or later, report the exact elevator step and save slot. |
| The epilogue will not advance past Speak with your Other Companions | Version 1.2 lists this epilogue progression fix. | Update, reload the campaign, and document which companion interaction was last completed if it still stops. |
| The utility tutorial or inspection mode softlocks | Version 1.2 lists both utility-tutorial and inspection softlock fixes; version 1.1 also addressed an inspection-mode progression block. | Use 1.2 or later. Note the screen, input, and objective that remain active when reporting a repeat. |
| The main menu crashes when you close the game | Version 1.2 lists a main-menu shutdown crash fix. | Update, then use the normal quit command. If the crash continues, complete the platform troubleshooting steps below. |
| Progress is missing after quitting | EA identifies quitting while you do not control Hawks as a reason the latest progress might not finish saving. | Repeat the Hawks-control exit sequence and avoid forced shutdowns. |
| Black screen, freeze, launch failure, or an unexplained crash | These symptoms can result from service, cache, file, driver, or device problems rather than a specific mission defect. | Restart, check service status, clear the applicable cache, repair PC files if applicable, and update graphics drivers. |
A patch fix does not necessarily repair an already damaged save. After updating, load the smallest affected campaign test you can identify and check whether the objective, bonus, or ability now behaves correctly. If a known issue is gone on a new test but not on one older slot, preserve the details of that slot for EA rather than overwriting it through repeated experiments.
Run the platform troubleshooting workflow
Use these steps in order because the first actions are reversible and quick. They address launch failures, black screens, crashes, freezes, and files that did not update correctly. A single-player campaign can still be affected by account or platform services during downloads, updates, and authentication.
1. Restart the device
Close the game completely and restart the PC or console. Relaunch only after the restart finishes. This clears a temporary process or memory state without changing the campaign files.
Rank #2
- PC download code for EA app. Single-player turn-based tactics set in the twilight of the Clone Wars—lead Hawks and Zero Company in a gritty Star Wars campaign.
- Deluxe Edition: Unlock Clone Wars–inspired cosmetics including the Republic Officer Uniform, 100th Clone Company Armor Set and ARC Trooper Armor Set.
- Includes the Shadow Collective Cosmetic Pack with the Pyke Helmet Cosmetic, five cosmetic tattoos and five themed weapon set designs.
- Single-player turn-based tactics set in the twilight of the Clone Wars—lead Hawks and Zero Company in a gritty, cinematic Star Wars campaign.
2. Check EA and platform service status
Check EA’s service-status information and the status page for your platform before repeatedly retrying an update or load. An outage can interfere with downloads, account functions, or entitlement checks even when the campaign itself is designed for single-player use. If services are degraded, wait until they recover before drawing conclusions from a failed launch.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
3. Clear the applicable cache
On PC, clear the EA app cache using the app’s built-in cache-clear option. Console owners should use the platform’s documented cache or power-cycle procedure rather than deleting game saves. Cache clearing is intended to remove stale launcher data; it is not a substitute for deleting a campaign.
4. Repair the PC installation
On PC, run the EA app’s repair option for Star Wars Zero Company. Repair checks the installed game files and replaces files that are missing or damaged. Let the operation finish before launching the game, and do not interrupt it with a shutdown.
5. Update graphics drivers
Install the current graphics driver supplied for your hardware, then restart the PC. This step is relevant to black screens, freezes, and crashes, and it is included in the troubleshooting guidance associated with the earlier patch. Keep the game update and driver update as separate changes when possible so you can identify which one resolves the symptom.
6. Test once on the patched build
After the restart, cache operation, repair, and driver update, launch the game and reproduce the smallest possible version of the problem. Note whether the failure happens before a save loads, during a mission transition, after an ability is used, or only when closing the main menu. That distinction determines what information support can act on.
Free tools Windows power users keep installed
One-click scans. No signup required.
Do not apply PC-only repair instructions to a PlayStation 5 or Xbox Series installation. On a console, the safe equivalent is to confirm the update, restart the hardware, and use only the manufacturer’s own cache or power-cycle procedure. Avoid deleting saved data as a first-line test; the documented workflow targets stale service data and damaged installation files without intentionally removing campaign progress.
Rank #3
- Command an elite squad through a gritty and authentic Star Wars story set in the twilight of the Clone Wars. Step into the role of Hawks, a former Republic officer leading Zero Company against an emerging threat that could consume the galaxy.
Understand Campaign Modifiers before calling a rule change a bug
Campaign Modifiers are intentional campaign rules, not hidden repairs or temporary difficulty toggles. In version 1.2, they are selected under Difficulty Settings when you start a new campaign and become active after the tutorial. A modifier can therefore make a later result look like a save or progression error when the campaign is following the selected rules.
Rules that modifiers can change
- How quickly progression values increase.
- Whether and how health increases.
- How Advantage is generated.
- Bond behavior and tactical effects.
- Injury and death rules.
- Assist-shot accuracy, critical hits, and limits on perfect shots.
- Whether respecs are available or locked.
Electronic Arts documents concrete values for some options. A static death-risk option can use a 20% chance, escalating to 40% and then 80% after surviving defeats. An enemy critical-hit option can use a 5% chance. Those percentages describe game rules when the options are enabled; they are not estimates of how often players encounter bugs.
Check the campaign context
- Open the campaign’s Difficulty Settings information and list every enabled modifier.
- Confirm whether the campaign began before or after the 1.2 update.
- Record whether the unexpected result appeared immediately after the tutorial, after a save reload, or after a specific defeat or mission event.
- Compare the observed result with the selected rule, including any escalating risk described in the setting.
Do not change several modifiers and then reload while diagnosing one mismatch. A clean record of the original settings makes it possible to distinguish an intentional rule from a save-loaded ability failure. In particular, compare the state before saving with the state immediately after reloading: a rule that is consistently applied is different from a bonus or ability that disappears only across the save boundary.
Quick wins for a faster PC:
Clear out junk files and repair common Windows errorsFree Scan →Scan for outdated or missing drivers - takes under a minuteDriver Scan →Use a decision path that fits your platform and symptom
| Platform | Save or progression symptom | First reversible action | When to escalate |
|---|---|---|---|
| PC | Missing progress after an unsafe quit | Update, regain Hawks control before quitting, wait a few seconds, and relaunch. | If the same safe exit loses progress on 1.2 or later, report the save slot and timing. |
| PC | Crash, black screen, freeze, or suspected damaged files | Restart, check service status, clear the EA app cache, repair game files, and update the graphics driver. | If the failure survives all five steps, provide the driver version and exact reproduction sequence to support. |
| PlayStation 5 | Mission block, modifier mismatch, or reload failure | Confirm the game is updated, restart the console, and retest without a forced shutdown. | Report the mission, patch, save timing, and enabled modifiers if the patched build still fails. |
| Xbox Series | Mission block, modifier mismatch, or reload failure | Confirm the game is updated, restart the console, and retest without a forced shutdown. | Report the mission, patch, save timing, and enabled modifiers if the patched build still fails. |
The console steps intentionally avoid PC-only file operations. Do not apply a PC cache or repair instruction to a console unless the console manufacturer’s own support documentation provides an equivalent procedure.
These paths differ mainly in the available maintenance tools, not in the save-timing rule. On every platform, wait for Hawks to be controllable or for the mission to begin, allow a few seconds, and exit normally. On PC, add the EA app cache, file repair, and driver checks when the symptom points to installation or graphics problems.
Prepare an evidence-based support report
If the issue remains after updating and completing the reversible workflow, contact EA Help. A useful report lets support separate a known fixed defect from a new reproduction instead of asking you to repeat generic steps.
Rank #4
- BECOME THE MANDALORIAN: Step into the shoes of the legendary bounty hunter and his allies in this thrilling cooperative board game, featuring The Mandalorian and 7 iconic characters from the hit series!
- EPIC MISSIONS: Embark on exciting adventures inspired by Season 1 of The Mandalorian, where you'll cooperate, battle enemies, and solve dilemmas to complete each mission's objective.
- UNIQUE STRATEGIES: Take on different roles and challenges with each character, as they come with their own deck of cards offering unique abilities and tactics to master.
- EXPANSIVE GAMEPLAY: Explore additional rules, components, and mission types as you progress through the game, including some missions that feature a hidden traitor mechanic for added intrigue!
- IMMERSIVE STAR WARS EXPERIENCE: Immerse yourself in the captivating world of Star Wars like never before, as you and your friends work together to overcome obstacles, fight enemies, and become heroes of the galaxy!
Include these details
- Platform: PC, PlayStation 5, or Xbox Series.
- Installed game version, including whether it is 1.1, 1.2, or a later build.
- Campaign name or context, including Beskar when relevant.
- Mission, objective, room, elevator, tutorial, or epilogue step.
- Save slot and the last action that definitely loaded correctly.
- Every enabled Campaign Modifier and when the campaign was started.
- Whether you controlled Hawks when quitting and whether the shutdown was forced.
- Exact reproduction steps, written in the order they occur.
- What happened after restarting, clearing cache, repairing files, and updating drivers, as applicable to the platform.
Use a concise reproduction format
Platform: [PC, PlayStation 5, or Xbox Series]
Game version: [version shown by the platform]
Campaign/mission: [name and objective]
Save slot: [slot identifier]
Campaign Modifiers: [enabled options]
Last known good state: [what loaded correctly]
Steps: 1) ... 2) ... 3) ...
Expected result: [what should happen]
Actual result: [what happens instead]
Quit method: [normal quit or forced shutdown]Keep the sequence short and deterministic. For example, state which action was taken, whether the game was saved or reloaded, and the exact point at which the elevator, ability, modifier, or objective stopped responding. If the issue cannot be reproduced after the patch, say so rather than inferring that the original save is permanently damaged.
EA Help is the authoritative escalation destination for this workflow. Include screenshots or video if the support form accepts them, but do not replace the written sequence with a clip alone: the platform, patch, save timing, mission context, and expected-versus-actual result are what make the report actionable.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.What not to do while diagnosing
- Do not keep testing on an unpatched build when 1.2 or a later update is available.
- Do not force power off the PC or console during a transition, save, or repair operation.
- Do not delete campaign saves merely to clear a launcher cache.
- Do not change multiple Campaign Modifiers and then claim one option caused the result.
- Do not treat the 20%, 40%, 80%, or 5% modifier values as evidence of a technical failure; they are intentional settings.
- Do not repeatedly overwrite the only affected slot before documenting the last known good state.
These precautions preserve the distinction between a missed save write, a damaged installation, a known mission defect, and an intentional campaign rule. That distinction is more useful to support than a long list of unrelated tweaks.
Prevent the next save or progression failure
- Keep the game updated before beginning a long mission.
- After transitions, wait until Hawks is controllable or the mission has started, then wait a few seconds before quitting.
- Use the normal quit command and avoid forced power-offs.
- Write down enabled Campaign Modifiers when starting a campaign.
- When a reload changes an ability or bonus, stop and record the before-and-after state instead of repeatedly overwriting saves.
- For a crash or black screen, perform the restart, service-status, cache, file-repair, and driver checks before attempting the same mission repeatedly.
There is no authoritative incidence percentage for these problems. The documented figures are patch versions and the intentional modifier values above, not a claim about how common save or progression bugs are.
Frequently Asked Questions
What is the first fix for a Star Wars Zero Company save bug?
Update to version 1.2 or later, then retry the smallest reproduction. When quitting, make sure you control Hawks or the mission has begun, wait a few seconds, and use the normal quit command.
The Tool Desk
Outbyte PC Repair FREEClear out junk files and repair common Windows errorsFree Scan →Outbyte Driver Updater FREEFix the driver behind crashes, sound loss and screen glitchesFind Drivers →Why did my progress disappear after I quit?
EA says progress might not finish saving if you quit while you are not controlling Hawks. Reopen the game, check the campaign, and use the Hawks-control exit sequence for future sessions.
Which patch fixed Beskar save problems?
Version 1.1, released September 9, 2026, addressed temporarily deleted Beskar saves, a Beskar-related crash, and corruption after sudden or forced shutdowns. Version 1.2 is the newer build and should be installed instead when available.
Why does a modifier or ability look different after reloading?
Version 1.2 includes fixes for the Double Down Defense bonus disappearing after reload and several save-loaded ability failures. If the mismatch remains, record the modifier settings, campaign start date relative to the patch, and the before-and-after states.
Can Campaign Modifiers make a result look like a bug?
Yes. Modifiers are selected under Difficulty Settings for a new campaign and activate after the tutorial. They can alter health, Advantage, bonds, tactical effects, injury and death, critical hits, perfect-shot limits, progression rates, and respec availability.
Recommended Free Tools
What should I do if Retake Luunata is blocked in the elevator?
Install version 1.2 or later and retry the mission. If the elevator still blocks progression, report the exact step, save slot, platform, and patch version to EA Help.
What should PC players do for crashes or black screens?
Restart the computer, check EA and platform service status, clear the EA app cache, repair the game files, update the graphics driver, and test once on the patched build.
What information does EA Support need?
Provide the platform, installed version, campaign and mission, save slot, enabled Campaign Modifiers, last known good state, quit method, and concise numbered reproduction steps with the expected and actual results.
The Bottom Line
Install version 1.2 or later first. Protect saves by quitting only after Hawks is controllable or a mission has begun, wait a few seconds, and avoid forced shutdowns. For crashes, freezes, or black screens, restart, check service status, clear the applicable cache, repair PC files, and update graphics drivers. Check Campaign Modifiers before labeling an intentional rule a bug. If a documented issue still reproduces on the patched build, send EA Help the platform, version, mission, save timing, modifier settings, and exact reproduction steps.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
