Automatically finds all installed Steam, Epic and Ubisoft games with their respective DLC-related DLL locations on the user's computer, parses SteamCMD, Steam S
Automatically finds all installed Steam, Epic and Ubisoft games with their respective DLC-related DLL locations on the user's computer, parses SteamCMD, Steam S
Automatically finds all installed Steam, Epic and Ubisoft games with their respective DLC-related DLL locations on the user's computer, parses SteamCMD, Steam Store and Epic Games Store for user-selected games' DLCs, then provides a very simple graphical interface utilizing the gathered information for the maintenance of DLC unlockers.
The primary function of the program is to automatically generate and install DLC unlockers for whichever games and DLCs the user selects; however, through the use of right-click context menus the user can also:
Expand for more info on CI Builds
If the program doesn't seem to launch, try downloading and installing .NET Desktop Runtime 8.0.7 and restarting your computer. Note that the program currently only supports Windows 10+ 64-bit machines as seen here.
Click to expand for troubleshooting steps
Check the following in order:
If none of these work, your system may not support .NET 8 or may have underlying system issues.
Click to expand for troubleshooting steps
CreamInstaller only installs DLC unlockers it does not guarantee they will work for every game.
If the program successfully installs the unlockers but DLCs still aren't unlocking, this is not an issue with CreamInstaller itself and isn't something I can directly fix. DLC Unlocker compatibility and behavior vary from game to game.
DLC Files: This program does not automatically download or install actual DLC files for you. As the name implies, it is only a DLC unlocker installer. If the game you wish to unlock DLC for does not already include the DLC files (which is the case for many games), you must manually obtain and install those files yourself. This includes manually installing new DLCs and manually updating or reinstalling previously installed DLCs after game updates.
If you're having trouble, try the following:
These are false positives. See the detailed explanation below:
Click to expand for information about false positives
CreamInstaller is not a virus, but it's commonly flagged because of its functionality:
| Reason | Explanation |
|---|---|
| DLL modification | Replaces game DLLs to unlock content behavior similar to some malware |
| Process hooking | Embedded DLC unlockers interact with Steam/Epic/Ubisoft/game processes |
| Compressed executable | Single file executables are often associated with packed malware |
| Not code-signed | No Extended Validation certificate ($300–500/year) means lower AV reputation (I will not be paying for this) |
| Misc | Game modding tools frequently trigger heuristic detections regardless of intent |
| Detection Name | What It Usually Means / Why It’s a False Positive |
|---|---|
| Mamson.A!ac | Generic heuristic detection; often triggered by packed or obfuscated executables |
| Phonzy.A!ml | Machine learning detection; flags unusual behavior patterns |
| Wacatac.H!ml | Extremely common false positive; triggered by compressed or self-updating programs |
| Malgent!MSR | Generic Microsoft label for “suspicious behavior,” not confirmed malware |
| Tiggre!rfn | Heuristic runtime detection often seen with tools that hook processes |
| UDS:DangerousObject.Multi.Generic | Reputation based detection for tools that can be abused |
| Trojan.Win64.Agent | Very broad category; common false positive for unsigned binaries |
| Trojan.Win64.Agent.oa!s1 | Cloud/AI heuristic variant of the above |
| Backdoor.Agent | Heuristic detection for applications that download remote content, extract archives, spawn processes, and self-replace. |
See also: Archived issue #40
CreamInstaller is 100% open source:
Click to expand for full walkthrough
If CreamInstaller's default proxy mode (winmm.dll) doesn't work for your game, you may need to proxy a different DLL one that the game already attempts to load on its own. The easiest way to discover which DLLs your game tries to load is Process Monitor (ProcMon) from Microsoft Sysinternals.
This method reveals:
Download and run Process Monitor (ProcMon) from Microsoft Sysinternals. Running ProcMon as Administrator is required to capture all process and file events.
Start ProcMon. Clear any pre-existing events using Ctrl + X or Edit → Clear Display.
Open the filter dialog with Ctrl + L and add the following filters:
| Column | Relation | Value | Action |
|---|---|---|---|
| Process Name | contains | `` | Include |
| Result | contains | NAME NOT FOUND | Include |
| Path | ends with | dll | Include |
Replace `` with part of the game executable name e.g., Risk of Rain for Risk of Rain 2.exe.
ProcMon will record every DLL load attempt matching your filters.
Look for entries with:
Result: NAME NOT FOUNDThese entries indicate the game searched for those DLLs but did not find them exactly the kind of load attempt a proxy DLL can hook into.
Example output:
GameFolder\version.dll
GameFolder\winmm.dll
GameFolder\winhttp.dll
The recorded paths reveal exactly where the game expects each DLL to exist and which DLL names it looks for.
No open issues yet, or sync has not completed.