Work through these troubleshooting steps in order, starting with the easiest and most common fixes. 1. Run the Application as an Administrator
Right-click dlllist.txt → Properties → Security → ensure your user has permission.
Antivirus tools frequently sandbox text scripts interacting with dynamic library links. Open via the start menu.
In Windows operating systems, translates directly to ERROR_FILE_NOT_FOUND .
Run SFC /scannow followed by DISM /Online /Cleanup-Image /RestoreHealth to fix underlying Windows image errors. : failed to open dlllist.txt for reading error code 2
typically indicates a missing file or a leftover configuration from a previous software installation. In Windows, "Error code: 2" specifically translates to "The system cannot find the file specified" Microsoft Learn Summary of the Issue
sfc /scannow
Broken Visual C++ Redistributable files prevent applications from executing file-reading scripts.
If you are running a custom script (Python, PowerShell, CMD) and seeing this error, the issue is likely a problem. Work through these troubleshooting steps in order, starting
Here are the most effective methods to resolve the "Failed to open dlllist.txt for reading" issue, ordered from the most common fix to more advanced troubleshooting. 1. Reinstall or Verify Game Integrity (For Gaming Issues)
If you are using Dependency Walker and keep seeing this error, you might be accidentally launching it with a script argument.
: Antivirus tools often isolate or quarantine dlllist.txt or its associated hooks, mistaking them for unauthorized script injection tools.
Then run your dlllist command from there. Run SFC /scannow followed by DISM /Online /Cleanup-Image
The user account running the tool does not have read permissions for the folder containing the file.
I can give you a more tailored solution if I know the context.
In 99% of cases, this error is not caused by a virus, corrupt Windows installation, or failing hard drive. It is caused by a legacy, but still widely used, tool called (also known as depends.exe ).
(Also — related search terms prepared.)
Delete these custom files, clear out your Windows temporary directory ( Win + R , type %localappdata%\Temp , delete entries), and try booting the clean application vanilla style. 4. Run SFC and DISM Repairs via PowerShell