• Donate
    TheWindowsForum.com needs donations to stay online!
    Love TheWindowsForum.com? Then help keep it alive by sending a donation!

There was a problem starting StartupCheckLibrary.dll

WELCOME TO THEWINDOWSFORUM COMMUNITY!

Our community has more than 63,000 registered members, and we'd love to have you as a member. Join us and take part in our unbiased discussions among people of all different backgrounds about Windows OS, Software, Hardware and more.

Makram

New Member
Nov 27, 2021
2
1
Hi there,
Is there a chance to help me resolving this issue.
Two messages appear after each restart and I don't know for what:

1st message is: There was a problem starting StartupCheckLibrary.dll
The specified module could not be found.

2nd message is: There was a problem starting winscomrssrv.dll
The specified module could not be found.


Really appreciate it!
Pls find attached screenshots of both message.

Sincerely yours,
Makram
:)
 

Attachments

  • StartupCheckLibrary.dll Screenshot.png
    StartupCheckLibrary.dll Screenshot.png
    6.5 KB · Views: 1
  • Winscomrssrv.dll Screenshot.png
    Winscomrssrv.dll Screenshot.png
    6.8 KB · Views: 1

There was a problem starting StartupCheckLibrary.dll​

Now since Windows is unable to find the module, it could mean that the file has gone missing, has been deleted or has become corrupted. Here are some suggestions that will help you move forward.

  • Check if your Antivirus has quarantined the file.
  • Run SFC Command
  • Disable StartupCheckLibrary.dll entry from the Startup
You will need administrative permission to resolve this missing DLL file issue.

1] Check if Antivirus has quarantined the file.​

Windows-Security-Virus-and-Threat-protection.jpg


If you are using Windows Security, open it, go to the Virus and threat protection section, and click on the Protection history link. It will list the files, and if you find the StartupCheckLibrary.dll. There can be two situations here.

First, the DLL has been marked as Trojan/Virus, and-

  1. It could really be a virus or
  2. It could be a false positive.
Disconnect from the internet and go to the Windows Defender Quarantine section, You will see the file quarantined there. Click on See details, and check the file path.


  • If it was from the System 32 folder you may click the Restore button.
  • If the path is shown as something else, it could be malware and it is best to let it remain there.
and clickremove the file from the quarantine. The file will be placed back in the original place.

Now if the file is legit, then it could get removed again, and for that, you will need to add an Exclusion. Once it is detected again, you can click on the Action button and then move it to the Allowed Threats section.

StartupCheckLibrary DLL Threat


If it was marked as a virus, then you will need to delete it.

2] Run SFC Command​

SFC or System File Checker command can scan Windows and replace any corrupted or missing system files. Follow the steps below:

  • Open Command Pr0ompt with elevated privileges.
  • Type SFC /scannow, and hit Enter.
  • Let it complete its job.
  • It is possible that the process may repair other files as well.
Once through this, you should not receive this error.

3] Disable StartupCheckLibrary.dll entry from the Startup​

Autorun Find Program


If none of these work, the DLL is infected, and you still get the error; the last option is to disable or remove it from the startup entry. While Windows allows removing applications, it is not easy to remove a DLL. That is where the Autoruns program from Microsoft comes into the picture.
 
There is a very good chance you are looking at the leftovers from a trojan infection, the fact that you are getting the error for winscomrssrv.dll is kind of the tell. The steps that Thumper has outlined for you are correct, just be aware that something attempted to infect you with a data stealing trojan. More than likely your A/V blocked and removed the offending files, but it's definitely worth your while to do an online scan of your system as whatever is installed on your system may have been corrupted.
You might want to be a little more careful with what you are installing on your system. That's what makes a site like 1337x so valuable, if an upload is a problem, someone usually lets you know not to mention their posts are vetted before they are published.
 
Back