The Circular certificate dependencies in the endpoint's certificate store need to be fixed to resolve the issue. The specific remediation will depend on the environment. However, here are the actions to follow and fix the certificates with Circular dependencies:

• Identify the redundant certificates that creates the cycle from the Intermediate Certification Authorities store as explained in the next section
• Export those certificates for backup and then delete them from the Certificate store
• Get the certificates with correctly chained versions from your CA administrator
• Re-enroll the endpoint to obtain a clean certificate chain

To identify the circular dependency on an end-point, follow the steps below:

• On the affected endpoint, open the Windows Certificate Manager (certlm.msc for the local machine store and certmgr.msc for the current user store)
• Navigate to Intermediate Certification Authorities > Certificates for both Local Machine and User store separately
• Look for intermediate certificates where:
  • Certificate A's Authority Key Identifier (AKI) points to Certificate B
  • Certificate B's AKI points back to Certificate A
  • Below is the screenshot of such an example where both intermediates issue each other. This can be checked by comparing each SKID against the others AKID. In addition, the subject and issuer names show that they issued each other as well.
  • 
• Ensure the corrected chain follows a valid hierarchical path from leaf through intermediates to root

To verify the certificate chain of the certificates with Circular dependenices, use the below command line:

• certutil -verify -urlfetch <certificate_file>

Review the output for any loops or repeated issuers in the chain. Once the circular dependency is resolved, VDI sessions will launch normally.

Workaround:

If certificate remediation cannot be performed immediately, use Workspace for Web (HTML5) to launch sessions, as it does not perform client-side pre-handshake certificate validation.