If Star Wars Zero Company started crashing at the opening screen when you press “A” after the October 15, 2026 update, treat it as a possible SteamOS/Proton compatibility regression. There is no confirmed Steam Machine fix yet. Work through the reversible checks below, then report the crash with your exact SteamOS and Proton versions if it persists.
Do not start by changing BIOS settings or buying hardware. Those measures address separate Windows PC issues described by EA, not the reported Steam Machine failure.
| # | 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 |
As an Amazon Associate I earn from qualifying purchases.
What changed with patch 1.2
Steam lists patch 1.2 as the current update for Star Wars Zero Company. Electronic Arts dated its 1.2 notes October 15, 2026. The update added Campaign Modifiers and included several bug fixes in addition to performance and stability work.
Free tools Windows power users keep installed
One-click scans. No signup required.
| Documented change or report | Date | What it means for a Steam Machine |
|---|---|---|
| Patch 1.2 released | October 15, 2026 | The timing matches the reported start of the opening-screen crash, but timing alone does not prove every Steam Machine is affected. |
| 1.2 stability fixes | October 15, 2026 | EA lists performance issues, a Utility Tutorial softlock, a unit-cycling softlock, and a crash when closing the game from the main menu. |
| Steam Community report | October 15, 2026 | One player reported a crash at the opening prompt immediately after pressing “A”; Proton 10.0-4, Proton Experimental and other Proton versions reportedly failed to restore launch. |
| SteamOS status in that report | October 15, 2026 | SteamOS support was described as formally unsupported, so behavior can depend on future game or Proton changes. |
The 1.2 notes do not claim to fix a Steam Machine launch crash. The listed main-menu fix concerns closing the game, which is a different failure from crashing before the main menu appears.
#1 Best Overall
- Star Wars: Empire at War Gold Pack PC
EA’s September 9, 2026 patch 1.1 notes also recorded several crash fixes, including a Beskar-mode crash, general crash issues, updated minimum suggested NVIDIA and AMD game-ready drivers, and save corruption after a sudden or forced shutdown. Those historical fixes show that crashes have been addressed before, but they do not establish a current SteamOS solution.
Identify your exact failure before changing anything
Write down where the game stops. “Crashes when I press A” is materially different from a crash during a loading screen or when closing the menu, and the distinction helps support staff match your case to known issues.
- Opening prompt: the game reaches the first screen, then exits or returns to Steam as soon as you press “A” to continue.
- Loading crash: the prompt works, but the process fails while loading the menu or a mission.
- Main-menu closing crash: the game runs, then fails when you choose to quit from the menu. EA specifically lists this case as fixed in patch 1.2.
Also note the SteamOS build, the Proton tool selected, whether the crash happens every time, and whether you use launch options, mods, DLL overrides, overlays, frame-generation settings or upscaling tweaks. These details let you undo one variable at a time instead of changing several things and losing the useful comparison.
Run the reversible SteamOS and Proton checks first
The following sequence changes configuration or replaces game files; it does not alter firmware or processor settings. None is documented by EA as a guaranteed Steam Machine fix. They are standard diagnostics that can identify an incomplete update or a configuration conflict.
1. Finish every game and SteamOS update, then restart
- Open the game’s Library entry and allow Steam to finish any pending download for Star Wars Zero Company.
- Open the SteamOS system-update control and install any available operating-system update.
- Restart the Steam Machine completely rather than only returning to the desktop or suspending the session.
- Launch the game once without changing any other setting and record whether the crash still occurs at the same point.
A restart clears a stale process and ensures the game and operating system are using the versions you think they are. It is a state reset, not evidence that the patch regression has been repaired.
2. Test installed Proton versions through Steam Properties
- In the Library, highlight Star Wars Zero Company, open its game menu and choose Properties.
- Open Compatibility and enable the option to force a specific Steam Play compatibility tool.
- Test the Proton versions already installed on the machine one at a time. Include the version that worked before patch 1.2, Proton 10.0-4 and Proton Experimental if they are available.
- After selecting a tool, close Properties, launch the game and test the same action that triggered the crash. Return to Properties before changing to the next tool.
The contemporaneous report says Proton 10.0-4, Proton Experimental and other versions did not restore launch on that player’s machine. Therefore, switching Proton is a diagnostic comparison, not a “best Proton version” recommendation. If every installed tool fails at the same opening prompt, record that result rather than repeatedly reinstalling Proton.
3. Verify the game files
- Open the game’s Properties from the Library.
- Select Installed Files.
- Choose Verify integrity of game files and wait for Steam to complete the check.
- Allow Steam to redownload any file it identifies, then restart the game without adding launch options.
Verification can repair a partial or damaged patch download. No source documents a Zero Company-specific verification fix, so a clean result does not rule out a compatibility regression.
Recommended Free Tools
4. Remove configuration variables
Temporarily return the game to a plain launch:
- Clear all text in Properties > General > Launch Options.
- Disable DLL overrides, compatibility tweaks and third-party mods.
- Turn off overlays that inject into the game process.
- Undo frame-generation, upscaling or other performance-layer options that you added outside the game’s default settings.
Retest after each category is disabled. If the game launches, re-enable one change at a time to identify the conflicting setting. The available reports do not identify a particular override as the cause on Steam Machine, so these actions isolate variables rather than apply a known patch.
5. If you reach the menu, simplify graphics temporarily
Only use this branch if the game gets far enough to open its settings. Disable DLSS and other advanced graphics features, apply the changes, exit normally and launch again. If your crash always occurs at the opening prompt before the menu, graphics settings cannot be changed in-game; do not treat this step as applicable to that symptom.
6. Re-test with a controlled baseline
After each change, keep the same Proton tool, resolution and input method long enough to reproduce the original action. A successful launch should be tested through the menu and, if possible, into a short session. If the crash returns only after restoring one override or mod, leave that item disabled and include its name in your report.
Rank #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
How to read the results
A result is useful even when it does not solve the crash. If updating and restarting changes the crash point, note both the old and new behavior. If verification downloads files and the game then launches, the original installation may have been incomplete; if verification finds nothing, that simply makes damaged files less likely.
If one Proton tool launches while another fails, keep the working tool selected and record its complete name and version. That is a compatibility observation, not proof that it is universally the best choice. If every installed tool fails at the same “Press A” action, repeated Proton downloads are unlikely to add information. Move to a clean configuration and then escalate with the complete test history.
Likewise, a launch after removing an overlay, mod or launch option identifies a configuration conflict only on that installation. Re-enable items individually if you need to find the exact one, and stop as soon as the crash returns. Changing several settings simultaneously makes it impossible to tell which change mattered.
Common pitfalls that make diagnosis harder
- Confusing two different crashes: the 1.2 note about closing the game from the main menu does not describe an exit at the opening prompt.
- Changing too many variables: switching Proton, deleting options and changing graphics in one attempt removes the comparison that support needs.
- Assuming a Windows fix transfers to SteamOS: NVIDIA driver and Intel tuning guidance is scoped to supported Windows PC configurations.
- Testing only once: record whether the failure is repeatable and at what exact action, rather than reporting only that the game “does not work.”
- Forgetting the pre-update baseline: state which Proton tool and settings worked before October 15, 2026, if you know them.
- Buying hardware as a first response: no dock, controller, SSD, graphics card or other replacement has been identified as a remedy for this software compatibility symptom.
EA guidance that applies to supported Windows PCs, not every Steam Machine
EA’s developer issue update discusses crashes on PCs using certain NVIDIA GPUs or Intel processors. Those instructions target supported Windows configurations and should not be presented as a general SteamOS remedy.
NVIDIA systems using DLSS
EA says crashes that occur while using DLSS with NVIDIA Game Ready Driver 610.88 or older may improve after updating to the latest Game Ready Driver. The relevant sequence is:
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
- Confirm that the computer is a supported NVIDIA Windows PC and that DLSS is enabled.
- Check the installed Game Ready Driver version.
- If it is 610.88 or older, install the current Game Ready Driver from NVIDIA’s normal driver channel.
- Reboot Windows, then test the game first with default graphics before re-enabling optional features.
Driver packages for Windows do not provide a documented fix for a SteamOS/Proton launch crash. Do not attempt to apply this threshold to an AMD system or assume it changes SteamOS’s support status.
Intel 13th- or 14th-generation desktop processors
EA also says BIOS updating may help instability on systems using Intel 13th- or 14th-generation desktop processors. As an alternative, its issue guidance describes lowering the Intel Extreme Tuning Utility Performance Core Ratio from 55x to 54x, 53x or 52x.
- Use this branch only when the device actually has one of those Intel desktop processors and you are troubleshooting the Windows PC issue EA described.
- Update the motherboard BIOS according to its manufacturer’s instructions before considering a ratio change.
- Changing a core ratio affects system performance and stability. Record the original 55x value, change only one setting, and restore the original value if the system becomes unstable.
- Do not change processor ratios on a Steam Machine merely because the opening prompt crashes; the available report does not connect that symptom to Intel tuning.
When Proton switching and verification do not help
If the game still exits at “Press A” after updates, a restart, clean files and a plain configuration, the remaining evidence points to an unresolved compatibility issue rather than a missing universal setting. SteamOS being formally unsupported means a working result may require a future game patch or Proton change; there is no documented way to force one today.
Do not spend money on a dock, controller, SSD, graphics card or other generic hardware as a crash fix. The failure is reported at the software compatibility layer, and no hardware replacement has been identified as a remedy.
PC Slower Than It Used to Be?
A free scan shows the junk files, broken settings and background clutter dragging Windows down - then fixes them in one click.Free scan · Windows 10 & 11Crashes, 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 minuteSend a report that developers can act on
EA’s issue update says the developers were aware of crash and CPU-threading problems and were working on fixes. A precise report helps them separate the Steam Machine regression from the NVIDIA and Intel cases.
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
Include all of the following:
- Game name and patch number: Star Wars Zero Company, patch 1.2.
- The date the problem began and whether it started immediately after the October 15, 2026 update.
- The exact failure point: opening prompt after pressing “A,” loading screen, mission, or menu exit.
- SteamOS version and hardware model.
- Every Proton tool tested, including the one that worked before the update, Proton 10.0-4 and Proton Experimental if tested.
- Whether file verification completed successfully.
- Launch options, mods, DLL overrides, overlays and graphics features that were enabled or removed.
- Whether the crash is repeatable and whether changing input devices changes the result.
Use EA or Bit Reactor’s official support channels and retain any crash logs requested there. State that the report concerns SteamOS/Proton and that the crash occurs before the main menu if that is your symptom. Avoid describing the 1.2 main-menu closing fix as a solution; it is a separate issue documented in the patch notes.
Quick decision guide
| Path | What it changes | Applies to | Reversible? | Evidence status |
|---|---|---|---|---|
| Update and restart | Current game and operating-system state | SteamOS/Proton | Yes | General diagnostic practice |
| Switch Proton tool | Compatibility runtime only | SteamOS/Proton | Yes | General diagnostic; report says several versions failed after 1.2 |
| Verify game files | Downloaded game data | SteamOS/Proton and other Steam installs | Yes | General diagnostic; no Zero Company-specific success documented |
| Remove overrides and mods | Per-game configuration | SteamOS/Proton and Windows | Yes | General isolation step |
| Update NVIDIA driver for DLSS | Windows graphics driver | Supported NVIDIA PCs using DLSS and driver 610.88 or older | Usually, through driver rollback | EA guidance |
| BIOS or Intel ratio adjustment | Firmware or processor behavior | Specific Intel 13th- or 14th-generation desktop PCs | Partly; restore settings where supported | EA guidance, not a SteamOS fix |
Frequently Asked Questions
Is there a confirmed fix for Zero Company crashing when I press A on a Steam Machine?
No. The October 15, 2026 report describes the opening-screen crash, but it does not establish a universal fix. Patch 1.2’s documented crash fix concerns closing the game from the main menu, not launching through the opening prompt.
Which Proton version is best after patch 1.2?
There is no confirmed best version. The report says Proton 10.0-4, Proton Experimental and other versions failed on that machine. Test installed versions one at a time, including the version that worked before the update, and record the result.
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 →Will verifying game files fix the SteamOS crash?
Verification can replace files damaged or incompletely downloaded during an update, but no Zero Company-specific verification success is documented. A clean verification result does not rule out a Proton compatibility regression.
Should I change BIOS settings or Intel core ratios on my Steam Machine?
Not for this symptom. EA’s BIOS and 55x-to-54x, 53x or 52x Performance Core Ratio guidance is for instability on specific Intel 13th- or 14th-generation desktop PCs, not a documented SteamOS opening-prompt crash.
Does updating an NVIDIA driver fix a SteamOS or Proton launch failure?
EA’s 610.88-or-older threshold applies to supported NVIDIA Windows PCs using DLSS. Windows Game Ready drivers are not documented as a fix for SteamOS or Proton.
Can a controller, dock or SSD solve the crash?
No hardware replacement has been identified as a remedy. Treat this as a software compatibility problem and complete the reversible game, Proton and configuration checks first.
What should I include in an EA or Bit Reactor bug report?
Give the patch number and start date, exact crash point, SteamOS version, hardware model, every Proton tool tested, verification result, launch options, mods, overrides, overlays, graphics settings and whether the failure is repeatable.
Why does SteamOS support status matter?
The contemporaneous report describes SteamOS support as formally unsupported. That means compatibility can depend on a future game update or Proton change, and a working result on one Steam Machine is not proof that every device will behave the same way.
The Bottom Line
Start with updates, a full restart, Proton comparisons, file verification and a clean configuration. These reversible checks may isolate a damaged download or conflicting option, but none is a confirmed cure for the reported post-1.2 SteamOS crash. If the game still fails at “Press A,” document the exact environment and send it to EA or Bit Reactor rather than changing BIOS settings or buying hardware.
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.
Quick wins for a faster PC:
Repair Windows errors before they cause bigger problemsFix Now →Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →Clear out junk files and repair common Windows errorsFree Scan →
