Over the time I have installed several additional trusted CA certificates to Windows trust store, sometimes because an app pushed me to do so, some other times for development and testing.

Is there any command to restore the default (or currently MS recommended) trusted CA certificates and delete any other entries?

  • I'm voting to close this question as off-topic because it should have been migrated to SuperUser at the time. – schroeder Dec 1 at 21:41
  • It is probably the number one fundamental thing necessary for windows security. – Tyler Dec 1 at 22:11
  • @Tyler no it's not. I can think of a dozen more fundamental things. And this is a Windows command question, not a security question. This really does belong on SuperUser. – schroeder Dec 1 at 22:12

Theoretically, you could apply the following method:

  1. Delete all root CA certificates except the ones that are absolutely needed by Windows itself, as indicated here.

  2. Install the current list of trusted root CA from the current package. Note that validation of this package requires that you still trust one of the "necessary" root CA, which is why you must keep them in the first step.

I emphasize that I have not tested this method. As a preparatory step, you may want to first make a backup of all these certificates: run certmgr.msc, open the Root store, select them all (e.g. with Ctrl-A), then right-click and choose to export them all as a PKCS#7 file. That file will contain a copy of all the certificates, which should allow you to repair things, if the method above fails in some way. There again, the recovery is untested.

Be wary of the multiplicity of stores. certmgr.msc shows an aggregate view containing certificates from various sources ("physical stores"). To understand what you are about to do, in the certificate manager, right-click on the Certificates node (root node of the tree in the left pane), select View then Options, and select the Physical certificate stores box. This process is described in this blog entry (with screenshots).

  • 2
    So there's no automated version that doesn't risk making Windows unusable? – Nzall Feb 23 '15 at 17:36
  • There should be, but there isn't. The second link ("current package") is redirected now. – Xan-Kun Clark-Davis May 21 '17 at 12:25
  • Do you know what would be the correct way to request this feature to MS?. – Jaime Hablutzel Aug 22 at 17:37

I found the following simple method to remove the locally trusted CA certificates not present in the official and current Microsoft Certificate Trust List:

First download Sigcheck (https://docs.microsoft.com/en-us/sysinternals/downloads/sigcheck) and then execute:

>sigcheck.exe -tuv
Listing valid certificates not rooted to the Microsoft Certificate Trust List:

   Test Purpose CA
        Cert Status:    Valid
        Valid Usage:    All
        Cert Issuer:    Some development Root CA
        Serial Number:  01
        Thumbprint:     9CB31B0AE15867B5E29C4F7E21FE195C2AF24FE3
        Algorithm:      sha1RSA
        Valid from:     2:10 PM 2/5/2015
        Valid to:       2:10 PM 2/5/2025
   LLAMA.PE Root CA - R2
        Cert Status:    Valid
        Valid Usage:    All
        Cert Issuer:    Some third party Root CA
        Serial Number:  01 E0 DA 86 CC 7D 58 ED D8 62 E6 47 A2
        Thumbprint:     1B4AEFF4FB8E2BEFEB3A8FE60D03D24269AB4A6B
        Algorithm:      sha256RSA
        Valid from:     7:00 PM 3/14/2017
        Valid to:       7:00 PM 3/14/2037

Then simply delete all the displayed CAs with something like certmgr.msc.


  • This method will only help to delete locally trusted CA certificates that don't exist in the Microsoft Certificate Trust List, but it won't install the Microsoft Certificate Trust List CAs not currently installed in the local store (e.g. the manually removed ones).
  • This checks the current user store, not the machine store. For checking the machine store, just omit the u in the arguments.
  • The output seems to include only valid certificates, e.g. I've observed that a locally trusted CA with a signature that Windows was unable to validate wasn't listed and I had to check it and remove it manually.

Credits to the following site, http://woshub.com/how-to-check-trusted-root-certification-authorities-for-suspicious-certs/.

  1. Create a VirtualBox VM or download a pre-made VM by microsoft (note it will include a few extra certs for code signing and visual studio)
  2. Install Windows 10 here is a wrapper that uses the official Windows 10 Media Creation Tool, but it will include enterprise releases and serials pre-activating your ISO
  3. Load mmc.msc
  4. Add certificates snap-in
  5. Choose "computer"
  6. Note the certificates listed
  7. Export what you are missing and copy them to your main PC

You may also delete every cert on your primary PC that you don't see in Windows 10 VM to reduce attack surface. Just be sure to back them up in case of future issues. I never had any issue.

This worked better for me than any other method listed above, as I had a lot of illegitimate and distrusted certs in my trusted certificate list thanks to the Rootsupd.exe utility tutorial here. No bad cert detection tool, anti-virus or security software detected them. Thus I removed over 300 Trusted Root certs from my Windows 10 installation and have only 36 left without any issue. I did this because each certificate, even legit ones, add a potential security hazard.

Importing the entire list is not resetting to default, and is a potential security hazard, however if you want to import the entire list as suggested by the MOD here, over 400 certs, download the list from windows update:

In Powershell/CMD Run certutil.exe -generateSSTFromWU roots.sst

Then In Powershell:

$sstStore = ( Get-ChildItem -Path C:\ps\rootsupd\roots.sst )
$sstStore | Import-Certificate -CertStoreLocation Cert:\LocalMachine\Root


Import certs from Windows Update using just powershell:

certutil.exe -generateSSTFromWU roots.sst
$sst = ( Get-ChildItem -Path C:\certs\roots.sst )
$sst = ( Get-ChildItem roots.sst )
$sst| Import-Certificate -CertStoreLocation Cert:\LocalMachine\Root
  • AV would not "detect" added certs – schroeder Dec 1 at 21:36
  • Wouldn't it be easier, faster, and more up-to-date to look up the current list and use that? docs.microsoft.com/en-us/security/trusted-root/… – schroeder Dec 1 at 21:40
  • I did not want 300-400 certs on my system that I imported using certutil. Each one adds, potentially, a security hazard. I wanted the default that came with windows. – Tyler Dec 1 at 21:44
  • Plus importing from windows update or that entire list is not resetting the list to default, as the user has requested. – Tyler Dec 1 at 22:10
  • But you could identify certs not on that list and remove them. – schroeder Dec 1 at 22:11

Not the answer you're looking for? Browse other questions tagged or ask your own question.