Unable To Find Required Root Certificates Exclusive [new]: Kepware The Installer Was

At its core, a root certificate is the ultimate anchor of trust in the public key infrastructure (PKI). Issued by a trusted Certificate Authority (CA) such as DigiCert, GlobalSign, or Let’s Encrypt, the root certificate is self-signed and stored in a protected “Trusted Root Certification Authorities” store within the operating system. When Kepware—or any modern application—attempts to establish a secure HTTPS connection for licensing, updates, or IoT Gateway communication, it checks the server’s certificate against this local root store. If the chain of trust leads back to a missing or untrusted root, the connection fails. The word “exclusive” in the error message is particularly telling: it implies that the installer is looking for a specific , non-generic root certificate, likely tied to Kepware’s code-signing or a proprietary communication component (such as the ThingWorx or IoT Gateway add-on). Without that precise root, the installer refuses to proceed, prioritizing security over functionality.

Remember: In the OT world, security and connectivity must coexist. Maintaining a healthy root certificate store is not just about installing Kepware—it is about ensuring the integrity of your entire industrial control system. At its core, a root certificate is the

When running the or PTC Kepware products installer, the error message "The Installer was unable to find required root certificates" typically occurs because the host operating system lacks up-to-date certificate authorities required to verify the installer's digital signature . This is common on legacy systems like Windows 7 or servers that have been offline and missed critical Windows Updates . Core Reasons for Failure If the chain of trust leads back to

For air-gapped systems, you must manually export certificates from an internet-connected machine and import them. Remember: In the OT world, security and connectivity

: