Guide

Troubleshooting

Close the game before editing its files, back up the file you are changing, and record the original setting. Start with the specific fix below rather than deleting the installation or resetting all your preferences.

The launcher will not open

A .NET or Windows Desktop Runtime prompt appears

  1. Confirm that you obtained launcher.exe from the project release page, then open it normally, not as administrator.
  2. If the error requests .NET 6.0, install Microsoft's Windows .NET Desktop Runtime 6.0.36, x64. Choose the Desktop Runtime, not the SDK or ASP.NET runtime.
  3. Finish the installer, then reopen the launcher. If the prompt remains, include the requested framework, version, and architecture in a support report, along with the runtime you installed.

The launcher requires .NET 6; installing a newer major version does not replace it.

The error names TorrentLib

  1. Copy the complete error, including any named library.
  2. Install or repair the Microsoft Visual C++ x64 Redistributable, then reopen the launcher. This is a separate dependency from .NET.
  3. If the error remains, include it in a support report. Check your security software's protection history for a blocked file; do not download replacement DLLs from third-party DLL sites.

Windows or antivirus blocks the executable

For a SmartScreen “Windows protected your PC” warning about an unrecognized app, check that you downloaded launcher.exe from the project release page. The launcher is unsigned; if the file came from that release, use More info → Run anyway to continue. This allows that launch without turning off antivirus protection.

If antivirus reports a specific malware detection, check the detection name and file path in protection history. Share those details and the download link with Support so the file can be investigated. Keep antivirus protection enabled; you do not need a blanket exclusion for the game folder.

The launcher cannot find a release or update

The launcher uses BitTorrent's distributed hash table (DHT) to discover releases before downloading the game. A failed lookup can come from network filtering, unavailable responses, a timeout, or a launcher error.

  1. For an existing installation, close the game and open the launcher in that installation, not a spare copy elsewhere. Check the current launcher release; if replacing an older launcher, close it first and preserve the old executable outside the installation as a backup.
  2. Use Settings → Updates to check again. For a new install still in the wizard, retry after checking the points below; there is no need to erase downloaded files.
  3. Check your Internet connection and the community server-status channel. Web access and DHT discovery use different traffic, so a working website does not rule out a network issue.
  4. Check whether a firewall rule blocks the launcher's current path. Allow the application on the intended network profile if needed. On a school or work network, ask the administrator whether the traffic is permitted.
  5. Try another connection, such as a mobile hotspot, to help identify a network problem. Keep mobile-data charges in mind.

If discovery still fails, report a release lookup failure with the launcher log and time of the attempt. Note that no game download started.

A game download stalls, or an update is interrupted

  1. Check the stage shown by the launcher. It may be checking or writing files rather than downloading, so low network activity can be normal.
  2. Check available disk space on the installation drive and ensure your normal account can write to the selected folder. Keep the game closed while updating.
  3. If the launcher stopped, reopen it from the same installation location so it can resume the unfinished install. Keep the partial installation. If it offers a new destination instead, check that you opened the correct launcher before continuing.
  4. If the launcher opens but the installed game seems incomplete, first back up personal content and any intentionally modified files. Open Settings → Files → Verify Files. Review the result before accepting Repair now?; repairing can replace files you deliberately changed and requires release discovery and downloads to work.

File verification repairs the base game, not community mods or graphics wrappers. If the download has no available peers or progress never resumes, report the stage and any error through Support.

Play closes immediately, or the game crashes

  1. Distinguish the launcher from eldorado.exe, the game. Record which window opens, which closes, and whether an error or crash reporter appears.
  2. If the problem began after adding a wrapper, menu replacement, or mod, undo that one change using its backup. Do not remove unrelated DLLs or copy files from an old 0.6 installation.
  3. Check the installed version and, after preserving customizations, use the file-verification procedure above if base-game files may be missing. Do not fetch a missing game DLL from an arbitrary website.
  4. If the game reaches its menus, compare an unmodded local game with the failing map or server. A failure confined to one mod or map belongs with that content's author or server host; a failure before every menu belongs in a general support report.

For compatibility layers, include the exact Wine/Proton/GPTK or other tool version and whether the game and launcher use the same prefix. Use the platform-specific Linux or macOS procedure rather than installing Windows dependencies into an unrelated prefix.

Menus are blank, stuck, or unresponsive

Try disabling GPU acceleration for the CEF web interface. This targets blank or unresponsive menus, not general game performance.

  1. Close the game. In your ElDewrito installation, back up data\dewrito_prefs.cfg if it exists.
  2. Open dewrito_prefs.cfg in a plain-text editor, or start a new file if it does not exist. Find Game.CEFGpuEnable and change its value to 0. If the setting is absent, add the line below. Keep only one active entry for this setting and leave everything else unchanged.
