LabVIEW HTTPS Client and Windows Certificate Store — Does the Client Reload Trust Anchors Mid-Session?

Integration Boundary

LabVIEW’s built-in HTTPS client on Windows delegates TLS certificate validation to WinHTTP, which consults the Windows system certificate store. The client also exposes a Certificate Store property that can override the system store with a custom CA list. The integration point between the LabVIEW runtime and the OS trust store is not fully specified regarding dynamic updates.

Goal and Uncertainty

Determine whether a long-running LabVIEW application (e.g., a headless service or continuous test executive) will automatically recognize a new root CA added to the Windows certificate store without restarting the LabVIEW process. The documentation does not state whether the HTTPS client caches the trust store at session start or re-queries it on each request.

Specific Questions

1. Does the HTTPS client reload the Windows certificate store automatically during an active session, or is a LabVIEW restart required?
2. If reloading occurs, is it triggered per-request, on a timer, or by a specific OS notification?
3. Does the behavior differ when the Certificate Store property is set to a custom CA file versus left at the default (system store)?