Introduction
One of the most frustrating experiences for Dwarf Fortress players is launching Dwarf Therapist only to find it refuses to detect a running game session. The dwarf roster stays blank, the connection status shows nothing, and no matter how many times you relaunch the tool, the result is the same. This problem is more common than it should be, and in nearly every case it comes down to one of a small number of identifiable causes.
Dwarf Therapist does not browse your file system to find a Dwarf Fortress installation. It locates the game by scanning memory for a running process that matches its internal expectations for a specific game version.
If that process is not running, is running under a different permission level, or does not match the version the tool was built for, detection fails silently with no helpful error message.
Understanding exactly how the detection mechanism works makes every troubleshooting step in this guide logical rather than guesswork. This article covers the full range of causes and solutions, from the most common to the less obvious, and applies to both the classic free version and the Steam Premium release of Dwarf Fortress.
All guidance is based on community-verified procedures and is intended for informational use.
Quick Answer about Dwarf Therapist
- Dwarf Therapist detects the game via memory process scanning, not file system browsing
- The most common cause of detection failure is a version mismatch between the tool and the game
- Launching Dwarf Therapist before Dwarf Fortress is fully loaded into an active session always causes detection failure
- Administrator privileges are frequently required, especially when the game runs through Steam
- Antivirus software can block the memory-reading process silently without displaying a visible error
- Running both applications as Administrator resolves a large proportion of permission-related detection failures
- The game must be in an active fortress session, not on the main menu or any loading screen
- Firewall and security software can interfere with inter-process memory access even on a local machine
- A blank dwarf roster is not always a detection failure it can also indicate a successful connection to a session with no dwarves present yet
- Reinstalling Dwarf Therapist to a different folder location resolves detection issues caused by path or permission conflicts in certain Windows environments.
What Causes Dwarf Therapist to Fail at Detecting the Game
How the Detection Process Actually Works
Dwarf Therapist does not use a configuration file that points to a specific Dwarf Fortress folder path. When you launch the tool, it enumerates running processes on your system and looks for one that matches the expected executable name and memory signature for the version it was built to support.
If the process is found and accessible, the tool reads the memory addresses it expects to find dwarf data at and populates the roster grid. If the process is not found, is inaccessible due to permission restrictions, or has a memory layout that does not match the expected offsets, detection either fails outright or connects to wrong addresses and displays nothing useful.
This design means that several entirely different root causes can produce identical symptoms. A version mismatch, a permission issue, an antivirus block, and an incorrect launch sequence all result in the same blank roster and a “no connection” message. Isolating the actual cause requires working through each possibility methodically rather than applying a single fix and assuming it will work.
Version Mismatch as the Primary Cause
Version mismatch between Dwarf Therapist and your installed Dwarf Fortress is statistically the most common cause of detection failure. Each release of Dwarf Therapist is compiled against specific memory offsets from a particular game version. When the game updates and those offsets shift, the tool can no longer locate dwarf data at the addresses it is looking for.
The symptom of a version mismatch is sometimes a completely blank roster and sometimes a roster that appears to populate but shows scrambled names, incorrect skill values, or labor states set to zero. Both outcomes indicate that the tool found a running process but could not read meaningful data from the expected memory locations.
Confirming your Dwarf Fortress version is the first diagnostic step when a detection failure occurs. In the classic free version the build number appears on the main menu screen. In the Steam Premium release it is visible in the game properties within the Steam library under the installed files information.
How to Diagnose the Detection Failure Step by Step
Checking Version Compatibility First
Before adjusting any system settings or reinstalling anything, confirm that your Dwarf Therapist release matches your current Dwarf Fortress version. Open the GitHub releases page for Dwarf Therapist and compare the compatibility notes on your installed release against your game version number.
If a mismatch exists, the only resolution is downloading the correct matching release. No amount of permission adjustment, antivirus configuration, or folder relocation will fix a detection failure caused by incompatible versions.
This step eliminates the most common cause immediately and prevents wasted troubleshooting effort on system-level settings that are not actually the problem.
Steps to check version compatibility:
- Note your exact Dwarf Fortress version number from the main menu or Steam properties
- Visit the Dwarf Therapist GitHub releases page
- Find your currently installed Dwarf Therapist version in the releases list
- Read its compatibility notes to confirm it lists your game version as supported
- If it does not, download the release that does and test again before continuing with any other steps
Verifying the Launch Sequence and Game State
If version compatibility is confirmed and detection still fails, the next most common cause is an incorrect launch sequence or an invalid game state when Dwarf Therapist attempts to connect.
Dwarf Therapist must be launched after Dwarf Fortress is fully loaded into an active fortress session. The game must be past the main menu, past world generation, past the embark screen, and into a live session where dwarves are present and active.
Launching the tool at any earlier stage means the game process either does not yet expose the memory structures the tool expects or exposes them in an incomplete state.
Common detection problems and practical solutions:
- Blank roster despite game running Confirm the game is in an active fortress session, not on any menu or loading screen; close Dwarf Therapist and relaunch it after the game is fully in play
- Tool launches but shows no connection status Run Dwarf Therapist as Administrator by right-clicking the executable; Steam-managed game processes often require elevated permissions for external memory access
- Detection worked previously but stopped after a game update A Dwarf Fortress update has likely shifted memory offsets; check GitHub for a new compatible Dwarf Therapist release immediately
- Detection fails only when antivirus is active Add the Dwarf Therapist folder as an exclusion in your antivirus or Windows Security settings; memory-reading behavior triggers heuristic blocks in many security tools
- Roster populates but all values are wrong or scrambled This is a version mismatch symptom even if connection appears to succeed; the tool is reading wrong memory addresses
- Detection fails after moving the Dwarf Therapist folder to a new location Some Windows security zones treat files differently based on path; move the folder to a location outside protected directories such as Program Files or OneDrive-synced folders
- Tool detects the game on some launches but not others This inconsistency often points to a timing issue; wait longer after loading your fortress before launching Dwarf Therapist to give the game process time to fully initialize its memory structures
Resolving Permission and Security Conflicts
Administrator Privileges and Windows Security Zones
Windows manages inter-process memory access through permission tiers. When Dwarf Therapist attempts to read the memory of a running Dwarf Fortress process, both applications need to be operating at compatible permission levels.
If the game runs at a higher privilege level than the tool, the tool is denied access, with no visible error message beyond the blank roster.
This situation occurs most frequently when Dwarf Fortress runs through the Steam client, as Steam sometimes elevates its child processes depending on how it was launched. Running Dwarf Therapist as Administrator brings it to a matching privilege level and resolves the access block in most cases.
To set Dwarf Therapist to always run as Administrator without needing to right-click every session, right-click the executable, select properties, navigate to the Compatibility tab, and check the box labeled Run this program as an administrator. This setting persists across launches and eliminates the need to remember the right-click step each session.
Antivirus and Firewall Interference
Antivirus software identifies Dwarf Therapist as potentially suspicious because memory-reading behavior is a technique used by certain categories of malicious software. Most security tools do not distinguish between a legitimate game utility and a harmful application based solely on behavior, so they apply the same block to both.
The block is typically silent. Dwarf Therapist launches normally, shows its interface, but never receives the memory access it needs to populate the roster.
There is no error message and no obvious indication that an antivirus rule is responsible. Resolving this requires adding a specific exclusion for the Dwarf Therapist folder in your security software. For Windows Defender, navigate to Windows Security, select Virus and Threat protection, go to Manage Settings, scroll to Exclusions, and add the folder containing your Dwarf Therapist executable.
Third-party antivirus tools have equivalent exclusion management sections in their settings panels. Players using corporate or managed Windows environments should be aware that group policy settings may prevent adding exclusions without administrator access to the machine.
In these environments, detection failures due to security policy may not be resolved without IT involvement.
Advanced Troubleshooting for Persistent Detection Failures
Reinstallation and Path-Related Issues
If version compatibility is confirmed, launch sequence is correct, administrator privileges are enabled, and antivirus exclusions are in place, and detection still fails, the next step is a clean reinstallation to a different folder path.
Some Windows environments apply implicit security restrictions based on folder location. Folders inside Program Files, within OneDrive-synced directories, or in user profile paths with special permission inheritance can cause inter-process memory access to fail even when the application itself appears to launch normally.
Extract a fresh copy of the correct Dwarf Therapist release into a simple path such as a folder directly on the C drive or in a non-synced documents location.
Avoid any path that contains spaces, special characters, or sits within a cloud-synced folder. Test detection from this new location before making any other changes. Keep your settings files from the previous installation by copying them to the new folder location before first launch.
This preserves your custom roles and labor definitions while giving you a clean application environment for testing.
Confirming the Game Process Is Visible to External Applications
In rare cases, particularly on systems with aggressive security hardening or certain third-party process isolation tools, the Dwarf Fortress process may not be visible to other applications at all.
You can verify this using the Windows Task Manager by opening it while Dwarf Fortress is running and confirming the Dwarf Fortress executable appears in the Processes list. If the process is visible in Task Manager but Dwarf Therapist still cannot detect it, the issue is access permission rather than visibility.
If the process does not appear in Task Manager at all, a system-level isolation setting or security tool is hiding it from external processes, and resolving that requires adjusting the relevant security configuration on your system.
Players running Dwarf Fortress in compatibility mode should disable compatibility mode settings and retest detection, as some compatibility mode flags alter how the process is registered with the Windows process manager, which can affect visibility to external tools.
Frequently Asked Questions
Why does Dwarf Therapist show a blank roster even when Dwarf Fortress is running?
The most common reasons are an incorrect launch sequence, in which the tool was opened before a fortress session was fully loaded; a version mismatch between the two applications; or a permission conflict preventing memory access. Work through each cause in order starting with version compatibility.
Does Dwarf Therapist need to know the installation path of Dwarf Fortress?
No. Dwarf Therapist locates the game by scanning running processes in memory, not by browsing the file system. You do not need to point it to a folder location. If the game is running and accessible at the right permission level, the tool finds it automatically.
Why did detection stop working after a Windows update?
Windows updates can adjust security policies, update Windows Defender definitions, or change how inter-process memory access is handled. After a Windows update, check that your Dwarf Therapist antivirus exclusion is still in place and that the Run as Administrator setting on the executable is still applied.
Can running both Dwarf Fortress and Dwarf Therapist as Administrator cause any problems?
Running both as Administrator is the recommended configuration for most setups and does not introduce known problems. It brings both processes to the same privilege level, which resolves the most common class of memory access permission failures.
Why does Dwarf Therapist detect the game sometimes but not others?
Inconsistent detection usually points to a timing issue where the tool is launched before the game has fully initialized its memory structures. Wait until you are in an active fortress session for at least a few seconds before launching Dwarf Therapist, and the detection rate should become consistent.
Does Dwarf Therapist work if Dwarf Fortress is running in windowed versus fullscreen mode?
Display mode does not affect memory access. Dwarf Therapist reads process memory regardless of whether the game is running in windowed, borderless windowed, or fullscreen mode. Display mode is not a factor in detection failures.
Can a VPN or network security tool cause Dwarf Therapist detection failures?
Most VPNs operate at the network layer and do not affect local inter-process memory access. However, certain endpoint security tools bundled with VPN software do include process isolation features.
If a VPN or its associated security software was installed around the time detection stopped working, temporarily disabling it for a test is a reasonable diagnostic step.
Is there a log file in Dwarf Therapist that shows why detection failed?
Some versions of Dwarf Therapist write basic diagnostic output to a log file within the application folder.
Check for a file named log, output, or debug with a .txt or .log extension in your Dwarf Therapist folder after a failed detection attempt. The content may identify the specific point where the connection process broke down.
Latest Post:
