This article will be the default article after the implementation of
the new Minimum Requirements for Code Signing on February 1, 2017.



  • /ac  –  Specify an Additional Certificate.
  • /a  –  Automatically selects the best certificate to sign the file from your Windows Certificate Store.
  • /fd SHA256  –  Specify the file digest algorithm used in creating file signatures.
  • /t  –  Specify a Microsoft Authenticode compatible time stamp server.
  • /tr  –  Specify an RFC 3161 compliant trusted time stamp server.*Recommended*
  • /td SHA256  –  Must be called after "/tr", this command specifies the TimeStamp digest Algorithm. *Recommended*
  • /sha1 Hash  – Used to select the signing certificate by the SHA-1 Hash (Thumbprint).                                 

Note: Timestamping your Code is extremely important and is highly recommended for every piece of code that you sign. 
This timestamp will allow the file that you sign to remain valid long after the certificate itself has expired.

TimeStamp URLs:

SHA1 based:
SHA2 based:


  • You can either sign files out of a working directory, or you can place them in your Windows SDK\bin folder.
  • Open the Command Prompt: Windows 7: Start > Run > cmd, or for Windows 8, press the Windows Key, then type cmd and press enter.
  • Navigate to the directory with signtool.exe.
  • Use the following command to sign your file: 
    signtool sign /a /tr /td SHA256 c:/path/to/your/file.exe

Note: For Kernel Driver Signing include the argument “/ac GlobalSign Root CS.crt” to the signtool command in order to complete the MS cross certificate chain.

  • Enter your Token Password. If the signing is successful you will see a prompt informing you so.
  • To verify the successful signature use the following commands:
    Authenticode: signtool verify /v /pa
    Kernel Driver Signing: signtool verify /v /kp

You may also verify the signature within the properties of the file, under the Digital Signatures tab.

Last Updated: Jan 30, 2017