Certificate not trusted

Unai Semeone 0 Reputation points
2026-11-16T16:03:36.12+00:00

The Windows Server is experiencing an SSL/TLS certificate trust issue. When users or client applications attempt to establish a secure connection to the server, the certificate is not recognized as trusted.

Windows for business | Windows 365 Enterprise
0 comments No comments

2 answers

Sort by: Most helpful
  1. Marcin Policht 113.3K Reputation points MVP Volunteer Moderator
    2026-11-16T16:19:04.5266667+00:00

    An SSL/TLS certificate trust issue on Windows Server generally indicates that the client cannot establish a trusted certificate chain between the server's SSL/TLS certificate and a trusted root certification authority (CA). This can occur when the server certificate is self-signed, has expired, is missing an intermediate certificate, or was issued by an internal CA whose root certificate is not trusted by the client.

    Start by examining the certificate installed on the Windows Server. Use the Certificates MMC snap-in (certlm.msc) and inspect Personal > Certificates under the Local Computer account. Verify that the certificate is within its validity period, has an associated private key, and includes the appropriate Server Authentication Enhanced Key Usage (EKU). Also verify that the certificate's Subject Alternative Name (SAN) includes the DNS name clients use to connect to the server.

    Next, verify the certificate chain. Open the certificate and examine the Certification Path tab. Windows should be able to build a complete chain from the server certificate through any intermediate CA certificates to a trusted root CA. If the chain is incomplete, install the missing intermediate certificates in the Local Computer's Intermediate Certification Authorities store. If the issuing root CA is internal, distribute its root certificate to client computers and install it in Trusted Root Certification Authorities.

    You can use PowerShell to examine the certificate stores and verify certificate details. For example:

    Get-ChildItem Cert:\LocalMachine\My |
        Select-Object Subject, Issuer, NotBefore, NotAfter, Thumbprint
    

    You can also use the Windows certificate verification utility:

    certutil -verify server.cer
    

    Finally, verify that the application or service is actually presenting the intended certificate. IIS, RDP, LDAPS, and other services can have separate certificate bindings or configuration requirements. For IIS, inspect the HTTPS binding in IIS Manager and confirm that the correct certificate is selected. For LDAPS, verify that the certificate meets the domain controller's requirements and is available in the appropriate computer certificate store.

    Keep in mind that installing a certificate on the server alone does not establish trust. The client must trust the certificate's issuing CA, and the certificate must be valid for the server name being accessed.


    If the above response helps answer your question, remember to "Accept Answer" so that others in the community facing similar issues can easily find the solution. Your contribution is highly appreciated.

    hth

    Marcin

    Was this answer helpful?

    0 comments No comments

  2. AI answer

    2026-11-16T16:05:25.17+00:00

    Identify the certificate actually presented by the affected endpoint and validate its chain before adding anything to the clients’ trusted-root store.

    1. Capture the affected endpoint and presented certificate

    On one affected domain-joined client:

    1. Record the exact DNS name and port being accessed, such as server.contoso.com:443.
    2. Open the certificate from the client application or browser and record:
      • Subject
      • Issuer
      • Thumbprint
      • Valid from/to
      • Subject Alternative Name (SAN)
      • Certification Path status
    3. Confirm that the DNS name used by the client appears in the SAN.

    A trusted chain must lead to a trusted root, with every certificate correctly signed, unexpired, unrevoked, and compliant with the issuing CA’s policies.^1^

    The path status distinguishes common cases:

    • Untrusted root/CA: the root CA is absent or deliberately untrusted.
    • Incomplete chain: an intermediate CA certificate is missing.
    • Expired certificate: replace the expired server, intermediate, or root certificate.
    • Name mismatch: reissue the server certificate with the accessed DNS name in its SAN.
    • Revocation failure: verify access to the CRL or OCSP locations encoded in the certificate.

    Do not install the server certificate itself as a trusted root; an incorrect trusted-root change weakens security for the entire computer.^2^

    2. Determine which service presents it

    If the connection uses HTTPS or another HTTP.sys-hosted service, run this elevated on the server:

    netsh http show sslcert
    
    Get-ChildItem Cert:\LocalMachine\My |
        Select-Object Subject, Issuer, Thumbprint, NotAfter,
                      HasPrivateKey
    

    Match the binding’s Certificate Hash to the certificate thumbprint. netsh http show sslcert displays the SSL certificate associated with each IP address and port.^3^

    For IIS:

    1. Open IIS Manager.
    2. Select Sites → the relevant site → Bindings.
    3. Edit the https binding.
    4. Compare its selected certificate with the certificate observed on the client.

    IIS 7 and later also store SSL binding information in HTTP.sys, so both the IIS binding and HTTP.sys certificate hash/store must be correct.^4^

    If no matching HTTP.sys binding exists, identify the process listening on the affected port and inspect that product’s TLS configuration. The available information does not establish whether this is IIS, LDAPS, Remote Desktop, SQL Server, or another service.

    3. Validate the server certificate and chain

    On the server, run certlm.msc, then inspect:

    • Personal → Certificates for the server certificate.
    • Intermediate Certification Authorities → Certificates for intermediates.
    • Trusted Root Certification Authorities → Certificates for the root.

    Open the server certificate and check Certification Path, SAN, validity dates, Server Authentication usage, and whether the certificate has its private key. Windows documents certlm.msc as the Local Computer store and provides read-only PowerShell inspection for these properties.^2^

    If the presented certificate has been exported as server.cer, validate it from an approved troubleshooting environment:

    certutil -urlfetch -verify .\server.cer
    

    This checks the certificate while retrieving its embedded validation URLs; those URLs can generate outbound traffic.^2^

    Also review Event Viewer → Windows Logs → System for Schannel errors at the time of a failed connection.

    4. Distribute an internal CA only when the chain proves it is missing

    If the certificate was issued by your organization’s internal CA and the affected clients lack that approved root or intermediate certificate:

    1. Verify the CA certificate’s issuer and thumbprint with the PKI administrator.
    2. Open Group Policy Management on a domain controller or RSAT management device.
    3. Create or edit a GPO linked to the affected clients’ domain, site, or OU.
    4. Navigate to:
      Computer Configuration → Policies → Windows Settings → Security Settings → Public Key Policies
    5. Import:
      • The root CA into Trusted Root Certification Authorities.
      • Any intermediate CA into its appropriate intermediate store.
    6. On a test client, run:
    gpupdate /force
    
    1. Reopen certlm.msc and confirm that the expected CA thumbprints appear, then retest the connection.

    Group Policy is the supported domain mechanism for distributing certificates to Windows devices.^5^ Domain or Enterprise administrative permissions, or equivalent delegated permissions, are required.^6^

    If this is a publicly issued certificate instead, do not deploy an internal trust override. Check whether the clients can receive Microsoft certificate trust list updates; Windows normally updates trusted and untrusted CTLs automatically, and disabling that mechanism is not recommended.^7^


    References

    1. Certificate Chain
    2. Inspect certificates and manage certificate store contents
    3. Netsh http commands
    4. How to Set Up SSL on IIS 7 or later
    5. Distribute certificates to Windows devices by using Group Policy
    6. Distribute Certificates to Client Computers by Using Group Policy
    7. Certificates and trust in Windows
    AI-generated content may be incorrect. Read our transparency notes for more information.

    Was this answer helpful?

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.