When de4dot runs without showing readable strings, the problem is rarely a single broken setting. String decryption depends on the protector used, the way the assembly was built, and the options you pass on the command line. This guide walks through the most common causes in a calm, methodical order so you can find the fault without guessing or damaging your original file.
Start with a safe copy and a simple test
Always work on a copy of the assembly and keep the original untouched. Run de4dot on that copy with no extra options first, then compare the output. If the cleaned file opens but strings remain encrypted, the issue is likely tied to the specific string protection method rather than a basic setup error. If de4dot stops early, read the full error message before changing anything, because that message often points to a missing dependency or an unsupported protector.
Check whether the protector is supported
Some protectors use custom string encryption that de4dot can only partly reverse. Others combine string encryption with control flow changes, which makes recovery harder. In that case, a partial result is still useful. You may recover class structure and some readable text even when a few strings stay hidden. Record which protector was detected, because that detail will guide every later step and help you decide whether another pass with different options is worthwhile.
Look for missing dependencies
A cleaned assembly can fail to reveal strings when a referenced library is missing. De4dot needs to resolve the types used by the program, and a missing reference can interrupt that process. Place the main assembly together with its supporting libraries in one folder, then run de4dot again. This simple step resolves many confusing cases where the tool appears to finish but the output looks incomplete.
Try a clean run before adding options
Extra options can help, but they can also hide the real problem when they are added too early. Start with the basic command, check the result, and only then test one change at a time. If you use an option that keeps original names, note that it may change how readable the output looks without changing whether strings are decrypted. Keep a short log of each attempt, including the command used and what changed in the output.
Inspect the output in a decompiler
Open the cleaned file in a .NET decompiler and search for a string you expect to find, such as a window title, an error message, or a menu label. If those strings are readable, decryption worked for that part of the program. If only some strings appear, focus on the code around the missing ones. That pattern can show whether one method, one class, or one library is responsible for the remaining encryption.
For background on how the tool works overall, see what de4dot does and how it works. For a reference to the options you may test one at a time, see the de4dot command line options explained.
A practical checklist
Work from a copy, confirm the detected protector, gather supporting libraries, run a basic pass first, and inspect the result before adding options. When a string stays encrypted, check whether the same pattern appears in other methods or only in one area. That distinction often tells you whether the limit is in the tool, the protector, or a missing file.
When to stop and use the partial result
Not every protected file can be fully restored, and that is a normal limit of deobfuscation rather than a sign that you made a mistake. A partial result can still support analysis, debugging, or research, especially when the main logic and most strings are readable. Document what was recovered, what remained encrypted, and which commands you tried, so your work can be checked and repeated later.
Frequently Asked Questions
Why does de4dot finish but strings stay encrypted
This usually means the string protection method is custom or only partly supported, or a referenced library was missing during the run.
Should I run de4dot several times on the same file
Running it again on an already cleaned file rarely helps and can make the output harder to read. Start fresh from your untouched copy for each new test.
Can a missing DLL cause string decryption to fail
Yes, a missing dependency can interrupt type resolution and leave parts of the output incomplete, so keep related files together.
Does keeping original names affect string decryption
Keeping names changes readability, not the decryption process itself, so test it separately from other options.
What should I record after a failed attempt
Record the protector detected, the exact command, the error message if any, and what the output looked like, because those details make the next attempt much easier.


