Wanderburg Crashing After Update? Startup, Run & Loading Fixes
Troubleshoot Wanderburg startup crashes, run crashes and loading problems with clearly labelled official and community evidence.
Current status
After the 0.9.x launch-window hotfixes, community reports describe three different failure patterns: the game closing during startup, a crash when starting a run, and an infinite loading state when entering a map. The official 0.9.7 Hotfix announcement confirms changes to missing Steam-initialization exception handling, startup Loadout localization and Graphics API priority intended to improve performance and reduce crashes. It does not state that every startup, run or loading failure has one confirmed fix.
Evidence labels: Official means the developer or Steam listing states it directly. Community report means a player described the symptom. Not confirmed means no reproducible fix is established in the available sources.
Quick answer
If Wanderburg quits after the logos, crashes when starting a run after a 0.9.x update, or stays loading when entering a map, update the game first, verify files once, update your graphics driver, disable overlays for one test, and record the exact stage. These are diagnostic steps, not guaranteed fixes.
Latest patch status
The safest first check is whether Steam has installed the latest Early Access hotfix. The 0.9.7 note is official evidence for startup and graphics-priority work; later 0.9.x notes should be checked on updates and patch notes before assuming an older crash report still applies.
Fixed in latest patch
Official hotfix notes confirm some startup-adjacent work, including missing Steam-initialization exception handling, Loadout localization on startup and Graphics API priority changes in 0.9.7. Those items are patch fixes or improvements, not proof that every startup crash, run crash or loading hang has the same cause.
Still reported problems
Treat logo exits, run-start crashes, infinite loading and whole-PC restarts as separate problems. If the same symptom continues after the latest hotfix is installed, include the game version, hardware, Windows version and exact stage in a report instead of repeating reinstall attempts.
Symptom routing
| Symptom | Evidence level | First check |
|---|---|---|
| Closes after the publisher logos | Community report; 0.9.7 has related official startup changes | Verify files and record the last visible screen |
| Crashes when starting a run | Community report | Reproduce once with overlays disabled |
| Infinite loading when entering a map | Community report | Note whether it follows a fresh launch or a resumed run |
| Whole PC restarts | Community report | Stop repeated attempts and check Windows stability |
The official Steam description confirms Windows requirements and the game’s PC target. It does not confirm a specific setting that fixes every crash.
Check the official requirements
Steam lists the minimum PC requirements as a 64-bit processor and operating system, Windows 10 or higher, Intel Core i5 10th Generation, 4 GB RAM, Nvidia GeForce GTX 1660 Ti, DirectX 11 and 2 GB available storage.
Before changing files, confirm:
- Windows is updated and is Windows 10 or higher.
- Your GPU is at least in the range of the listed GTX 1660 Ti requirement.
- DirectX 11 support is available.
- You have more than 2 GB free storage after installation.
- Steam installed the game or demo from the official app page.
Logo exit versus full PC restart
The main reported pattern is the game showing logos and then closing. One player also reported the PC restarting after the logo intro on one machine while an older PC ran the demo. Those are different failure levels.
| Symptom | Next step |
|---|---|
| Game closes after logos | Verify files, restart Steam, record the last visible logo or error mark |
| Window never opens | Check graphics driver and DirectX support before reinstalling |
| PC restarts | Treat it as a system stability issue and check Windows Event Viewer, temperatures and drivers |
| Game keeps running after quit | Close through Steam and include that detail in the bug report |
Safe troubleshooting order
- Restart Steam and launch again once.
- Use Steam's file verification for the demo or Early Access app.
- Update graphics drivers from the GPU vendor.
- Disable overlays for one test run if the crash happens before the game window opens.
- Reboot Windows after driver or Steam changes.
- If the whole PC restarts, stop repeated launch attempts until you check system logs and thermals.
What to send in a report
Include your CPU, GPU, RAM, Windows version, input device, whether you used the demo or Early Access build, and the exact stage where it exits. If you saw a short exclamation mark or Unity dialog, mention it. The useful next step is a reproducible report; the available community thread does not prove a single setting fixes every startup case.
Related: if the game starts but the castle stops moving, use the controls and movement guide. If you are checking whether your system can install the game at all, use the release guide.