AD FS federation metadata update HTTP SSL handshake failure

Has anyone seen this behavior with AD FS and the trusted partner server? Successfully triggers the scheduled relying party metadata update task, resolves the external federation metadata URL via DNS, completes the initial network routing layer.

Windows Filtering Platform Event ID 5156 in the Security log confirms the outbound connection is permitted.

Initiates the TLS cipher suite negotiation, transmits the initial client hello packet, and maintains the active socket connection state but the metadata sync process never reaches the AD FS configuration database (the relying party trust fields remain empty)?