Skip to main content

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.

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.

How to Access Logs

Before diagnosing any issue, locate your Eden log files. Logs are required when reporting bugs to the Eden team.
By default, Eden stores logs at:
C:\Users\<USER>\AppData\Roaming\Eden\log
For portable installations, logs are in the log subfolder of your Eden installation directory.
1

Open Eden

Launch Eden normally.
2

Open the log folder

Navigate to File → Open Eden Folder → Log Folder. A Windows Explorer window will open directly to the log directory.
3

Review or upload your logs

Your log files are now available for review or upload to a bug report.
A visual guide with screenshots is available at the Notion log access guide.

Common Issues

Eden fails to start or shows a Vulkan initialization error on launch.Fixes to try in order:
  1. Update your GPU drivers to the latest version available from your GPU vendor.
  2. 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.
  3. Change the graphics backend manually by editing the Eden settings file. Toggle the backend value between 0 and 1.
  4. Disconnect any secondary monitors and try launching again. Some multi-monitor configurations confuse the Vulkan device enumeration.
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:
  1. Open Emulation → Configure → System (or equivalent settings location).
  2. Enable the RNG seed option.
  3. Set the RNG seed value to 0.
  4. Restart the game.
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.
A visual version of this guide with screenshots is available at the Notion launch failure guide.
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.
1

Download the redistributable

Download the Latest Visual C++ Redistributable for your machine architecture (usually x64).
2

Install it

Double-click the downloaded executable and wait for installation to complete.
3

Restart

Reboot your computer.
4

Test Eden

Launch Eden again. If the main window appears, the issue is resolved. If not, continue to Cause 2.
Cause 2: Corrupted Windows system filesCorruption in core Windows system files (particularly 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:
Faulting application name: eden.exe
Faulting module name: ntdll.dll
Exception code: 0xc0000005
1

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.
2

Run DISM as Administrator

Open a Command Prompt as Administrator and run the following command. It will take several minutes — let it finish completely.
DISM /Online /Cleanup-Image /RestoreHealth
3

Reboot

Restart your computer after DISM completes.
4

Test Eden

Launch Eden and verify it now starts correctly.
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 eden.exe). Save it as a .bat file and run it as Administrator, or paste it directly into an elevated Command Prompt.
@echo off
pushd "%~dp0"
if exist "%temp%\FixFullScreen.reg" (
  del %temp%\FixFullScreen.reg
)
set str_path="%cd:\=\\%\\eden.exe"
echo Windows Registry Editor Version 5.00 >> %temp%\FixFullScreen.reg
echo. >> %temp%\FixFullScreen.reg
echo [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\AppCompatFlags\Layers] >> %temp%\FixFullScreen.reg
echo %str_path%="~ DISABLEDXMAXIMIZEDWINDOWEDMODE HIGHDPIAWARE" >> %temp%\FixFullScreen.reg
regedit /s %temp%\FixFullScreen.reg
del %temp%\FixFullScreen.reg
exit /b
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 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:
QT_QPA_PLATFORM=xcb eden
Or pass it as a launch argument:
eden -platform xcb
You can make this permanent by adding the export to your shell profile or creating a wrapper script.

Build docs developers (and LLMs) love