You didn't answer me, so I'll give you another chance. You must've missed my question last time. Which VPN were you using which stopped working after a windows update?
Yeah, but you didn't bother to actually follow the link or read what it says. There was a bug in Microsoft's VPN implementation (which no one uses) which affected no one, until they fixed it.
Disregarding the topic and focusing on semantics for half a second out of pure (and weekend freedom stoned) curiosity, why do you value the anecdotal experience of others--and seemingly in one direction only?
My Cousin Vinny's Tomato Canning and Money Laundering Inc, ran by my cousin Vinny and his family of hard looking unrelated men lost VPN access after the last Microsoft update. I'm lying, BUT let's pretend I'm not, what's your next weird hill, I'm curious.
Well, I used to use it back in the days. Many VPN providers like NordVPN use IKEv2. Older corporate deployments of Cisco VPN use IPSEC. Should I continue?
Tinc gets broken by Windows updates every once in a while. The problem is that the update sometimes renames the network connections and Tinc needs the connection to have a specific name to work.
That's the one I personally ran into several times now.
Given that I literally said I personally encountered this problem: Yes, it does. It's mostly just an annoyance that goes straight onto the "Windows Update jank" pile but I have wasted quite a bit of time helping people deal with connectivity issues that could down to "tinc_vpn" getting automatically renamed to "Network Connection 7".