Microsoft retired TLS 1.0 and 1.1: What this means for Source-Connect 3.8
Important: Source-Connect 3.8 will no longer be able to connect after May 31, 2027. On that date, the service endpoint used by Source-Connect 3.8 will stop accepting the legacy TLS 1.0 protocol it requires.
Microsoft support for TLS 1.0 and TLS 1.1 ended on October 31, 2024. Microsoft has also begun disabling these legacy protocols by default in newer Windows releases.
This matters directly to Source-Connect 3.8. Source-Connect 3 is now a legacy product, and Source-Connect 4 became the current generation when it was released in March 2025. Source-Connect 3.8 depends on older TLS behavior that is no longer considered acceptable on modern Windows systems.
Why Source-Connect 3.8 is affected
Source-Connect 3.8 uses TLS 1.0 for secure communication. The service that supports this legacy connection will retire TLS 1.0 on May 31, 2027. At that point, Source-Connect 3.8 will no longer be able to establish a connection.
- After May 31, 2027, Source-Connect 3.8 will no longer connect because the required TLS 1.0 connection will be rejected.
- Even where it can still run, it depends on security technology that Microsoft and the wider industry have already retired.
- That makes Source-Connect 3.8 unsuitable for long-term production use on modern systems.
Why this is a security issue
TLS 1.0 and 1.1 have been deprecated for years because they no longer meet modern security expectations. Major platforms, vendors, and compliance-focused environments now expect TLS 1.2 or newer, with TLS 1.3 preferred wherever available.
For that reason, we cannot guarantee the security posture of a computer running Source-Connect 3.8 as part of an active workflow. We want users to be fully aware that running legacy software carries both compatibility risk and security risk.
Windows 10 and older Windows systems
Windows 10 Home, Pro, Enterprise, and Education reached end of support on October 14, 2025. These editions no longer receive regular security updates, except where an organization has a separate Extended Security Updates program or uses an edition with its own lifecycle, such as LTSC.
Windows 10 end of support is separate from the TLS 1.0 retirement. Keeping an older Windows system only to preserve Source-Connect 3.8 compatibility does not avoid the May 31, 2027 service deadline, and it can add another security risk: an unsupported operating system may no longer receive fixes for newly discovered vulnerabilities.
What this means for Source Elements services
Supporting a legacy product that depends on retired security protocols also requires older server-side systems to remain available. Those systems are separated from our modern platform, but they still add operational complexity and increase the chance of service interruptions.
In other words, this is not only about an old application on one workstation. It also affects the reliability of legacy infrastructure required to keep that application functioning.
Our recommendation: upgrade to Source-Connect 4
We highly recommend moving to Source-Connect 4. It is our current platform and the correct path forward for users who need a supported, modern, and secure remote recording workflow.
- Source-Connect 4 is the actively supported generation of Source-Connect.
- It is designed for current operating systems and modern security standards.
- It avoids dependence on TLS 1.0 and other legacy platform requirements.
What you should do next
- If you are still using Source-Connect 3.8, plan your upgrade as soon as possible.
- If Source-Connect 3.8 no longer opens on your Windows system, this is consistent with Microsoft's TLS retirement and default disablement of older protocols.
- Move to Source-Connect 4 for the best chance of continued compatibility, security, and support.
Upgrade options are available here: https://dashboard.source-elements.com/products/upgrades.
For assistance, please contact [email protected].