If you’re a system administrator, a forensic analyst, or a power user troubleshooting processes on Windows, you’ve likely encountered the frustrating error message:
| Purpose | Alternative Tool | Command Example | |---------|----------------|------------------| | List DLLs for a process | tasklist /m | tasklist /m /fi "PID eq 1234" | | List DLLs for all processes | Get-Process in PowerShell | Get-Process | Select-Object -ExpandProperty Modules | | Detailed DLL info | listdlls (another Sysinternals tool) | listdlls.exe explorer | | Process explorer GUI | procexp.exe (Sysinternals) | Interactive | failed to open dlllist.txt for reading error code 2
cd C:\my_scripts dlllist.exe @dlllist.txt Even if the file exists, error code 2 can appear if the process lacks permission to read the file. If you’re a system administrator, a forensic analyst,
If you continue to encounter this error even after applying the fixes above, verify which script or parent process is invoking dlllist.exe — the culprit is often a legacy batch file written for a different version of the Sysinternals suite. Always run dlllist.exe /? to view the correct syntax for your version. Newer releases may have deprecated response file support. By following this guide, you’ll not only resolve the "error code 2" message permanently but also gain deeper insight into how Windows tools handle file input — knowledge that will serve you well in countless future troubleshooting sessions. to view the correct syntax for your version
dlllist.exe @dlllist.txt # WRONG – treats file as command source The correct approach is to use redirection for input , not @ :