It's not unusual to receive such an error(s) when "booting up" after using anti-virus and other security scanning tools to remove a malware infection.RunDLL32.exe
is a legitimate Windows file that executes/loads .dll
(Dynamic Link Library) modules which too can be legitimate or sometimes malware related. A RunDLL "Error loading...
" or "specific module could not be found
" message usually occurs when the .dll file(s) that was set to run at startup in the registry has been deleted. Windows is trying to load this file(s) but cannot locate it since the file was mostly likely removed during an anti-virus or anti-malware scan. However, an associated orphaned registry entry
still remains and is telling Windows to load the file when you boot up. Since the file no longer exists, Windows will display an error message
. You need to remove this registry entry so Windows stops searching for the file when it loads.
To resolve this, download Autoruns
, search for the related entry and then delete it.
- Create a new folder on your hard drive called AutoRuns (C:\AutoRuns) and extract (unzip) the file there.
Vista/Windows 7 users refer to these instructions.
- Open the folder and double-click on autoruns.exe to launch it.
Vista/Windows 7 users right-click and select Run As Administrator.
- Please be patient as it scans and populates the entries.
- When done scanning, it will say Ready at the bottom.
- Scroll through the list and look for a startup entry related to the file(s) in the error message.
- If found, right-click on the entry and choose delete.
- Reboot your computer and see if the startup error returns.
If you're going to keep and use Autoruns, be sure to read: