Super User is a question and answer site for computer enthusiasts and power users. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

On running SigCheck on my Windows box, I noticed quite a few dlls that are unsigned. For eg:

        Verified:       Unsigned
        File date:      10:47 AM 9/14/2011
        Publisher:      Advanced Micro Devices Inc.
        Description:    AMD Accelerated Parallel Processing OpenCL 1.1 Runtime
        Product:        OpenCL 1.1 AMD-APP-SDK-v2.5 (732.1)
        Version:        2, 5, 732, 1
        File version:   2, 5, 732, 1
        Verified:       Unsigned
        File date:      10:38 AM 9/14/2011
        Publisher:      Advanced Micro Devices Inc.
        Description:    AMD COMPILER OpenCL 1.1 Compiler
        Product:        AMD Compiler Library 1.1 AMD-COMP-LIB-v0.7 (727.0)
        Version:        0, 7, 727, 0
        File version:   0, 7, 727, 0

But I downloaded the executables from the the official AMD website. Why wouldn't AMD sign their dlls? Are their any security issues I need to be worried about, considering the fact that these (among many others, including vendors like HP) are unsigned

share|improve this question
Any chance you've installed beta drivers? – ragnq Feb 4 '12 at 17:33
I doubt that. Let me double check anyway. – Lelouch Lamperouge Feb 4 '12 at 17:55
No, they are stable releases – Lelouch Lamperouge Feb 4 '12 at 17:55
up vote 5 down vote accepted

The effect is that you are using a driver that has not been authenticated by a third party as coming from the source it purports to be.

Getting drivers signed costs money and takes time to get, If the company is releasing drivers regularly they may not want to spend that money on signing the latest and greatest version every time.

From Microsoft's Driver Signing Requirements for Windows:

Digital signatures allow administrators and end users who are installing Windows-based software to know whether a legitimate publisher has provided the software package.

Generally, if you trust the source you got it from, there should be no concern.

share|improve this answer
AMD drivers are normally WHQL signed. – ragnq Feb 4 '12 at 20:24
@ragnq Agreed, but AMD was just the OP's example. – Ƭᴇcʜιᴇ007 Feb 4 '12 at 21:42
@techie007, like you said I just showed AMD examples. But there a so many dlls by HP, that haven't been updated in a long time and are still unsigned. I'd expect HP to take that more seriously. – Lelouch Lamperouge Feb 5 '12 at 16:04

this may mean the dlls might have been altered, but it is normally no effect except if it is a malware. example, game installers copy their versions of a dll instead of the system default dll so the dll is unsigned. or if you edit a dll. or a system restore by using other engine than the system restore tool in windows. there are plenty of cases, but with a good protection don't worry.

share|improve this answer

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .