Trusted Root Certification Authorities Certificate Store
The Plug and Play (PnP) manager performs driver signature verification during device and driver installation. Verification succeeds when:
A certification authority (CA) issued the signing certificate used to create the signature.
The corresponding root certificate for the CA is installed in the Trusted Root Certification Authorities certificate store. Therefore, the Trusted Root Certification Authorities certificate store contains the root certificates of all CAs that Windows trusts.
To access the Trusted Root Certification Authorities certificate store on a Windows computer, you can use the Microsoft Management Console (MMC) with the Certificates snap-in. Here are the steps for a Windows 10 or later computer:
Open the Windows Run dialog: Press Windows key + R to open the Run dialog.
Open the Microsoft Management Console (MMC): Type
mmc
into the Run dialog and press Enter. This command opens the Microsoft Management Console. If prompted by User Account Control (UAC), select Yes to allow the MMC to make changes to your device.Add the certificates snap-in:
- In the MMC window, select File in the menu bar and select Add/Remove Snap-in.
- In the Add or Remove Snap-ins window, scroll down, and select Certificates, then select Add >.
- A pop-up asks which certificates you want to manage. Select Computer account, then select Next.
- Select Local computer: (the computer this console is running on), then select Finish.
- You can also choose My user account or Service account depending on your needs, but for accessing the Trusted Root Certification Authorities, choose Computer account.
- Select OK to close the Add or Remove Snap-ins window.
Access the Trusted Root Certification Authorities:
- In the MMC, under the Certificates (Local Computer) tree, expand the Trusted Root Certification Authorities folder.
- Select Certificates under the Trusted Root Certification Authorities. See all the certificates currently trusted by the computer.
Manage Certificates:
- From here, you can view details of each certificate, import new trusted certificates, or remove existing ones. However, be cautious when adding or removing certificates as it can affect the security and functionality of your system.
Close MMC:
- When you're done, you can close the MMC window. If you made changes and it asks if you want to save the console settings, choose No unless you plan on reusing this console setup frequently.
Remember, managing certificates and the Trusted Root Certification Authorities store should be done carefully and typically requires administrator privileges. Improper changes can compromise the security of your system.
By default, the Trusted Root Certification Authorities certificate store is configured with a set of public CAs that meet the requirements of the Microsoft Root Certificate Program. Administrators can configure the default set of trusted CAs and install their own private CA for verifying software.
Note
A private CA is unlikely to be trusted outside the network environment.
Having a valid digital signature ensures the authenticity and integrity of a driver package. However, it doesn't mean that the end-user or a system administrator implicitly trusts the software publisher. A user or administrator must decide whether to install or run an application on a case-by-case basis, based on their knowledge of the software publisher and application. By default, a publisher is trusted only if its certificate is installed in the Trusted Publishers certificate store.
The name of the Trusted Root Certification Authorities certificate store is root. You can manually install the root certificate of a private CA into the Trusted Root Certification Authorities certificate store on a computer by using the CertMgr tool.
Note
The driver signing verification policy that is used by the PnP manager requires that the root certificate of a private CA has been previously installed in the local machine version of the Root Certification Authorities certificate store. For more information, see Local Machine and Current User Certificate Stores.
For more information about driver signing, see Driver Signing Policy.