When de4dot reports that it cannot load an assembly, the file may be missing a dependency, locked by another program, or in a format it cannot read. Rather than guessing, work through a short set of checks that reveal the cause. This guide explains them in order.
Confirm the file path and access
Check that the file exists at the path you used, that the name is spelled correctly, and that no other program has it open. A locked file or a moved file can cause a loading error even when the assembly itself is fine. Working from a copy in a simple folder path also avoids problems with long or unusual paths.
Check dependencies and the runtime
Place the assembly beside the libraries it references, and confirm you are using a compatible .NET runtime. A missing reference or a Framework versus Core mismatch can stop de4dot from loading the file. If the program normally runs with extra libraries, gather those libraries first.
Confirm the file is a managed assembly
Make sure the file is a managed .NET assembly and not a native executable or a corrupted download. Try opening it in a decompiler or a simple assembly viewer. If no .NET tool can load it, the problem is likely the file itself rather than de4dot.
Try a clean copy and a basic pass
Start again from a fresh copy of the original, with its libraries present, and run a basic de4dot pass. If that works, the earlier error was likely caused by a locked file, a missing library, or a damaged copy. Record the steps that fixed it so you can repeat them later.
For general troubleshooting, see how to fix de4dot not working. For system needs, see de4dot system requirements for Windows.
Frequently Asked Questions
What does unable to load assembly mean
It means de4dot could not open or read the file in its current state, often because of access, dependencies, or format.
Should I try a different file copy
Yes, a fresh copy rules out a locked or damaged file and is a quick first test.
Can a missing library cause this error
Yes, missing references can stop loading, so gather the libraries the program normally uses.
Is the file always damaged
No, many loading errors are caused by path, access, or runtime problems rather than damage.
What should I check first
Check the path, file access, dependencies, and runtime, in that order.


