Test certificates

Test certificates should not be created by commercial certificate authorities, and are therefore not recognized by operating systems and browsers.

This is a good thing, because you don't want your test-signing process to be as sensitive as your release-signing process. After all, a mistakenly or even maliciously signed binary should not affect your users and customers.

Test certificate strategies

There are several strategies for creating and rolling out test certificates.

Strategy Description

Manual installation of self-signed certificates


  • Create a self-signed certificate in SignPath
  • Install it on every computer used for testing and development (manually or using a script)


  • No set-up required


  • Distribution mechanism not secure (users can be tricked into installing any certificate)

  • Manual effort (once on every computer)

  • Cannot revoke certificate in case of abuse

Automatic installation of self-signed certificates


  • Create a self-signed certificate in SignPath
  • Install it on all or selected computers using auto-enrollment
  • In case of serious incidents, disable these GPOs and add the certificate to computers Untrusted Certificates list


  • Central control via GPOs
  • Can use existing Active Directory groups and OUs for selection when using auto-enrollment


  • Some configuration effort, especially if the certificate is to be trusted only on selected computers

  • Cannot revoke certificate in case of abuse (but you can follow the incident process above)

Issue certificate from an in-house CA


  • Create a certificate signing request (CSR) in SignPath
  • Depending on your permissions,
    • send the CSR to your PKI team, or
    • use your in-house CA (e.g. Microsoft Active Directory Certificate Services or OpenSSL) to issue the certificate
  • Import the signed certificate in SignPath


  • Central control via PKI
  • Straight-forward revocation process


  • Cannot easily limit certificate roll-out to specific computers, business unites etc.

Certificate installation

Certificate store selection

You should generally add self-signed test certificates to the Trusted Root Certification Authorities certificate store of computers you use for testing your software. If you do this, Windows will treat your test certificates as if they were issued by a trusted Root CA.

Information Trusted Publishers

You may also add your test certificates to the Trusted Publishers store on internal machines. This is what happens when a user choses always trust this publisher during installation, and therefore results in the same behavior, so don't do this if you want to replicate the default behavior on user machines. Adding a certificate to this store will affect User Account Control (UAC) device driver installation prompts as well as whitelisting features such as Software Restriction Policies (SRP), AppLocker and WDAC Code Integrity Policies. (Only add your certificates to this store for computers in your own organization.)

Manual installation

  • Open the certificate in Windows Explorer
    • Certificate file: select Open.
    • Signed files: select Properties from the context menu, go to the Digital Signatures tab, open a signature (Details) and select View Certificate.
  • In the certificate property window, click Install Certificate...
  • Select Current User or Local Machine location
  • Select the Trusted Publishers store

Using scripts and batch files

  • In PowerShell scripts, use Import-Certificate <certificate-file> -CertStoreLocation Cert:LocalMachineRoot
  • In batch files, use CertUtil -addstore Root <certificate-file>

These commands require administrative permissions.


Use Group Policy Objects (GPOs) to add certificates to computers.

  • In order to trust a certificate, create a GPO for
    • Windows Settings
    • Security Settings
    • Public Key Policies/Trusted Root Certification Authorities
  • In order to explicitly un-trust a certificate, create a GPO for
    • Windows Settings
    • Security Settings
    • Public Key Policies/Untrusted Certificates

See also: Configure certificate auto-enrollment (Microsoft)