Reset Windows Certificate Management Store on 21H1?

  • Be sure to checkout “Tips & Tricks”
    Dear Guest Visitor → Once you register and log-in please checkout the “Tips & Tricks” page for some very handy tips!

    /Steve.
  • BootAble – FreeDOS boot testing freeware

    To obtain direct, low-level access to a system's mass storage drives, SpinRite runs under a GRC-customized version of FreeDOS which has been modified to add compatibility with all file systems. In order to run SpinRite it must first be possible to boot FreeDOS.

    GRC's “BootAble” freeware allows anyone to easily create BIOS-bootable media in order to workout and confirm the details of getting a machine to boot FreeDOS through a BIOS. Once the means of doing that has been determined, the media created by SpinRite can be booted and run in the same way.

    The participants here, who have taken the time to share their knowledge and experience, their successes and some frustrations with booting their computers into FreeDOS, have created a valuable knowledgebase which will benefit everyone who follows.

    You may click on the image to the right to obtain your own copy of BootAble. Then use the knowledge and experience documented here to boot your computer(s) into FreeDOS. And please do not hesitate to ask questions – nowhere else can better answers be found.

    (You may permanently close this reminder with the 'X' in the upper right.)

Intuit

Well-known member
Dec 27, 2020
80
21
Ran CertMgr.MsC on 21H1. Did Microsoft widdle down the number of 3rd-Party Certs? Seems like that used to be quite a sprawling list there.

There are quick commands for resetting the Windows network stack, firewall settings. Is there a quick way to reset the Certificate Management Store while validating locally installed certs?

Thanks.

======================
Win7 / 21H1 Update Experience
======================
Recently updated an old Win7 Athlon X2 3GB nVidia chipset system with 8GB RAM, SSD, AMD PCI Video Card, Win10 21H1.
Contrary to past updates, the Guest account was left active.
I went ahead and deactivated the account anyway, replacing it with a "Visitor" account instead.
The update otherwise was flawless and the system runs surprisingly well, quick.

Anyway, removing/updating some old programs AutoRuns64 wasn't identifying many of the legitimately signed Windows binaries.

So I decided to checkout the certificate store.

CertMgr.MsC
SigCheck -tu
SigCheck -tuv

No extraneous certs appear to be present. Just the normal default certs with exception to some OEM certs. I don't intend on going through the trouble of verifying whether or not some default certs are missing.