Introduction
The missing dependencies warning in Dwarf Therapist keeps many players from ever getting the tool working. It appears at launch, blocks the application from running, and often references library names or file paths that mean nothing to someone who just wants to manage their fortress dwarves.
This warning is not a sign that something is permanently broken. It is Dwarf Therapist telling you precisely what it needs that is not currently available on your system. Every missing dependency has a specific fix, and in most cases that fix takes only a few minutes to apply.
This guide explains what the missing dependencies warning means, why it appears, and exactly how to resolve it on Windows, Linux, and macOS.
Each platform has its own dependency chain and resolution path, all of which are covered here in full.
Quick Answer about Dwarf Therapist Warning
- The missing dependencies warning means Dwarf Therapist cannot find one or more runtime libraries it requires to launch and operate correctly
- On Windows the most common missing dependency is the Microsoft Visual C++ Redistributable package or a specific Qt DLL file
- On Linux the warning typically points to absent Qt shared libraries such as libQt5Core or libQt5Widgets that need to be installed via the package manager
- On macOS missing dependencies usually involve a broken Qt framework path inside the application bundle or missing Homebrew-installed libraries
- Missing dependencies do not affect Dwarf Fortress save files and resolving them requires no changes to the game installation
- The exact name of the missing dependency is displayed in the warning message and should be noted before attempting any fix
- Installing the correct runtime package for your platform resolves the majority of missing dependency warnings without requiring a rebuild
- Never attempt to manually copy individual DLL or shared library files from other locations as version mismatches between manually copied files cause further instability
- Building Dwarf Therapist from source eliminates binary dependency issues entirely and is the most reliable resolution on macOS and Linux
- After resolving dependencies, always verify the fix by launching Dwarf Therapist with Dwarf Fortress running before making any labor assignments
What the Missing Dependencies Warning Actually Means
Understanding Runtime Dependencies in Qt Applications
Dwarf Therapist is built using the Qt application framework, which provides the graphical interface, memory management utilities, and cross-platform compatibility layer the tool relies on.
Qt is not bundled inside the Dwarf Therapist executable itself on most platforms. Instead, it exists as a set of separate shared library files that the executable expects to find on the host system at runtime.
When Dwarf Therapist launches, the operating system’s dynamic linker attempts to locate all shared libraries referenced by the executable. If any of these libraries are absent, the wrong version, or installed in a location the linker cannot find, the launch fails and the missing dependencies warning is displayed.
The warning message is generated either by the operating system before the application even starts, or by an early-startup check within Dwarf Therapist itself. On Windows this typically appears as a dialog box listing specific DLL filenames. On Linux it appears as terminal output referencing .so file names. On macOS it may appear as a system dialog or be visible only in crash logs.
Understanding that this is a system-level library resolution problem rather than an application bug is important. The fix lives at the system level, not inside the Dwarf Therapist installation itself.
Reading the Warning Message Correctly
The dependency warning will name the specific file or library that could not be found. This name is the most valuable piece of diagnostic information available and should be recorded accurately before attempting any fix.
On Windows, the message format is typically something like the system cannot find the file Qt5Core.dll or the program cannot start because VCRUNTIME140.dll is missing from your computer. The filename in the message directly identifies the package to install.
On Linux, the terminal message will state that a shared object such as libQt5Core.so.5 is not found or cannot be opened. The library name before the version suffix identifies the Qt module or system library that needs to be installed.
On macOS, missing framework errors may appear in the Console application crash log and reference paths like Qt5Core.framework or a Homebrew-specific path that no longer resolves correctly after a package update.
Write down the exact filename referenced in the warning. Every step that follows depends on correctly identifying what is missing.
How to Fix Missing Dependencies on Windows
Installing the Visual C++ Redistributable and Qt Runtime
The most common missing dependency on Windows is the Microsoft Visual C++ Redistributable. Dwarf Therapist is compiled with MSVC on Windows, and the compiled binary requires the corresponding runtime libraries to be present on the system. These are not included with Windows by default and must be installed separately.
Navigate to the official Microsoft Visual C++ Redistributable download page and download the latest version covering Visual Studio 2015 through 2022.
Install both the x64 and x86 versions even on a 64-bit system. Some Qt components reference 32-bit runtime libraries even in primarily 64-bit applications. After installing the Redistributable, restart your system, then relaunch Dwarf Therapist.
Some runtime library installations do not fully activate until after a system restart, and skipping this step can cause the warning to persist even after a successful installation.
If the warning references a specific Qt DLL such as Qt5Core.dll, Qt5Widgets.dll, or Qt5Gui.dll rather than a Microsoft runtime file, the Dwarf Therapist archive was extracted incompletely. These Qt DLL files should be present in the same folder as the Dwarf Therapist executable when extracted from the official release archive.
Delete the existing Dwarf Therapist folder entirely and re-extract the release archive to a fresh location.
Ensure the extraction process completes without errors and that the destination folder is not inside a system-protected directory such as Program Files, which can cause file permission issues during extraction.
Common Windows missing dependency problems:
- VCRUNTIME140.dll or MSVCP140.dll missing: Install Microsoft Visual C++ 2015 to 2022 Redistributable x64 and x86 from the official Microsoft download page
- Qt5Core.dll missing: Re-extract the full Dwarf Therapist archive to a fresh folder outside Program Files; this file should be included in the archive
- Qt5Widgets.dll or Qt5Gui.dll missing: Same cause as above; full re-extraction to a clean folder resolves this
- ucrtbase.dll missing: Install the Windows Universal C Runtime through Windows Update or from the Microsoft Update Catalog
- Application reports missing dependency but no filename shown: Run Dwarf Therapist from Command Prompt to capture the full error output before the window closes
Using Dependency Walker to Identify Hidden Missing Files
If the warning message is vague or a second missing dependency appears after resolving the first, a dependency analysis tool provides a complete picture of what the executable needs. On Windows, a utility called Dependencies (the modern replacement for the classic Dependency Walker) scans an executable and lists every library it requires along with which ones are currently unresolvable.
Download the Dependencies tool from its GitHub releases page. Open it and drag the DwarfTherapist.exe file into the analysis window. The tool will display a tree of all required libraries, with any unresolved ones clearly highlighted.
This gives you a complete list of everything that needs to be resolved rather than discovering missing dependencies one at a time through repeated launch attempts.
Address each missing library identified by the tool using the appropriate method for its type. Microsoft runtime files are resolved through the Visual C++ Redistributable installer. Qt DLL files are resolved through re-extraction of the Dwarf Therapist archive.
Windows system libraries missing from the results indicate a deeper Windows installation issue that may require running the System File Checker utility via sfc /scannow in an elevated Command Prompt.
How to Fix Missing Dependencies on Linux and macOS
Resolving Missing Qt Libraries on Linux
On Linux the dependency resolution process is more direct because the package manager handles library installation cleanly without the complications of manually managed files.
The key is identifying the correct package name for your distribution that provides the missing library.
Launch Dwarf Therapist from a terminal to capture the full error output. The error message will name the missing shared object file. Use that name to identify the appropriate package. On Debian and Ubuntu based systems, use the apt-file tool to find which package provides a specific library file:
sudo apt install apt-file
sudo apt-file update
apt-file search libQt5Core.so.5
Once the package name is identified, install it:
sudo apt install libqt5core5a libqt5widgets5 libqt5gui5 libqt5x11extras5
On Arch Linux, Qt libraries are part of the qt5-base package:
sudo pacman -S qt5-base qt5-x11extrasOn Fedora:
sudo dnf install qt5-qtbase qt5-qtx11extrasAfter installing the missing libraries, relaunch Dwarf Therapist from the terminal to confirm the dependency warning is resolved. If a new missing library name appears, install the package that provides it using the same method.
It is common for a first installation to resolve one dependency only to surface another that was masked by the first failure.
If Dwarf Therapist launches successfully after library installation but cannot connect to Dwarf Fortress, the remaining issue is ptrace permissions rather than missing dependencies. This is a separate problem covered in the launch troubleshooting guide.
Fixing Missing Dependencies on macOS
On macOS, missing dependency issues most commonly appear after installing Dwarf Therapist from a prebuilt binary or after Homebrew updates Qt to a new major version following a source build. Both scenarios break the path that the application bundle uses to locate Qt frameworks.
For prebuilt binary installations, the first step is confirming that the binary was built for your macOS architecture.
Apple Silicon Macs require an arm64 build, while Intel Macs require an x86-64 build. Running a mismatched-architecture binary will produce a missing-dependency-style failure even when all required libraries are technically present on the system.
Check the architecture of the binary by running this command in Terminal:
file /path/to/DwarfTherapist.app/Contents/MacOS/DwarfTherapistThe output will state either arm64, x86_64, or universal, depending on whether the binary supports both. If the architecture does not match your Mac, you need a different binary or a source build for your architecture.
For source builds where Homebrew has updated Qt, run macdeployqt to re-embed the current Qt frameworks into the application bundle:
cd /path/to/build/directory
macdeployqt DwarfTherapist.appThis command copies the currently installed Qt frameworks from Homebrew into the application bundle, making the application self-contained and no longer dependent on the Homebrew installation path remaining stable.
After running macdeployqt, the application bundle can be moved to the Applications folder and will launch without external Qt dependencies.
| Platform | Most Common Missing Dependency | Package or Fix | Verification Command |
| Windows | VCRUNTIME140.dll | VC++ 2015 to 2022 Redistributable | Run DwarfTherapist.exe from Command Prompt |
| Windows | Qt5Core.dll | Re-extract full release archive | Check all Qt DLLs are present in install folder |
| Linux Debian/Ubuntu | libQt5Core.so.5 | sudo apt install libqt5core5a | ldd DwarfTherapist pipe grep not found |
| Linux Arch | qt5-base missing | sudo pacman -S qt5-base | ldd DwarfTherapist pipe grep not found |
| Linux Fedora | qt5-qtbase missing | sudo dnf install qt5-qtbase | ldd DwarfTherapist pipe grep not found |
| macOS | Qt framework path broken | Run macdeployqt on app bundle | file command to verify architecture |
| macOS | Wrong architecture binary | Download correct arch or build from source | file command on executable |
Post-Fix Verification and Long-Term Stability
Confirming the Fix and Testing the Full Launch
After addressing the missing dependency, close all related windows and perform a clean launch sequence. Start Dwarf Fortress first and load a fortress to an active game state.
Then launch Dwarf Therapist and observe whether the dependency warning appears again. If the application opens to the main grid without any warning dialog, the dependency issue is resolved. Verify that the grid populates with your dwarf roster by waiting a few seconds or triggering a manual refresh.
A populated grid confirms that not only did the application launch successfully but it is also connecting to the game process correctly.
On Linux, a useful command to proactively check for any remaining unresolved dependencies before launching is:
ldd /path/to/DwarfTherapist | grep "not found"This command lists every shared library the binary requires and flags any that cannot be located on the current system. Running this after each fix lets you resolve all missing libraries in a systematic pass rather than discovering them one by one through repeated launch failures.
Preventing Missing Dependency Warnings After Updates
Missing dependency warnings recur most often after three events: updating Dwarf Therapist to a new release, updating the operating system, or updating Homebrew on macOS. Each of these can change which library versions are present or where they are located.
After any Dwarf Therapist update on Windows, verify that the new archive includes all required Qt DLL files by checking the installation folder before launching. A missing file at this stage is easier to catch by inspection than by waiting for the warning to appear.
After macOS system updates, test Dwarf Therapist with a clean launch before relying on it for a play session. System updates occasionally modify framework search paths in ways that break previously stable source builds.
Running macdeployqt again after a significant macOS update restores self-contained operation. On Linux, major distribution upgrades that change the default Qt version from Qt5 to Qt6 will break existing Dwarf Therapist installations built against Qt5.
In this situation, rebuilding Dwarf Therapist from source against the new Qt version is the cleanest resolution.
FAQs
What does the missing dependencies warning mean in plain terms?
It means Dwarf Therapist cannot find one or more library files it needs to run. These libraries are separate from the application itself and must be present on your system. The warning names the specific file that is missing, which tells you exactly what to install or restore to resolve the problem.
Can I fix the missing dependencies warning by copying DLL files from another application?
This approach is strongly discouraged. DLL and shared library files are version-specific, and copying a file from another application that happens to have the same name will very likely cause version conflicts that produce new errors or silent data corruption.
Always install missing runtime libraries through their official installers or package managers to ensure version compatibility.
Why does the warning appear after a Dwarf Therapist update when it was working before?
A new Dwarf Therapist release may have been compiled against a different version of Qt or the Visual C++ runtime than the previous release. The new version requires a newer library that is not yet on your system. Install the updated runtime or Qt version indicated by the warning message to restore functionality.
The warning names a file I cannot find anywhere online. What should I do?
Search for the exact filename including the version suffix in the Dwarf Therapist GitHub Issues section and the Bay 12 Forums thread. Other users have likely encountered the same missing file.
If no result appears, post the exact filename in those communities with your platform and Dwarf Therapist version details. Community members can usually identify the correct package within a short time.
Is it safe to install the Visual C++ Redistributable from Microsoft’s website?
Yes. The Visual C++ Redistributable is a standard Microsoft runtime package distributed directly from Microsoft’s official download center. It is digitally signed, widely used by applications across Windows, and poses no security risk when downloaded from the official Microsoft source.
Always download it from microsoft.com directly rather than from third-party software distribution sites.
After fixing the dependency warning Dwarf Therapist still does not connect to Dwarf Fortress. Are these the same problem?
No. A missing dependency prevents the application from launching. A failure to connect to Dwarf Fortress after a successful launch is a separate issue related to process permissions, version mismatches, or memory layout problems.
The dependency fix addressed the launch barrier. The connection issue requires separate troubleshooting focused on version compatibility and platform permissions.
How do I know if I need the x86 or x64 Visual C++ Redistributable on Windows?
Install both. Even on a 64-bit Windows system, some components of Qt-based applications reference 32-bit runtime libraries. Installing only the x64 version can leave the x86 dependency unresolved, causing the warning to persist. The x86 and x64 installers are separate downloads and both should be run to ensure complete coverage.
Will fixing missing dependencies require me to reinstall Dwarf Fortress?
No. Missing dependency issues in Dwarf Therapist are entirely contained within the Dwarf Therapist application and the system libraries it depends on.
Dwarf Fortress itself is not involved in the dependency chain and does not need to be modified, reinstalled, or updated to resolve Dwarf Therapist dependency warnings.
Latest Post:
