Star Wars Zero Company Stuck on Loading Screen – The Non-Obvious Fixes

That infinite loading spinner. You launch Star Wars Zero Company, the screen goes black, the little icon spins, and nothing happens for five, ten, fifteen minutes. You’ve already verified files, updated drivers, and run as administrator. Still stuck.

The issue is almost never a corrupt game file. It’s almost always a shader compilation stall, a background overlay intercepting the rendering pipeline, or a system memory bottleneck that Unreal Engine 5 refuses to tolerate. This guide skips the obvious checklist and goes straight to the fixes that actually break the impasse.

Why the Loading Screen Hangs – Beyond the Basics

Loading screens in Unreal Engine 5 titles like Star Wars Zero Company serve two purposes: loading assets into memory and compiling shaders. The compilation step is the troublemaker. When the game tries to build shaders for your specific GPU and driver combination, it can deadlock if the shader cache is corrupted, your page file is too small, or a background application hooks into the D3D11 or D3D12 runtime.

The default advice—verify game files, update drivers, restart PC—addresses symptoms, not root causes. A corrupted shader cache won’t be fixed by file verification. Driver updates can actually introduce new shader compilation triggers. We need to target the pipeline directly.

Nuke the Shader Cache (The Real First Step)

Forget verifying files. The single most effective fix for a stuck loading screen is wiping the DirectX shader cache and forcing a fresh compile.

1. Open Disk Cleanup (type “disk cleanup” in Start, select your OS drive).
2. Click Clean up system files.
3. Check DirectX Shader Cache (and nothing else unless you know what you’re doing).
4. Confirm and restart.

But Windows Disk Cleanup doesn’t always catch every cache file. For a deeper purge, navigate manually to:

%LOCALAPPDATA%\Star Wars Zero Company\Saved\codecodecodecodecodecode

Look for a folder named PipelineCachecodecodecodecodecodecode or ShaderCachecodecodecodecodecodecode. Delete its contents. Do not delete the entire Savedcodecodecodecodecodecode folder unless you’ve already backed up your save data.

After clearing, launch the game. The first startup will take longer (up to 10–15 minutes) as the engine rebuilds shaders from scratch. That’s normal. Wait. If it hangs beyond 15 minutes, move to the next step.

Some players have reported that simply switching the renderer via launch options can skip the corrupted cache entirely. Right-click the game in Steam → Properties → General → Launch Options. Add one of these, one at a time:

• -dx11codecodecodecodecodecode (forces DirectX 11)
• -dx12codecodecodecodecodecode (forces DirectX 12)
• -vulkancodecodecodecodecodecode (if the engine supports it; check patch notes)

Each flag forces a different shader compilation path. If your cache was built under DX12 and is corrupted, launching in DX11 bypasses it.

Kill Overlays That Hook the Rendering Pipeline

Steam overlay is the obvious culprit, but the real problem is often RivaTuner Statistics Server (RTSS), MSI Afterburner, Nvidia Broadcast, or Overwolf. These tools hook into the DirectX runtime to display framerates or apply filters. That hooking can intercept shader initialization and cause a deadlock.

Disable all overlays at the source:

• Steam: Settings → In-Game → uncheck “Enable the Steam Overlay while in-game.”
• Discord: User Settings → Game Overlay → toggle off.
• Nvidia App (GeForce Experience or the new Nvidia app): disable in-game overlay.
• MSI Afterburner/RTSS: close them entirely. Do not just minimize.

The loading screen should now pass. If it does, re-enable overlays one by one to identify the aggressor.

Network Timeout – The Hidden Culprit

Star Wars Zero Company may check for DRM or online authentication during the loading screen. If your firewall or security software blocks that connection, the game hangs indefinitely.

Add the game executable to your firewall’s whitelist. For Windows Defender Firewall:

1. Open Windows Security → Firewall & network protection.
2. Click Allow an app through firewall.
3. Click Change settings, then Allow another app.
4. Browse to the game’s .execodecodecodecodecodecode file (usually in steamapps\common\Star Wars Zero Companycodecodecodecodecodecode).
5. Ensure both Private and Public boxes are checked.

Alternatively, launch Steam in Offline Mode and try again. If the loading screen passes offline, the issue is a network timeout, not a shader problem.

Save File Corruption or Profile Conflict

A corrupt save file or profile configuration can cause the engine to hang while trying to load your player settings. The game may initialize the UI, then die trying to apply your graphics or control prefs.

Locate the save folder:

%USERPROFILE%\Documents\My Games\Star Wars Zero Company\codecodecodecodecodecode

Rename the entire folder to something like _oldcodecodecodecodecodecode. This forces the game to create a fresh set of default profiles. Launch the game. If it loads, you know the corruption is in your local profile. You can then copy your actual save files (usually in a SaveGamescodecodecodecodecodecode subfolder) back into the new folder.

Disable Steam Cloud saves beforehand to prevent the corrupt data from syncing back:

Steam → Right-click game → Properties → General → uncheck “Keep games saves in the Steam Cloud.”

Graphics Driver – Not Just Latest, But Clean Install

“Update your GPU driver” is the laziest advice. A stuck loading screen can be caused by a recent driver that conflicts with the game’s shader compiler. The fix is a clean reinstall using Display Driver Uninstaller (DDU), followed by installing either the latest driver or an older known-stable version (one from two or three months prior).

DDU removes every leftover registry key, INF file, and driver component that a normal uninstall leaves behind. Those leftovers can corrupt shader compilation.

Boot into Safe Mode, run DDU, then install the driver of your choice. For Nvidia, the Game Ready driver from October 2024 (version 566.14) has shown better stability for this title than the latest hotfix. For AMD, the Adrenalin 24.9.1 release is a safe bet.

Edge Case: Page File Size and Virtual Memory

Low virtual memory is a common but overlooked cause of Unreal Engine loading screen hangs. The engine pre-allocates a large contiguous block of virtual address space during load. If the paging file is too small or is set to a system-managed size on a nearly full drive, the allocation fails silently.

Set the page file manually:

1. Search for Advanced system settings → Performance Settings → Advanced → Virtual Memory → Change.
2. Uncheck “Automatically manage paging file size for all drives.”
3. Select your fastest SSD (preferably the one where the game is installed).
4. Choose Custom size and set Initial size and Maximum size to 1.5 times your physical RAM (e.g., 24576 MB for 16 GB RAM).
5. Click Set, then OK, and restart.

This is a permanent change that also helps with general system stability.

What If Nothing Works? The Nuclear Option

If you’ve cleared shader cache, killed overlays, bypassed network checks, refreshed profiles, clean-installed drivers, and increased page file, the problem is likely a deeper engine incompatibility. Consider these advanced steps:

• Switch to DXVK: This wrapper converts DirectX calls to Vulkan, bypassing the Windows D3D runtime entirely. It can resolve shader compilation bugs in some UE5 titles. Extract the DXVK DLLs into the game’s executable folder and launch again.
• Disable CPU-specific optimizations: Some users with AMD Ryzen systems have solved loading screen hangs by disabling SMT (Simultaneous Multithreading) in BIOS. Disable it temporarily (reboot required) and test.
• Run the game on a different storage device: Moving from an HDD to an NVMe SSD can reduce load times so drastically that the game bypasses a timing-related hang.

These are not standard troubleshooting steps. They are last-resort interventions for a game that shouldn’t require them. Use them only after exhausting everything above.

FAQ

There is no single fix that works for every copy of Star Wars Zero Company. The shader cache purge is the highest-probability first step, but when that fails, the culprit is almost always an application hooking into the rendering pipeline or a system memory constraint that no amount of driver updates will solve. These are the invisible dependencies that the standard troubleshooting checklists ignore. You now have the map to navigate around them.