Have you ever encountered the error message “Failed to verify the Authenticode signature of the filename” while working with SQL Server? If so, you’re not alone. In this blog post, we will explore this interesting error and discuss how to resolve it.

When it comes to ensuring the security and integrity of our systems, it’s crucial to be aware of any potential malware or unauthorized changes. Unfortunately, sometimes it can be challenging to track down and identify these issues. In some cases, the only solution may be to format and rebuild the operating system to eliminate any potential compromises.

One particular error that SQL Server users may encounter is the “Failed to verify the Authenticode signature” error. This error message typically appears in the SQL Server ERRORLOG shortly after startup, and it indicates that the Authenticode signature of certain SQL Server files could not be verified.

Here is an example of the complete error message:

2018-07-31 16:58:45.56 Server Failed to verify the Authenticode signature of 'C:\Program Files\Microsoft SQL Server\MSSQL14.MSSQLSERVER\MSSQL\Binn\sqlservr.exe'. Signature verification of SQL Server DLLs will be skipped. Genuine copies of SQL Server are signed. Failure to verify the Authenticode signature might indicate that this is not an authentic release of SQL Server. Install a genuine copy of SQL Server or contact customer support.

The same error message may also appear for other SQL Server files, such as SQLOS.dll, sqlmin.dll, sqllang.dll, and more.

So, how can we resolve this issue? One possible solution is to check the trust of the DLLs and ensure that they are properly registered. To do this, we can follow these steps:

1. First, gather information about the server’s history. In some cases, this error may occur on a brand-new installation of SQL Server.
2. Search the internet for methods to check the trust of a DLL. You may come across helpful articles and resources.
3. Use a tool like Process Monitor to capture and analyze the system’s activities. Search for the specific Authenticode signature, such as “00AAC56B-CD44-11d0-8CC2-00C04FC295EE”.
4. If you find that a specific registry key is missing, such as “HKLM\Software\Microsoft\Cryptography\Providers\Trust\Certificate\{00AAC56B-CD44-11D0-8CC2-00C04FC295EE}”, you can proceed to the next step.
5. Register the Wintrust.dll file using the following command: regsvr32 C:\Windows\System32\wintrust.dll
6. Restart the SQL Server service.

After following these steps, you should no longer see the “Failed to verify the Authenticode signature” error in the SQL Server ERRORLOG.

It’s important to note that this error typically occurs when the Authenticode signature of SQL Server files cannot be verified. Genuine copies of SQL Server are signed, so failure to verify the signature may indicate that the installation is not authentic. If you encounter this error, it’s recommended to install a genuine copy of SQL Server or contact customer support for further assistance.

By understanding and resolving the “Failed to verify the Authenticode signature” error, you can ensure the security and authenticity of your SQL Server installation. Remember to regularly update and maintain your system to prevent any potential compromises.

Thank you for reading this blog post. We hope you found it informative and helpful. If you have any questions or comments, please feel free to reach out to us.