You have hardware that meets the minimum specs. You verified the game files. You even updated your GPU driver. Yet the game still crashes the moment you hit the main menu—before you can even touch “Play.” This is not a random bug. It is a symptom of a specific handshake failure between the game engine and your system. And the standard fixes rarely address it directly.
Most crash advice for Star Wars Zero Company lumps all errors together. But the main menu crash is distinct. It happens after the splash screens, during the shader compilation that runs in the background, or when the game tries to initialize its online services. The root causes are narrow. The fixes are equally specific—and most of them are not listed in the first page of a search result.
What follows are the solutions that actually work for this particular failure point. No fluff. No “make sure your PC meets requirements.” You already checked that. Here is the non-obvious stuff.
Why the Main Menu? The Real Culprits
The main menu in Star Wars Zero Company performs several tasks in parallel. It compiles shaders for the background visuals. It connects to the game’s backend to fetch news, offers, and authentication tokens. It loads the audio engine and runs the first frame of the menu animation. Any one of these tasks can choke.
Corrupted shader cache is the single most common reason. The game stores compiled shaders locally to speed up future launches. If that cache gets corrupted—common after a GPU driver update or a sudden crash—the menu will fail to load. The game either hangs or throws a low-level fatal error.
The second culprit is a background process that conflicts with the game’s anti-cheat or overlay system. Discord overlay, Nvidia GeForce Experience, Xbox Game Bar—each can intercept the rendering pipeline at a critical moment. The game sees an unexpected change in the GPU state and aborts.
Third: the game might be trying to use your integrated GPU instead of the dedicated one. Laptop users with hybrid graphics are especially vulnerable. The main menu is not especially demanding, but the game engine checks the GPU properties at launch. If it finds the wrong adapter, it can crash before drawing a single element.
Fourth: missing runtime libraries. Microsoft Visual C++ redistributables and DirectX are often installed, but they may be the wrong version or partially corrupted. The game’s launch sequence depends on a specific DLL loading without error. If it fails, you get a silent crash to desktop.
Fixes That Target the Main Menu Crash
Clear the Shader Cache Using Disk Cleanup
Do not just delete the game’s config folder. Use the Windows Disk Cleanup tool and check the box for “DirectX Shader Cache.” This removes the entire system-level shader cache, not just the game’s. After cleaning, restart your PC. The first launch will take longer—the game recompiles every shader from scratchaaa—but the menu should load.
If you also see a “GPU Crash Dump Triggered” error, this step alone resolves it in most cases. The source material confirms that a corrupted shader cache causes repeated or stuck shader compilation at the menu.
Disable All Overlays, Not Just Steam’s
Steam’s in-game overlay is the obvious target. But the non-obvious ones are Discord, Nvidia App (formerly GeForce Experience), AMD Adrenalin, and even the Windows Game Bar. Disable them all before launching. Do not just toggle them off—quit the applications entirely.
For Discord, go to Settings > Overlay and disable the toggle. Then right-click the system tray icon and select Quit. For Nvidia, open the Nvidia App, go to Settings > General, and turn off “In-Game Overlay.” Restart the game. If the menu loads, re-enable them one by one to find the specific conflict.
Force the Game to Use Your Dedicated GPU
On Windows 11, go to Settings > System > Display > Graphics. Find Star Wars Zero Company in the list. If it is not there, click Browse and navigate to the game’s .exe file. Click Options and set it to High Performance. This forces the game to use your discrete GPU even if Windows thinks integrated is fine.
This fix is especially relevant for laptops with Nvidia Optimus or AMD Switchable Graphics. The main menu crash often disappears immediately after this change.
Install or Repair Microsoft Visual C++ Runtimes
The game requires the 2015–2022 x64 and x86 redistributables. Even if you have them installed, a repair can fix silent corruption. Go to Control Panel > Programs and Features. Find “Microsoft Visual C++ 2015-2022 Redistributable (x64).” Right-click and select Change, then Repair. Do the same for the x86 version. Restart your PC.
If you are missing any runtime, download the all-in-one package from Microsoft’s official website. Do not rely on the installer that ships with the game—it may be outdated.
Add Specific Launch Options
Right-click Star Wars Zero Company in Steam, go to Properties > General > Launch Options. Try these in order:
-dx11codecodecodecodecodecode — Forces DirectX 11 mode. Some systems crash in DX12 at the menu.-windowed -nobordercodecodecodecodecodecode — Prevents fullscreen mode from initializing incorrectly.-nohithreadcodecodecodecodecodecode — Disables high-priority CPU threads that can cause instability on older processors.
Test each one separately. If the game launches in DX11, keep it. The visual difference is negligible for the menu.
Check for Anti-Cheat Service Interference
The game uses Easy Anti-Cheat (most likely—verify in the game folder). Open Services (services.msc), look for “EasyAntiCheat,” and ensure it is running. If it is stuck, right-click and restart. You can also run the EasyAntiCheat setup executable in the game’s installation folder and select “Repair Service.”
A blocked anti-cheat service will prevent the main menu from connecting to the backend. The game does not display an error—it just crashes.
Reinstall Audio Drivers
This is the deepest non-obvious fix. The game’s audio engine (likely Wwise) initializes during the menu. A problematic audio driver—especially Realtek or Nvidia High Definition Audio—can cause a silent crash. Use Device Manager to uninstall the audio driver, then restart Windows. Let it reinstall automatically. Alternatively, download the manufacturer’s latest driver directly.
Many users find this resolves a main menu crash that no other fix touched.
FAQ
Q: Why does Star Wars Zero Company crash only at the main menu and not in-game?
The main menu is where shader compilation and online authentication happen. In-game, those tasks are already done. If one of those two sets fails, you never get past the menu.
Q: Do I need to reinstall the entire game to fix the main menu crash?
Rarely. Reinstalling is a last resort only if the game files are corrupted beyond what a verification fixes. Try the shader cache clear and launch options first.
Q: Can a third-party antivirus cause the main menu crash?
Yes. Antivirus software that monitors game processes can block the anti-cheat or the shader compiler. Temporarily disable real-time protection or add the game folder to the exclusion list.
Q: Should I lower graphics settings before launching?
You cannot change graphics settings from the menu if it crashes. You can edit the configuration file manually (usually in Documents/Star Wars Zero Company), but lowering settings rarely helps the main menu crash. It is not a performance issue.
Q: Does the crash happen on both Steam and other storefronts?
The source material focuses on Steam, but the same fixes apply to other versions. The shader cache and runtime dependencies are system-level.
Closing Thought
One scenario where none of these fixes work: a system with a CPU that lacks support for certain instruction sets (AVX or AVX2). Star Wars Zero Company may require AVX for its shader compilation, and older processors like some Intel 4th-gen or AMD FX series will hang. There is no workaround—the engine simply cannot run. That is not a crash you can fix with software. It is a hardware boundary. Check your CPU’s instruction set compatibility before spending hours on troubleshooting.
