Troubleshooting Guide
Solutions to common issues and problems with Deadlock Mod Manager
Common Installation Issues
Application Won't Start
Symptoms: The application fails to launch or crashes immediately upon startup.
Windows Solutions
-
Run as Administrator
# Right-click the application and select "Run as administrator" -
Check Windows Defender/Antivirus
- Add an exception for the mod manager in your antivirus software
- Temporarily disable real-time protection to test
-
Install Visual C++ Redistributables
# Download and install the latest Visual C++ Redistributable # Available from Microsoft's website -
Update Windows
- Ensure you're running Windows 10 version 1903 or later
- Install all pending Windows updates
-
Check for the
OPENSSL_ia32capenvironment variable- If the window never appears and nothing above helps, see Windows: App Closes Instantly on Launch
Linux Solutions
-
Install Dependencies
# Ubuntu/Debian sudo apt update sudo apt install libwebkit2gtk-4.0-dev libappindicator3-dev librsvg2-dev # Arch Linux sudo pacman -S webkit2gtk gtk3 librsvg # Fedora sudo dnf install webkit2gtk3-devel gtk3-devel librsvg2-devel -
Fix Wayland + NVIDIA Issues
# Launch with environment variable WEBKIT_DISABLE_COMPOSITING_MODE=1 deadlock-modmanager -
Permissions Issues
# Make AppImage executable chmod +x deadlock-modmanager-*.AppImage
Windows: App Closes Instantly on Launch
Symptoms: On Windows, version 1.1.0 or later closes the moment you open it, before any window appears. Reinstalling and clearing app data don't help, and version 1.0.0 may still start normally. Event Viewer shows an application error for the mod manager, and other apps built on the same networking stack can crash the same way.
Cause: The OPENSSL_ia32cap environment variable is set on your PC without a leading ~, for example OPENSSL_ia32cap=0x20000000. Guides for older games often recommend this variable, usually as ~0x20000000. With the ~, it turns a CPU feature off. Without it, it asks for CPU features that your processor may not have, and the encryption library the mod manager uses for secure connections stops the app at startup. This happens before the mod manager's own code runs, so the app can't show an error.
Check Whether the Variable Is Set
Open PowerShell and run:
[Environment]::GetEnvironmentVariable('OPENSSL_ia32cap','User')
[Environment]::GetEnvironmentVariable('OPENSSL_ia32cap','Machine')If either command prints a value that doesn't start with ~, this is the cause.
Remove or Fix the Variable
- Press Start, type environment variables, and open Edit the system environment variables
- Click Environment Variables...
- Find
OPENSSL_ia32capunder both User variables and System variables - Delete it. If an older game needs it, change the value to start with
~instead, for example~0x20000000 - Sign out and back in, or restart your PC, so every program picks up the change
The space in a Windows username or install path is not related to this crash.
Flatpak Opens to a Grey Screen on NVIDIA
Symptoms: The Flatpak application opens, but its window stays grey or blank on Linux with an NVIDIA GPU.
Community-reported workaround: Community member optimisticlucio shared this workaround in issue #281. They reported that manually disabling WebKit's DMA-BUF renderer fixed the grey screen, even with matching host and Flatpak NVIDIA drivers. Flatpak's sandbox can prevent automatic NVIDIA detection from enabling this workaround.
Apply the Rendering Workaround
Fully quit Deadlock Mod Manager, including any running tray instance. Run these commands in a terminal on your Linux host:
flatpak override --user --env=WEBKIT_DISABLE_DMABUF_RENDERER=1 dev.stormix.deadlock-mod-manager
flatpak run dev.stormix.deadlock-mod-managerThe override persists for your user and applies when launching from the desktop menu too. It disables one WebKit rendering path and may reduce rendering performance.
To remove this override later, fully quit the app, run the following command, and launch it again:
flatpak override --user --unset-env=WEBKIT_DISABLE_DMABUF_RENDERER dev.stormix.deadlock-mod-managerIf the Screen Still Stays Grey
Community contributor Mackamuir also suggested checking for mismatched host and Flatpak NVIDIA drivers in issue #281:
nvidia-smi
flatpak list --runtime | grep nvidia
flatpak updateCompare the driver version reported by nvidia-smi with the installed org.freedesktop.Platform.GL.nvidia-* runtime. Flatpak encodes version dots as hyphens: for example, driver 570.124.04 corresponds to nvidia-570-124-04. Multiple installed NVIDIA runtimes are normal; look for one matching your host driver. After updating, fully quit and relaunch the app.
If the issue persists, share those command outputs, your Linux distribution, app version, and whether the rendering override helped in issue #281.
Game Detection Problems
Symptoms: The mod manager can't find your Deadlock installation.
Automatic Detection Failed
-
Verify Deadlock Installation
- Ensure Deadlock is installed through Steam
- Launch Deadlock at least once to create necessary files
- Verify the game runs without issues
-
Check Steam Library Locations
- Open Steam Settings > Downloads > Steam Library Folders
- Note all library locations where games might be installed
- Look for Deadlock in each library under
steamapps/common/Deadlock
Flatpak Crashes When Selecting the Game Folder
Symptoms: On Steam Deck or other Linux systems, opening the folder picker in Settings > Game briefly shows a dialog and then crashes the app. Automatic game detection may also fail.
Community-reported workaround: Community member Hyperiya shared the filesystem-permission workaround in issue #521, reporting that granting access through Flatseal or the terminal resolved this problem. Rubyboat1207 confirmed the host-filesystem override below worked in the related issue #516.
Fully quit Deadlock Mod Manager, including any running tray instance. On Steam Deck, switch to Desktop Mode to use Flatseal or a terminal.
Grant Access to Your Steam Library
To try a narrower permission first, open Flatseal, select Deadlock Mod Manager, and add your Steam library's absolute path under Filesystem > Other files. Include any library on an SD card or external drive that contains Deadlock. Find the library location in Steam > Settings > Storage.
Alternatively, run this in a terminal on your Linux host, replacing the example path with your Steam library's actual path:
flatpak override --user --filesystem="/absolute/path/to/SteamLibrary" dev.stormix.deadlock-mod-managerRelaunch the app and try selecting the game folder again. This grants the app read/write access to that library so it can manage mods there.
Community Workaround: Host Filesystem Access
If granting access to just the library does not resolve the crash, try the broader override reported by Rubyboat1207 in issue #516:
flatpak override --user --filesystem=host dev.stormix.deadlock-mod-manager
flatpak run dev.stormix.deadlock-mod-managerThis persistent override grants read/write access to much of your host filesystem, beyond your Steam library. In Flatseal, the equivalent is enabling Filesystem > All system files for Deadlock Mod Manager.
To revoke the host access later, fully quit the app, run the following command, and relaunch it:
flatpak override --user --nofilesystem=host dev.stormix.deadlock-mod-managerTo revoke a library-specific grant instead, remove its entry in Flatseal or use --nofilesystem="/absolute/path/to/SteamLibrary" with the same app ID.
The thread does not confirm a fix for the separate recurring “Something went wrong” notification. If folder selection still crashes after granting access, include your app version, Linux distribution, Steam library location, and permissions tried in issue #521.
Download and Installation Issues
Download Failures
Symptoms: Mods fail to download or downloads stop unexpectedly.
Network Issues
-
Check Internet Connection
- Test your internet connection with other applications
- Try downloading from a web browser to test connectivity
-
Firewall/Antivirus Blocking
- Add Deadlock Mod Manager to firewall exceptions
- Check if your antivirus is blocking downloads
- Temporarily disable firewall/antivirus to test
-
Proxy/VPN Issues
- If using a proxy or VPN, try disabling it temporarily
- Configure proxy settings if needed in the app settings
Server Issues
-
GameBanana Server Problems
- Check if GameBanana is accessible in your web browser
- Wait and retry if servers are experiencing issues
- Try downloading at a different time of day
-
Regional Restrictions
- Some mods may have regional download restrictions
- Try using a VPN to a different region if necessary
Windows: Downloads Are Very Slow
Symptoms: GameBanana downloads crawl at a few hundred KB/s on Windows, whichever download routing option you pick, while speed tests and other downloads on the same PC are fast. A 250 MB mod takes 15 minutes or more.
Cause: Windows' TCP receive window auto-tuning is turned off. Without it, each connection can only have 64 KB in flight, so its speed is capped by the distance to the server rather than by your internet plan. GameBanana's file servers are far from many players (around 240 ms away from Southeast Asia, for example), where this cap works out to roughly 250 KB/s per download. Auto-tuning is on by default. It is usually turned off by an old "fix slow downloads" or game patching guide that recommends netsh int tcp set global autotuninglevel=disabled, or by a "network optimizer" tool.
Check Whether Auto-Tuning Is Off
Open PowerShell and run:
Get-NetTCPSetting -SettingName Internet | Select-Object AutoTuningLevelLocalIf it prints Disabled, HighlyRestricted or Restricted, this is the likely cause. netsh interface tcp show global shows the same setting as Receive Window Auto-Tuning Level.
Turn Auto-Tuning Back On
-
Press Start, type PowerShell, right-click Windows PowerShell, and choose Run as administrator
-
Run:
netsh interface tcp set global autotuninglevel=normal -
Cancel any download that is still running and start it again, since it keeps using its old connection. You don't need to restart your PC
If downloads get slow again later, check the setting again: some optimizer tools turn it back off when they run. If you turned it off on purpose, for example to work around a router problem, run the same command with autotuninglevel=disabled to go back.
Mod Installation Failures
Symptoms: Downloads complete but mods don't install properly.
Permission Issues
-
Insufficient Permissions
# Windows: Run as administrator # Linux: Check folder permissions sudo chmod -R 755 /path/to/deadlock/installation -
Read-only Files
- Check if game files are set to read-only
- Disable Steam's file verification if enabled
- Ensure no other applications have game files locked
-
Access is denied. (os error 5)
- This error typically occurs when the mod manager lacks permission to modify files
- gameinfo.gi is read-only: Right-click the file, select Properties, and uncheck "Read-only"
- Addons folder is read-only: Check folder properties and remove read-only attribute
- High-privilege existing mods: Some mods may have been installed with elevated privileges and cannot be removed by the mod manager. Try running the mod manager as administrator or manually remove the problematic mod files
Disk Space Issues
- Check Available Space
- Verify sufficient disk space in both download and game directories
- Clear temporary files if space is low
- Move game installation to a drive with more space if needed
Stuck Downloads and Installations
Symptoms: Mods get stuck during download or installation process and won't complete.
Recovery Solutions
-
Remove Individual Stuck Mod
- Use the trash can icon next to the stuck mod to remove it
- Wait for the removal process to complete
- Try downloading/installing the mod again
-
Clear All Mods (Nuclear Option)
Clear All Mods deletes files
Clear All Mods removes every tracked mod from the active profile and deletes its installed VPKs and downloaded files, including downloads shared with other profiles. Unrecognized files are kept. Back up local mods and any downloads you cannot get again before you confirm.
If individual mod removal doesn't work:
- Navigate to Settings > Tools
- Click Clear All Mods and confirm
If you only need to reset the mod list, use Clear Mods State in the same section instead. It resets the list without deleting mod files, and restarting the app restores the mods recorded in its ownership manifest.
-
Alternative Manual Recovery
To keep your installed VPKs while clearing a stuck state:
- Copy the mods from your game's
addonsfolder to a safe location - Use Clear All Mods in Settings > Tools
- Copy the saved VPKs back to the
addonsfolder - Use Analyze Local Addons to reconnect them to the mod manager
This keeps only the VPKs that were installed. Other files from the original downloads, such as variants you had not installed, are deleted and have to be downloaded again.
- Copy the mods from your game's
Mod-Related Issues
Mods Not Working In-Game
Symptoms: Mods appear installed but don't work in Deadlock.
Not sure which mod is the problem?
If the game crashes or looks wrong with your mods on, use Find a broken mod. It turns mods off in rounds and narrows the problem down to one mod, or two that conflict.
Game Version Compatibility
After a Deadlock update, check the mod's health badge in Mods Library. Mods marked Can be fixed or Can be partly fixed can be repaired locally; see Fixing Mods After Game Updates.
-
Check Game Version
- Verify your Deadlock version matches mod requirements
- Update Deadlock if you're running an older version
- Check mod description for version compatibility notes
-
Mod Updates Required
- Check if the mod has been updated for recent game versions
- Look for alternative or updated versions of the mod
- Contact mod authors for compatibility updates
Installation Verification
-
Verify Mod Files
- Check that mod files are in the correct game directories
- Look for any error messages when toggling the mod on/off
- Try reinstalling the problematic mod
-
Mod Conflicts
- Disable other mods to test if there's a conflict
- Check mod descriptions for known conflicts
- Install conflicting mods one at a time to identify issues
Application-Specific Issues
User Interface Problems
Symptoms: The interface doesn't display correctly or is unresponsive.
Display Issues
-
Scaling Problems
- Check your system display scaling settings
- Try different scaling values (100%, 125%, 150%)
- Restart the application after changing scaling
-
Theme/Rendering Issues
- Switch between light and dark themes
- Clear the application cache in settings
- Try different window sizes
Responsiveness Issues
If the app is slow or laggy, install the CEF build first. It bundles Chromium, which generally performs better than the system webview, especially on Linux. On Ubuntu/Debian, switch the APT repository to the cef component as described in the installation guide.
-
High CPU Usage
- Check for runaway processes in Task Manager
- Restart the application
- Check for system-wide performance issues
-
Memory Leaks
- Monitor memory usage over time
- Restart the application periodically for long sessions
- Report persistent memory issues on GitHub
Settings and Configuration
Symptoms: Settings don't save or reset unexpectedly.
Configuration File Issues
-
Corrupted Settings
- Close the application completely
- Navigate to the application data directory:
- Windows:
%APPDATA%\deadlock-mod-manager\ - Linux:
~/.config/deadlock-mod-manager/
- Windows:
- Delete or rename the configuration file
- Restart the application to regenerate default settings
-
Permission Issues
- Ensure the application has write permissions to its data directory
- Check if antivirus is blocking configuration writes
- Run as administrator (Windows) if necessary
Network Diagnostics
Connection Testing
-
Test API Connectivity
# Test connection to the API curl -I https://api.deadlockmods.app/mods -
DNS Issues
- Try using different DNS servers (8.8.8.8, 1.1.1.1)
- Flush DNS cache:
- Windows:
ipconfig /flushdns - Linux:
sudo systemctl restart systemd-resolved
- Windows:
Getting Additional Help
Self-Service Resources
Community Support
-
Discord Community
- Join our Discord server for real-time help
- Search previous discussions for similar issues
- Ask questions in the support channels
-
GitHub Issues
- Search existing issues for your problem
- Create a new issue if your problem isn't covered
- Include detailed information and logs when reporting
Reporting Bugs
When reporting issues, please include:
Bug Report Checklist
- Detailed description of the problem - [ ] Steps to reproduce the issue - [ ] System information (OS, version, etc.) - [ ] Application version and build number - [ ] Screenshots or screen recordings if relevant - [ ] Log files from the time of the issue - [ ] List of installed mods (if relevant)
Emergency Recovery
Complete Reset
If all else fails, you can completely reset the application:
-
Backup Your Mod List
- Export your installed mods list from Settings (if possible)
- Make note of which mods you had installed
-
Complete Uninstall
- Uninstall the application normally
- Delete the application data directories (listed above)
- Clear any remaining registry entries (Windows)
-
Fresh Installation
- Download and install the latest version
- Reconfigure settings from scratch
- Reinstall mods as needed
Remember, the community is always ready to help! Don't hesitate to reach out on Discord or GitHub if you can't resolve an issue using this guide.