All devices running Windows 10 and Windows 7 are facing CTL/SSL problems following the update.
All devices running Windows 10 and Windows 7 are facing CTL/SSL problems following the update.
Hey everyone, I'm facing a tricky issue that's really frustrating. My plan is to reinstall Windows on all five PCs in the house, but that seems risky. There was a major update last Thursday, and now almost every machine can't connect to any HTTPS domains in any browser—even embedded ones. In Firefox it stalls with "Performing a TLS Handshake with...", while Chrome shows "Establishing a secure connection..." The Discord app works but can't join voice channels or make calls. Spotify appears online when I play music, but the album art disappears. Peer-to-peer apps like Deluge and Steam are fine, though the Steam store, embedded browser, and workshop don’t function. When I ping 8.8.8.8 or 1.1.1.1 it works, but the problems seem to vary in severity across all devices. This issue is described in a Microsoft blog post from their Directory Services Escalation Team (https://blogs.technet.microsoft.com/askd...tl-engine/). I've tried running regedit, renewing DNS, using automatic DNS, and even switching to Google or OpenDNS, but nothing helps. A NetAnalyzer scan showed some details, but I’m at a loss. My ISP has been in touch with their engineers, who can’t solve it either. I’ve reset the router twice—once factory and once with a new unit—but it’s still not working. I suspect the problem might be linked to an update in Windows security certification, which started right after the updates on all machines. Other OSes like Linux, Android, macOS, and even some smart TVs are fine. Any suggestions would be greatly appreciated. Thanks!
Is the DHCP service running on a different device than your ISP router? This might indicate a problem there. It could also stem from the network driver not accepting the update. Check if both are compatible.
The latest Windows update faces issues with CA authorizations. Turning on Credential Guard on your machine might fix the issue: https://social.technet.microsoft.com/For...rosecurity