How to Trust a Certificate on Windows

Published: December 1, 2025 (Updated: Dec 1, 2025)

Enjoying this content? Subscribe to the Channel!

Stop Seeing HTTPS Errors! How to Trust Self-Signed Certificates on Windows

Welcome back to Darren’s Tech Tutorials!

If you work with development environments, testing servers, or internal applications, you’ve probably run into the dreaded “Your connection is not private” or “Certificate error” warning. This usually happens when the application is using a self-signed certificate.

While self-signed certificates are perfectly fine for internal use, Windows doesn’t inherently trust them because they haven’t been verified by a public Certificate Authority (CA).

In this practical guide, we’ll walk through the quick process of installing that certificate directly into your Windows Trusted Root Certificate Authorities store. Once done, those annoying security warnings disappear, and your browser will treat your self-signed certificate just like any public one!


⚠️ A Critical Safety Warning Before You Begin

The process below grants system-level trust to a certificate. You should only follow these steps if you are 100% sure of the certificate’s source. Trusting a malicious or unknown certificate can compromise your machine’s security.


Step 1: Preparation and Accessing the Certificate

To make system-level changes to the certificate store, we must use a browser capable of handling these installations and run it with administrative privileges. We will be using Internet Explorer (IE) for this specific task.

  1. Run Internet Explorer as Administrator: Find Internet Explorer in your start menu, right-click the icon, and select Run as administrator.
  2. Navigate to the Self-Signed URL: In the administrator IE window, navigate to the URL that is using the self-signed certificate (e.g., https://localhost:44344).
  3. Bypass the Security Warning: Because the certificate is not yet trusted, the browser will block the page and show a security warning. Click the link (usually labeled “Continue to this website (not recommended)” or similar) to view the page.
  4. View the Certificate Details: Once the page loads (or you see the broken lock icon/error bar), click on the certificate error icon or the address bar to view the details of the certificate that is causing the problem.
  5. In the Certificate window, click the Details tab, and then click the Copy to File… button to launch the Certificate Export Wizard.

Note: In newer versions of IE/Edge, you might access the certificate by clicking the red security warning in the address bar.

Step 2: Installing the Certificate on the Local Machine

The Certificate Export Wizard allows us to install the certificate into the system trust store rather than just exporting it.

  1. In the Certificate window, navigate to the General tab.
  2. Click the Install Certificate… button. This launches the Certificate Import Wizard.
  3. When prompted, select Local Machine as the Store Location.
    • Important: Selecting “Local Machine” ensures that the certificate is trusted system-wide, not just for the current user.
  4. Click Next.

Step 3: Choosing the Trusted Root Certificate Authorities Store

This is the most crucial step where you explicitly tell Windows to trust the source of this certificate.

  1. On the “Certificate Store” screen, select the radio button for Place all certificates in the following store.
  2. Click the Browse… button.
  3. Scroll down and select Trusted Root Certificate Authorities.
  4. Click OK.
  5. Verify that the selected store is now “Trusted Root Certificate Authorities,” and click Next.
  6. Click Finish.

You should receive a final pop-up confirmation stating: “The import was successful.”

Conclusion and Final Check

That’s it! You have successfully added your self-signed certificate to the Windows Trusted Root Certificate Authorities store.

To confirm the fix, close all browser windows and open a new one (it doesn’t have to be run as administrator this time). Navigate back to your HTTPS URL. You should now see the standard secure lock icon, and the irritating security warning should be completely gone.

This quick fix is essential for smooth development and testing. If this tutorial helped you get rid of those frustrating security pop-ups, please give the video a like and subscribe to Darren’s Tech Tutorials for more clear, practical guides! Happy coding!