A friend of mine had an error at startup of his computer. RunDLL There was a problem starting winscomrssv.dll. The specific module could not be found.
Table of Contents
What happened before
Previously he’d been a victim of a trojan virus. His antivirus program quarantined three files from C:\Windows\System32:
Afterwards, his pc was running fine and smoothly. Windows Defender did not find any threats. Still he got these RunDLL module errors at startup.
How to fix There was a problem starting winscomrssv.dll
The winscomrssv.dll and startupchecklibrary.dll errors are definitely the dreg of the malware that was present before.
I was sure all threats were solved. I only needed to remove the references to the (missing) DLL files. Sysinternals Autoruns is a great free lightweight tool to help you with this.
Detailed steps to fix winscomrssv.dll
- Download and unzip Autoruns from https://docs.microsoft.com/en-us/sysinternals/downloads/autoruns
- It’s also an option to download the Sysinternals Live version of Autoruns.
- Rightclick the downloaded Autoruns.exe and choose Run As Adminstrator
- In the Filter box, type winscomrssv
- View the result. Any ‘File not Found’ image paths, are save to delete.
- Do the same for startupchecklibrary. Any File Not Found results can be safely removed.
Malware often leaves traces behind. Even when the malware is remove by your antivirus program. However, errors like “The specific module could not be found” are not always caused by malware. An upgrade of Windows 10 or uninstallation of 3rd party software may also leave traces. A great example is Logitechs logilda.dll
In most cases, Sysinternals Autoruns.exe may help you remove these kind of startup errors.