Yeah, you’re not wrong that the article kinda sets itself up for the “lookit our recommended VPNs” pitch.
There’s no way Microsoft would purposefully disable VPNs from working. I can guarantee that they require VPNs for thousands of roles in the company, let alone breaking it for government agencies that require VPNs, etc.
It is good to know that a specific update can break something ahead of time, though. Then at least you can avoid it.
Yeah, you’re not wrong that the article kinda sets itself up for the “lookit our recommended VPNs” pitch.
There’s no way Microsoft would purposefully disable VPNs from working. I can guarantee that they require VPNs for thousands of roles in the company, let alone breaking it for government agencies that require VPNs, etc.
It is good to know that a specific update can break something ahead of time, though. Then at least you can avoid it.
No, but they’ve done it accidentally before.
One time a few years ago it broke all LT2P VPN’s unless you removed a specific KB########.
IIRC, six months later there was still no fix.
I think it’s been fixed now, though.