It's not unusual to receive such an error when "booting up" after using anti-virus and other security scanning tools to remove malware infection.RunDLL32.exe
is a legitimate Windows file that executes (loads) .dll modules which too can be legit or 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 has been deleted and it becomes an orphaned registry entry
. Windows is trying to load this file(s) but cannot locate it since the file was removed during an anti-virus or anti-malware scan. However, the associated registry entry 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. (click here if you're not sure how to do this.)
- Open the folder and double-click on autoruns.exe to launch it.
- 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.
- Right-click on the entry and choose delete.
- Reboot your computer and see if the startup error returns.
Rescan again with MBAM (Quick Scan
) in normal mode and check all items found for removal. Don't forgot to check for updates before scanning and to reboot afterwards. Failure to reboot normally
(not into safe mode) will prevent MBAM from removing all the malware. When done, click the Logs
tab and copy/paste the contents of the new report in your next reply.