SagXD@lemm.ee to Microblog Memes@lemmy.worldEnglish · 2 months agoFirst and Last daylemm.eeimagemessage-square26fedilinkarrow-up1368arrow-down111
arrow-up1357arrow-down1imageFirst and Last daylemm.eeSagXD@lemm.ee to Microblog Memes@lemmy.worldEnglish · 2 months agomessage-square26fedilink
minus-squarePennomi@lemmy.worldlinkfedilinkEnglisharrow-up17·2 months agoOr if they were smart enough to do a phased rollout to a small percentage of users before deploying worldwide. That catches most issues quickly.
minus-squareJustin@lemmy.jlh.namelinkfedilinkEnglisharrow-up5·2 months agoOr if Microsoft reviewed drivers before signing them.
minus-squareKmlSlmk64@lemmy.worldlinkfedilinkEnglisharrow-up4·2 months agoI think they do (or at least I’ve seen it mentioned), but this wa apparently caused a by a bad configuration fil for that driver. (A 40-something kB file pf pure zeroes)
minus-squareKillingTimeItself@lemmy.dbzer0.comlinkfedilinkEnglisharrow-up4·2 months agoor like, tested the fucking update at all…
Or if they were smart enough to do a phased rollout to a small percentage of users before deploying worldwide. That catches most issues quickly.
Or if Microsoft reviewed drivers before signing them.
I think they do (or at least I’ve seen it mentioned), but this wa apparently caused a by a bad configuration fil for that driver. (A 40-something kB file pf pure zeroes)
or like, tested the fucking update at all…