Windrose Fatal Error — 'UE-R5 Game Has Crashed and Will Close'
Windrose entered Early Access on 14 April 2026 and its most-reported crash is the Unreal Engine 'UE-R5 Game has crashed and will close' fatal error, which pops up randomly during menu navigation and gameplay rather than at a fixed spot. Because it's an Early-Access UE build, most cases are driver, runtime or cache related. Here's what it means and the fastest fixes.
Error codes
'UE-R5 Game has crashed and will close' (random fatal error)
Unreal Engine hit a fatal error during menu or gameplay
Cause: Outdated/corrupt GPU driver, missing runtimes, or a corrupted shader cache in the Early-Access build.
- Clean-install the latest GPU driver with DDU — the top fix for random UE fatal errors.
- Install the latest Visual C++ Redistributables (x86 + x64) and the DirectX End-User Runtime.
- Verify game files in Steam and delete the local shader cache so it rebuilds cleanly.
Crash when opening a menu / loading a save
The fatal error triggers on a specific UI or load action
Cause: Early-Access build instability plus overlays/config bloat.
- Disable all overlays (Steam, Discord, GeForce Experience) which frequently trip UE menu crashes.
- Delete the game's config/SaveGames cache folder in %LOCALAPPDATA% (back it up first) to clear a corrupted setting.
- Report the reproducible step to the developers — in Early Access, a build patch is often the real fix.
Crash on startup / won't reach main menu
The game closes before you can play
Cause: Missing runtimes, antivirus block, or overclock instability.
- Turn off CPU/GPU overclocks (XMP/EXPO included) and run at stock while testing.
- Add the game to antivirus exceptions and run it as administrator.
- Reinstall if the executable itself is flagged as corrupt.
Fixes that work for most Windrose (PC / Steam Early Access) errors
- Verify/repair the game files (Steam: Properties -> Installed Files -> Verify integrity) — this replaces corrupted files behind most UE5 fatal errors.
- Clean-install the latest GPU driver with DDU, and install the latest Microsoft Visual C++ Redistributables (x86 and x64) plus the DirectX End-User Runtime — stale drivers and missing runtimes cause most UE5 launch crashes.
- Clear the DirectX Shader Cache (Disk Cleanup) and delete the game's local shader/cache folder in %LOCALAPPDATA%, then relaunch so it rebuilds.
- Disable overlays (Steam, Discord, GeForce Experience) and any third-party antivirus/VPN, and run the game as administrator.
FAQ
What is the 'R5' in the Windrose crash message?
It's the Unreal project code the developers gave Windrose, so the engine reports fatal errors as 'UE-R5 Game has crashed'. It doesn't indicate the cause — treat it as a generic UE5 fatal error.
Will these fixes survive Early Access patches?
The driver/runtime/cache fixes are permanent, but some crashes are build bugs the developers must patch. Keep the game updated and re-verify files after each Early-Access patch.
Other games
- Counter-Strike 2 Errors — VAC Unable to Verify, Matchmaking Failed & Fixes
- Dota 2 Errors — Searching for Game Coordinator, Disconnected & Fixes
- Elder Scrolls Online Error Codes — 301, 307, 210, 200 & Connection Fixes
- Fallout 76 Error Codes — 3:0:7, 4:7:0, 4:7:1, 4:8:2009 & Fixes
- Lost Ark Error Codes — 10010, 10027, G0x9-SPELPWP1P2NT & Connection Fixes
- Once Human Errors — Login Failed, Error 3, Error 101 & Network Fixes
- The Division 2 Error Codes — Delta, Mike, Bravo, Delta-03, Mike-01 & Fixes
- Zenless Zone Zero Errors — Invalid Network Request, Cannot Connect to Server & Fixes