This page collects fixes for the issues users most frequently encounter. Each section describes the symptom, explains the likely cause, and walks through the resolution steps. If your issue is not listed here, check the Eden logs first — they often point directly to the root cause.Documentation Index
Fetch the complete documentation index at: https://mintlify.com/eden-emulator/mirror/llms.txt
Use this file to discover all available pages before exploring further.
How to Access Logs
Before diagnosing any issue, locate your Eden log files. Logs are required when reporting bugs to the Eden team.- Windows
- Steam Deck
- Android
By default, Eden stores logs at:For portable installations, logs are in the
log subfolder of your Eden installation directory.A visual guide with screenshots is available at the Notion log access guide.
Common Issues
Vulkan initialization error
Vulkan initialization error
Eden fails to start or shows a Vulkan initialization error on launch.Fixes to try in order:
- Update your GPU drivers to the latest version available from your GPU vendor.
- On Windows: Use Display Driver Uninstaller (DDU) to fully remove old driver remnants before reinstalling the latest driver. DDU removes registry entries and leftover files that a standard uninstall misses.
- Change the graphics backend manually by editing the Eden settings file. Toggle the backend value between
0and1. - Disconnect any secondary monitors and try launching again. Some multi-monitor configurations confuse the Vulkan device enumeration.
"This mod only works on an Emulator" error
"This mod only works on an Emulator" error
Some mods include a check that requires the RNG seed to be set to a specific value. If the mod shows this message, the fix is straightforward:
- Open Emulation → Configure → System (or equivalent settings location).
- Enable the RNG seed option.
- Set the RNG seed value to 0.
- Restart the game.
Eden fails to launch and leaves no logs (Windows)
Eden fails to launch and leaves no logs (Windows)
Symptom: Eden appears to do nothing when launched, exits immediately, and no log files are created in the log directory.Platform: Windows only.This issue has two common causes. Work through them in order.Cause 1: Missing Visual C++ RedistributableEden requires the Microsoft Visual C++ Redistributable to run. Without it, the process terminates before any logs can be written.Cause 2: Corrupted Windows system filesCorruption in core Windows system files (particularly
A visual version of this guide with screenshots is available at the Notion launch failure guide.
Download the redistributable
Download the Latest Visual C++ Redistributable for your machine architecture (usually x64).
ntdll.dll) can cause Eden to crash before writing any logs. This is rare — you would likely see other programs misbehaving as well.The telltale sign is an entry in Windows Event Viewer resembling:Check Event Viewer
Open Event Viewer (
Start → eventvwr.msc), expand Windows Logs, and select Application. Look for an Error entry matching the pattern above, timestamped near your last Eden launch attempt.Run DISM as Administrator
Open a Command Prompt as Administrator and run the following command. It will take several minutes — let it finish completely.
Windows Device Loss (fullscreen / GPU reset)
Windows Device Loss (fullscreen / GPU reset)
On Windows 10 and 11, Eden may trigger a GPU device loss when running in fullscreen or maximized-windowed mode. This is caused by a Windows DWM interaction that can be disabled via a registry entry.Run the following batch script from inside the Eden folder (the directory containing This script writes a compatibility flag to the registry that disables the maximized-windowed DX mode and marks Eden as DPI-aware, preventing the GPU reset condition.
eden.exe). Save it as a .bat file and run it as Administrator, or paste it directly into an elevated Command Prompt.Poor performance or bugs on Wayland (Linux)
Poor performance or bugs on Wayland (Linux)
Eden running under a Wayland compositor typically shows significantly worse performance than under X11, alongside random rendering errors and compatibility issues.Fix: Force Eden to use the X11 (XCB) Qt platform plugin instead of Wayland.Set the environment variable before launching:Or pass it as a launch argument:You can make this permanent by adding the export to your shell profile or creating a wrapper script.