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.
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?
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”.
What changed? Likely your VPN doesn’t work now. Lol
Which VPN were you using that stopped working after a windows update?
Or did you just read a headline and not bother to look into it any further?
For reference, they literally just broke VPNs for many people and corporations are now having to roll back updates for their staff
https://www.bleepingcomputer.com/news/microsoft/microsoft-says-april-windows-updates-break-vpn-connections/
No, you’re just making shit up and saying it as if it were fact.
Can you provide a source that it affected “many people and corporations”? If there are so many, it should be easy to name one.
Mate, you dumb? The link cites Microsoft KB. This issue is officially reported BY Microsoft, not by some random people online.
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.
What do you mean no one uses it? You seriously that dumb?
I am seriously that dumb. Can you give me an example of someone who used it and was affected by this?
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.
Isn’t it weird that you, also, can’t name a single person who was affected by this?
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?
I hope you weren’t just lying to my face.
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.
Yeah, none of those are affecting me right now. I don’t think they’re affecting you, either.
Holy fuck ignore my other comment. “Yeah your reality sounds different from mine, you’re wrong.” You’re just a stunted mind, no longer interesting.
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”.