Game.CEFGpuEnable 0
  1. Save the file and restart the game. If the file did not exist, create it at that path. Ensure the filename is dewrito_prefs.cfg, not dewrito_prefs.cfg.txt.
  2. Try the same menu. If it does not help, close the game and restore your backup, or remove only the entry you added. If you created the file and the game has since added other preferences, retain those rather than deleting the whole file.

If you can still use the menus, change CEF Gpu Acceleration under Advanced CEF Options in settings instead, then restart the game. Do not edit the configuration file while the game is running, as saving settings can overwrite your edit. If the problem began after installing a custom menu, restore that menu's working backup first.

The world is extremely bright or bloom is excessive

  1. Open settings with Home and go to the video settings. Note the current state of CPU Exposure (Bloom Patch).
  2. Enable that option and apply the change. Compare the same map and scene; do not simultaneously change gamma, contrast, and your GPU driver.
  3. If the result is worse or unchanged, restore the original option and apply it. Report your GPU, driver, map, and whether this affects unmodded maps too.

The bloom patch is built into the game; there is no separate patch executable to download.

Performance remains poor: optional Windows DXVK workaround

The optional ElDewrito DXVK 2.1 package, release 0525 replaces the game's Direct3D 9 rendering with Vulkan. It may help with some rendering or menu problems, but results depend on your GPU and driver.

  1. Check that your GPU and installed driver support Vulkan 1.3, required by this DXVK generation. Use the GPU vendor's support information for your device. Follow this recipe with the linked ElDewrito package, not a newer upstream DXVK release with different requirements.
  2. Close the game. Check whether d3d9.dll, dxvk.conf, or eldorado.dxvk-cache already exists beside eldorado.exe. Back up any such files separately. If another graphics wrapper owns d3d9.dll, do not stack or overwrite wrappers without understanding its removal procedure.
  3. Download ElDewrito.DXVK.zip from the linked release. Extract d3d9.dll, dxvk.conf, and eldorado.dxvk-cache beside eldorado.exe, not into Windows system directories.
  4. Try a known map. Shader compilation can increase first-load time and cause stutter, so compare a later launch of the same map before deciding whether performance has improved.
  5. If the game crashes, looks wrong, or does not improve, close it. Remove only the three files added by this procedure and restore any originals you backed up. Retest without the wrapper.

This procedure is for the community Windows package. Proton and other compatibility tools may already manage DXVK; use their platform instructions rather than combining this with a second renderer setup.

The server browser is empty, or servers cannot be joined

  1. Clear browser filters and refresh. Check the web server list to see which servers are online.
  2. Try another server and record whether the failure affects one server or several. If another works, check the original server's status, required game version, password, and capacity with its host.
  3. If several fail, check whether local play works and whether eldorado.exe at the actual installation path is blocked by your firewall. A rule for the launcher is not a rule for the game, and a rule for an old folder may no longer match.
  4. Allow the game's executable through Windows Firewall on the network profile you use. You can leave the firewall enabled, and you do not need router port forwarding to join a game. On a managed network, ask the administrator to allow the connection.

Browser listings, game connections, launcher downloads and mod downloads use different services. When asking for help, say which part is failing and whether trying another network changed the result.

Joining stops at a mod download

Servers can request automatic mod downloads. Note the server, package name/version, and exact download message before changing anything.

  • Not enough disk space: free up space on the installation drive, then retry the download.
  • Error writing to file: check that your normal account can write to the game folder, that the drive has free space, and that security software has not blocked the file. Run the game normally, not as administrator.
  • Server returned bad response / Server request error: retry once, then tell the host which package failed. The host may need to fix the download link or server configuration.
  • Network error: check your connection and try another server to see whether the problem is specific to that download.
  • Download cancelled: rejoin or retry when you are ready.

Allow the Preparing files stage to finish after the transfer completes. If retrying does not help, give the server host the package version and error. See Custom content for installing and managing packages.

Friends cannot reach a game you host

If you can join other servers but friends cannot reach yours, follow Hosting to configure the host's firewall and router. Only the game's player-facing ports need to be reachable; keep remote administration private.

Ask for help with a useful report

Post in the Discord community, or ask r/HaloOnline. Include enough detail to separate a local issue from a service or content problem:

Symptom and exact error:
Game version / launcher version:
Windows version, or OS + compatibility tool/version + prefix arrangement:
GPU and driver version:
Steps that trigger the problem:
Expected result / actual result:
Does local unmodded play work?
One map/server/package or several? Which ones?
What changed immediately before it started?
Fixes tried individually, their results, and what was rolled back:
Time of failure and relevant redacted log excerpt or screenshot:

Find the launcher log at %LOCALAPPDATA%\ElDewrito\logs\launcher.log in File Explorer. Game logs are in the installation's logs directory; look for dorito.log and, for menu problems, custom_menu.log. Include the relevant excerpt if the file exists. A launcher that fails before initialization may not create a log.

Before posting, remove passwords, tokens, personal paths, IP addresses you do not intend to share, and player identity details. Share the relevant log excerpt rather than uploading entire logs or configuration files.