Home Fix Fix “There was a problem starting StartupCheckLibrary.dll”

Fix “There was a problem starting StartupCheckLibrary.dll”

by Mohsin Raza

If you get an error message — There was a problem starting StartupCheckLibrary.dll, The specified module couldn’t be found — then this post will help you settle the problem.

StartupCheckLibrary.dll is an official Microsoft Windows framework file that is located in the C:\Windows\System32 folder. If it located somewhere else, it very well may be malware.

There was a problem starting StartupCheckLibrary.dll

Now since Windows is unable to find the module, it could mean that the file has disappeared, has been erased or has gotten corrupted. Here are a few proposals that will help you push ahead.

  • Check if your Antivirus has quarantined the file.
  • Run SFC Command
  • Disable StartupCheckLibrary.dll section from the Startup

You will require administrative authorization to determine this missing DLL file issue.

1] Check if Antivirus has quarantined the file.


If you are using Windows Security, open it, go to the Virus and threat assurance segment, 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.

To begin with, the DLL has been marked as Trojan/Virus, and-

  • It could really be an infection or
  • It very well may be a false alarm.

Disconnect from the internet and go to the Windows Defender Quarantine area, 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 appears as something else, it very well may be malware and it is ideal to allow it to remain there.
  • and click remove the file from the quarantine. The file will be placed back in the original place.

Now if the file is genuine, then it could get taken out again, and for that, you should add an Exclusion. Whenever it is identified again, you can click on the Action button and then move it to the Allowed Threats area.

If it was marked as an infection, then you should erase it.

2] Run SFC Command

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

  • Open Command Pr0ompt with the admin privileges.
  • Type SFC/scannow, and hit Enter.
  • Allow it to finish its work.
  • It is conceivable that the cycle may repair different files as well.

Once through this, you ought not to get this error.

3] Disable StartupCheckLibrary.dll passage from the Startup


If none of these work, the DLL is infected, and you actually get the error; the last choice is to disable or eliminate it from the startup passage. While Windows allows removing applications, it is difficult to eliminate a DLL. That is the place where the Autoruns program from Microsoft comes into the image.

Also see: Enable or Disable Hardware Acceleration in Microsoft Edge

Autoruns is an amazing utility that can locate anything which should run when Windows starts and the user signs into the account.

When you download the utility and run it, you can search with the DLL name. When it appears in the rundown, you can uncheck it. It will make sure you don’t get the error.

You may also like

Leave a Comment