[deleted]
Luckily, the patch won’t install for me, because the default size of the recovery partition is too low.
[deleted]
Submitted 6 months ago by MasterPain@lemmy.world to technology@lemmy.world
Comments
deafboy@lemmy.world 6 months ago
AcesFullOfKings@feddit.uk 6 months ago
[deleted]possiblylinux127@lemmy.zip 6 months ago
Luckily, the update won’t install for me, as I run Linux
Legend@lemmy.sdf.org 6 months ago
Completely coincidental eh ?
downpunxx@fedia.io 6 months ago
I keep reading about this supposed VPN breakage, but haven't read a single comment where a Windows users has had their VPN connections break, nor a listing of the VPN clients/protocols that are supposedly affected by this security update, which is curious now several days out from this "news" coming to the surface.
IHawkMike@lemmy.world 6 months ago
Exactly. Everybody on Lemmy a couple days ago was acting like the sky was falling when all we had were these one-paragraph FUD articles quoting Microsoft’s own KB article. Most people commenting have no clue that “VPN” is a broad term covering at least a dozen different possible protocols and acted like Microsoft was intentionally breaking all VPNs.
The only thing I found was a reddit thread talking about how some VPNs using TPM-backed certs were broken. I, for one, am using an IPsec VPN with certs stored in TPM on one of the affected versions of Windows 11 and have had no problems. Nor have I had any issues with SSL or Wireguard-based VPNs, so it does just seem to be a fringe case they’re warning about.
So Microsoft is just giving a heads-up that IT should probably include VPN testing in their patch cycle test rings and all the anti-MS people are losing their shit.
CarbonatedPastaSauce@lemmy.world 6 months ago
This confusion is Microsoft’s fault because they’re being incredibly vague about the whole thing. Of course people are going to freak out when the only thing they have to go on is “Windows devices might face VPN connection failures” which is less than useless information. They might as well have said “Between 0 and 100 percent of your remote users may suddenly be unable to work for reasons we can’t or won’t tell you”
Which protocols are affected? In what circumstances? Is this specific to certain software or hardware? WHAT DID YOU FIND? TALK TO US. etc etc
But Microsoft’s documentation has been in a death spiral for a decade now and it’s just going to keep getting worse. We bitch at our account manager regularly about all the problems we find with it.