What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
iTechGuides is reader-supported. When you buy through links on our site, we may earn an affiliate commission. As an Amazon Associate I earn from qualifying purchases. Learn more
If Star Wars Zero Company started crashing at the opening “Press A” prompt after patch 1.2, released October 15, 2026, you are likely seeing a SteamOS/Proton compatibility regression rather than a normal in-game crash. There is no documented, universal Steam Machine fix yet. Work through the reversible checks below, then report the exact failure if the game still will not reach its menu.
What changed in patch 1.2
Electronic Arts’ 1.2 patch notes, dated October 15, 2026, list Campaign Modifiers and several bug fixes. In the Performance and Stability section, EA says it fixed various performance problems, a Utility Tutorial softlock, a softlock caused by cycling units, and a crash that occurred when closing Star Wars Zero Company from the main menu.
| # | Preview | Product | Price | |
|---|---|---|---|---|
| 1 |
|
Star Wars Empire At War Gold Pack | $54.99 | Buy on Amazon |
| 2 |
|
Star Wars: Battlefront - Standard Edition - PC | $9.99 | Buy on Amazon |
| 3 |
|
Star Wars Battlefront II | $13.78 | Buy on Amazon |
Those notes do not say that patch 1.2 fixes launching on SteamOS, Proton, or a Steam Machine. A Steam Community report posted on the same date describes a different failure: the game reaches the opening screen, then crashes when the player presses “A” to continue. The reporter says Proton 10.0-4, Proton Experimental, and other Proton versions all failed after the update. That is strong evidence of a post-update compatibility regression on at least one Steam Machine, not proof that every Steam Machine has the same problem.
The game is sold as a single-player PC title through Steam. The contemporaneous report also says SteamOS support is formally unsupported, so compatibility can depend on the game build and future Proton or SteamOS changes. Treat the procedures below as diagnosis and recovery attempts, not a guaranteed workaround.
#1 Best Overall
- Star Wars: Empire at War Gold Pack PC
First, identify exactly where the crash occurs
Before changing anything, note the last screen you can reach. This separates the reported launch regression from crashes that occur later.
- Opening-prompt crash: the game displays the initial screen and exits when you press “A” to continue. This matches the October 15 Steam Community report.
- Loading-screen crash: the game accepts the prompt but closes while loading the main menu or a save.
- Menu or mission crash: the game reaches the menu or gameplay and then exits. Patch 1.2’s documented fixes include a main-menu closing crash, but that is not the same as a crash at the opening prompt.
Write down the exact point of failure, whether the process closes to the Steam library or freezes first, and whether the behavior changed immediately after patch 1.2. These details will matter if you need to submit a support report.
Use this order of operations
The sequence starts with changes that are easy to undo and avoids altering firmware unless EA’s narrowly scoped PC guidance applies. Stop when a test produces a stable launch, and change only one variable at a time.
Recommended Free Tools
| Step | What it changes | SteamOS/Proton relevance | Reversible? | Evidence status |
|---|---|---|---|---|
| Update and restart | Refreshes the game, SteamOS, and running session | Applies to the Steam Machine | Yes | General state-reset practice; not a Zero Company-specific fix |
| Test installed Proton versions | Changes the Windows-compatibility layer used to launch the game | Directly relevant | Yes | Diagnostic attempt; the October 15 report says several versions failed |
| Verify game files | Checks the installed patch and redownloads damaged files | Directly relevant | Yes | Standard Steam troubleshooting; no documented Zero Company-specific result |
| Remove overrides and launch options | Returns the prefix and startup command closer to defaults | Directly relevant | Yes, if you record the old settings | General isolation step |
| Disable advanced graphics after reaching the menu | Removes DLSS and similar rendering variables | Relevant only if the game starts far enough | Yes | EA documents DLSS/driver advice for specific supported NVIDIA PCs |
| Update BIOS or alter Intel ratio | Changes system firmware or CPU tuning | Not a general SteamOS remedy | BIOS changes require care; ratio can be restored | EA guidance limited to certain Intel desktop systems |
1. Fully update the Steam Machine and restart it
- Open Steam’s system update area and install every available SteamOS update.
- In the Steam library, select Star Wars Zero Company and allow any pending game update to finish. Confirm that the installed build is patch 1.2 or newer if Steam displays a version or update state.
- Choose Steam’s restart or power-cycle option and wait for the machine to return to the library.
- Launch the game without changing any other setting and test the opening prompt.
A restart clears a stalled process, reloads updated runtime components, and ensures that Steam is not still applying the patch in the background. It is a sensible reset, but neither EA nor the Steam Community report identifies it as a confirmed cure.
2. Test the Proton versions already installed
Proton switching is the most relevant reversible diagnostic for a SteamOS launch failure. It can reveal whether a particular compatibility layer handles the new game build differently, but there is no confirmed “best Proton version” for this patch.
- Open the Steam library and highlight Star Wars Zero Company.
- Open the game’s Properties.
- Select Compatibility.
- Enable the option to force a specific Steam Play compatibility tool, then select one Proton version that is already installed.
- Close Properties, launch the game, and test the same action at the opening screen.
- If it still crashes, return to Compatibility and test the next installed version. Include the version that worked before patch 1.2, if you know it.
Keep a simple test log containing the Proton version and result: reaches prompt, crashes on “A,” crashes while loading, or reaches the menu. The October 15 report specifically says Proton 10.0-4 and Proton Experimental, along with other versions, did not restore launch on that reporter’s machine. That means switching versions is worth testing, but it should not be presented as an established fix.
How to interpret the result
- One version works: leave that version forced and record it, because a later game or Proton update may change the result.
- Every installed version fails at the same prompt: the pattern is more consistent with a game-build or SteamOS compatibility regression than with one bad Proton release.
- The crash point changes: record both versions. A change from an immediate prompt crash to a loading crash is useful diagnostic information even if it is not a complete solution.
3. Verify the installed game files
A patch can fail to apply cleanly, leaving a missing or damaged file. Steam’s integrity check can identify that state and redownload files. No source documents a Zero Company-specific success rate, so regard this as standard troubleshooting.
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 problems- Open the game’s Steam library page.
- Open Properties and select Installed Files (the wording may appear as the installed-files section in your Steam client).
- Choose Verify integrity of game files.
- Wait for Steam to finish. If it reports files that need to be reacquired, let the download complete before launching.
- Retest with the same Proton version used in your previous test, then test another version only if necessary.
Do not interrupt the verification or immediately switch several other settings; otherwise you will not know whether a repaired file changed the outcome.
4. Remove custom launch options, overrides, mods, and overlays
Custom configuration can mask a regression or create a second failure. Return the game to a baseline before drawing conclusions about patch 1.2.
- In the game’s Steam Properties, clear every custom Launch Options entry. Save the text elsewhere first if you may need it again.
- Disable DLL overrides, compatibility-prefix tweaks, and manually added environment variables associated with this game.
- Temporarily remove or disable mods and injectors.
- Turn off overlays and frame-generation or upscaling tweaks that you added outside the game’s default configuration.
- Launch with one known Proton version and test the opening prompt.
The available reports do not identify a particular override, mod, or overlay as the cause on Steam Machine. The purpose of this step is isolation: if the crash disappears, re-enable additions one at a time until the conflicting setting is identified.
5. If you reach the menu, simplify graphics settings
Only use this branch if the game gets far enough to open its settings. If it crashes before the menu, graphics changes inside the game cannot affect that launch path.
Outdated Drivers Are Slowing You Down
One free scan finds every outdated or missing driver and matches the right update for your exact hardware.Free scan · exact hardware matchWindows 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 reinstallRank #2
- Product Packaging Notice: This product includes a download code in packaging, no physical media disc included.
- Visit classic planets from the original Star Wars trilogy, detailed with an unprecedented amount of realism and sense of authenticity that will transport you to a galaxy far, far away
- Pilot a diverse set of ground-based vehicles including nimble speeder bikes, massive AT-ATs, and more
- Encounter a variety of beloved characters from the original trilogy such as C-3PO and R2-D2
- Pilot the Millennium Falcon, X-wings, TIE fighters, and more of your favorite vehicles in exhilarating aerial combat
- Open the game’s graphics or display settings.
- Disable DLSS and any other advanced upscaling, frame-generation, or experimental rendering option you enabled.
- Apply the changes, exit the game normally if possible, and launch again.
- If stability improves, re-enable one feature at a time to identify the trigger.
EA’s developer issue update says that on supported NVIDIA PC configurations, crashes while using DLSS with NVIDIA Game Ready Driver 610.88 or older may improve after updating to the latest Game Ready Driver. That guidance targets NVIDIA drivers on supported PC setups; it is not evidence that installing a Windows driver or changing DLSS will fix a SteamOS/Proton crash at “Press A.”
6. Apply EA’s Intel guidance only to the specified hardware
EA also says BIOS updating may help instability on systems using 13th- or 14th-generation Intel desktop processors. As an alternative, its issue update describes lowering the Intel Extreme Tuning Utility Performance Core Ratio from 55x to 54x, 53x, or 52x.
Do not use those instructions as a general Steam Machine remedy. They are scoped to the Intel desktop hardware and instability scenario described by EA, and they do not establish a solution for SteamOS, Proton, AMD processors, laptops, or other devices.
- Identify the processor model before changing firmware or tuning.
- Use the system or motherboard manufacturer’s documented BIOS procedure.
- Record the original ratio and other settings so you can restore them.
- Do not change firmware or CPU ratios merely because the game crashes at the opening prompt unless your hardware matches EA’s stated case.
Why patch 1.2’s crash fix may not help
Patch notes are specific, not a promise that every crash has been eliminated. EA’s wording concerns a crash that occurred when closing the game from the main menu. The Steam Machine report concerns pressing “A” on the opening screen before the main menu. Those are different execution paths, so a player can have the reported launch crash even after installing patch 1.2 successfully.
The Tool Desk
Outbyte PC Repair FREERepair Windows errors before they cause bigger problemsFix Now →Outbyte Driver Updater FREEFix the driver behind crashes, sound loss and screen glitchesFind Drivers →EA’s earlier 1.1 notes, dated September 9, 2026, list various crash fixes, a Beskar-mode crash fix, updated suggested NVIDIA and AMD game-ready drivers, and a save-corruption fix after sudden or forced shutdown. Those historical fixes show that the game has had documented stability work, but they do not supply a current SteamOS solution.
How to make each test useful
Run the same short test after every change: start the game, wait for the opening screen, press “A” once, and observe whether it reaches the menu. Avoid changing the Proton version, launch options, graphics settings, and SteamOS build simultaneously. A one-variable method tells you whether a change affected the crash rather than merely coincided with it.
Record the date, patch number, SteamOS version, Proton tool, and result. If the game freezes instead of closing, note how long it remains unresponsive and whether Steam displays a force-close prompt. Also note whether the controller disconnects, whether audio continues, and whether the same failure occurs with keyboard input if one is available. These observations do not prove a cause, but they make a support report reproducible.
What a Proton result can and cannot prove
A successful launch on one Proton build shows only that the game can run with that combination of game files, SteamOS, and compatibility layer. It does not establish a universal recommendation. Conversely, failure on Proton 10.0-4 and Experimental does not prove that every Proton release is broken; it describes the contemporaneous report from one machine.
Do not delete prefixes or saves as a first response. The documented steps support reversible configuration testing, file verification, and removal of overrides. Destructive cleanup can remove useful diagnostic state and may complicate recovery if a save or configuration is not backed up.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.When to stop troubleshooting and report the crash
If updating, verifying, testing Proton, and removing custom settings produce the same result, further random changes are unlikely to provide useful information. Submit the issue through EA or Bit Reactor support channels and include a reproducible description.
Include these details
- The game version, including confirmation that patch 1.2 installed.
- SteamOS version and Steam Machine model or hardware details.
- Every Proton version tested, including Proton 10.0-4 and Proton Experimental if applicable.
- Whether the crash occurs exactly when pressing “A,” during loading, at the menu, or in a mission.
- Whether file verification found anything.
- All launch options, overrides, mods, overlays, and graphics changes that were enabled or removed.
- Whether the game ever reached the menu after the update.
EA’s official issue post says the developers were aware of crashes involving certain NVIDIA GPUs or Intel processors and of CPU-threading issues, and that they were working on fixes. Supplying precise reproduction data helps distinguish those supported-PC cases from the separate SteamOS/Proton regression reported after patch 1.2.
Rank #3
- Revamped single-player experience includes smarter AI enemies and allies, plus a greater emphasis on story told through open-ended mission-based objectives.
- New space battles allow you to dogfight in X-wings, TIE fighters, Jedi starfighters and several other starcraft, or fight it out on foot aboard an enemy capital ship.
- Special opportunities throughout the game for players to earn the ability to wield a lightsaber and use their favorite Force powers as a Jedi.
- More than 16 new battlefronts on land and in space, including many from Star Wars: Episode III Revenge of the Sith such as Utapau, Mustafar and the space battle above Coruscant
- All-new classic trilogy locations including the Death Star interior, classic space battles and the fight aboard the Tantive IV, Princess Leia’s blockade runner seen at the beginning of Star Wars: Episode IV A New Hope
What not to buy or change for this problem
This is a software-compatibility issue. A new dock, controller, SSD, GPU, or other generic hardware accessory is not an evidence-based fix for a crash at the opening prompt. Likewise, do not assume that a different controller will solve a process that exits when the game receives the “A” input; test with the existing controls first and document the exact behavior.
Quick wins for a faster PC:
Clear out junk files and repair common Windows errorsFree Scan →Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →Practical conclusion
The most defensible diagnosis is a possible patch 1.2 regression affecting at least one Steam Machine under SteamOS/Proton. Start with updates and a restart, then test installed Proton versions, verify files, and remove custom launch settings. Disable advanced graphics only if you can reach the menu. Reserve BIOS or Intel ratio changes for the specific hardware scenario EA describes. If every reversible test fails at “Press A,” retain your test log and report the issue rather than treating an unsupported SteamOS configuration as proof that the hardware is defective.
Frequently Asked Questions
Is there a confirmed Proton version that fixes Zero Company patch 1.2 crashes?
No. The contemporaneous Steam Community report says Proton 10.0-4, Proton Experimental, and other versions failed on that Steam Machine. Test installed versions as a reversible diagnostic, but no universal best version has been documented.
Why does Zero Company crash when I press A?
That is the opening-prompt failure described in the October 15, 2026 report. It occurs before the main menu and differs from patch 1.2’s documented fix for a crash while closing the game from the menu.
Will verifying Steam files fix the Steam Machine crash?
Verification can redownload incomplete or damaged files, so it is worth trying. However, no Zero Company-specific result confirms it as a fix for this post-update SteamOS problem.
Free tools Windows power users keep installed
One-click scans. No signup required.
Should I install a Windows NVIDIA driver on SteamOS?
No. EA’s driver advice applies to supported NVIDIA PC configurations using DLSS and Game Ready Driver 610.88 or older. It is not a documented SteamOS solution.
Should I change BIOS settings or Intel Core Ratio?
Only if your system matches EA’s stated case: a 13th- or 14th-generation Intel desktop processor with the relevant instability. EA describes BIOS updating or lowering the ratio from 55x to 54x, 53x, or 52x. These are not general Steam Machine fixes.
Does SteamOS officially support Star Wars Zero Company?
The contemporaneous report describes SteamOS support as formally unsupported. That means a game or Proton update may be required, and success on one Steam Machine does not guarantee success on another.
What should I send support?
Include the patch number, SteamOS version, Steam Machine hardware, every Proton version tested, the exact crash point, verification results, launch options, overrides, mods, overlays, and whether the game ever reached the menu.
Should I buy a new controller, dock, SSD, or GPU?
No evidence links those accessories to this crash. Treat it as a software compatibility problem and complete the reversible Steam and Proton checks first.
The Bottom Line
Bottom line: Patch 1.2 may have introduced a SteamOS/Proton launch regression that crashes at “Press A” on at least one Steam Machine. Update and restart, test installed Proton versions, verify files, and remove custom overrides. Use EA’s DLSS, driver, BIOS, and Intel-ratio advice only for the specific supported PC hardware it names. If the crash persists, document the test results and report it to EA or Bit Reactor.
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.
