Windows 10: Sigverif reported a dll file that is not signed. What do i do?

Hellu,


today I was unable to start a game and was suggesting to run a sigverif.

After doing that I found out that the file "nvcpl.dll" was not signed.

I thought updating or reinstalling the Nvidia Geforce driver might be the solution, however

I still encounter this file not being signed, which makes me unable to play a certain game.


Now my question: What do I do? What can fix this issue?


Thank you for any repsone!

:)

 

Sigverif reports system files not signed

Sigverif reports that msvcp110.dll and vcruntime140.dll are not signed.

I have run sfc /scannow to no avail. I performed a takeown on both files but got the following error when I attempted to regsvr32:

---------------------------

RegSvr32

---------------------------

The module "vcruntime140.dll" was loaded but the entry-point DllRegisterServer was not found.

Make sure that "vcruntime140.dll" is a valid DLL or OCX file and then try again.

---------------------------

OK

---------------------------

Is either the fact that they are unsigned or the fact that I got the error upon attempting regsvr32 of any concern?

 

Sigverif reports system files not signed

Hi,

The issue may occur due to corrupted system files. In order for us to assist you, we suggest to check this article:

How to fix missing DLL files errors on Windows 10/8/7 PC. It contains troubleshooting steps pertaining the issue.

We look forward to your response.

 

False Positives: Drivers from working computer copied over still showing as "unsigned drivers" by sigverif

I tried installing an old game from the disc (Bet on Soldier). It said it would not work on my OS, only XP and 95, but I went ahead anyway.

After install it required a restart. It could not boot until I disabled driver signature enforcement.

I remembered a similar thing happened a while back when I tried to play the demo of the game, so I'm pretty sure the game's installer is making a bad change to a Windows file somewhere, probably with an out-of-date driver signature.

I ran sigverif and it found three unsigned drivers in c:\windows\system32\

msvcp110.dll

msvcr110.dll

vccorlib110.dll

However, the date modified for each of those files was not today, but several years ago (5/11/2012), so it seems unlikely. I followed all the procedures I could find on these forums:

1) I ran sfc /scannow. It repaired one file: mscormmc.dll. Edit: Also tried DISM /online /cleanup-image /checkhealth and it reported no corruption detected, and completed successfully:

Version 10.0.17763.1

Image Version: 10.0.17763.379

No component store corruption detected.

The operation completed successfully.

2) Downloaded Visual Studio Redistributable 2017 (Edit: Also tried with the 2012 version) and tried repairing, and tried uninstalling then installing again. Made no difference.

3) Copied the specific dll files from my partner's computer (also running up-to-date Windows 10) and using them to replace my versions of those three dll's. Still sigverif finds them to be unsigned. Ran sigverif on my partner's computer and it finds no signature
problems with any of her files.

This suggests to me that it has nothing to do with these three dll's, but is actually a reference problem - I think these dll's have the correct signature, and whatever signature database sigverif is checking against has been altered or corrupted and no longer
has the correct signatures in its database for these three dll's. Next I tried:

4) I ran cmd as admin, used takeown /f on each of the files, and tried "regsvr32 msvcp110.dll" for each of them, and received this error:

"The module "c:\windows\system32\msvcp110.dll" was loaded but the entry-point DllRegisterServer was not found.

Make sure that "C:\windows\system32\msvcp110.dll" is a valid DLL or OCX file and then try again."

5) Just to see what would happen, I deleted these three dll's and ran sigverif, and it still reported that these were unsigned, but now it listed their date modified as "Unknown" and their version as "None" in the dialog box. I tried deleting another random
dll from that directory to see if sigverif would show the same error whenever a dll was missing, but it didn't. It still only found a problem with those three dll's.

So where/how does sigverif or Windows check the driver signatures? Is there a local database on the computer?

I'm guessing it might have something to do with HKEY_LOCAL_MACHINE\Software\Microsoft\Driver Signing registry key. Is there a way I can get Windows to refresh/verify/update this?

Or any other ideas on how to solve this?