kirk781@discuss.tchncs.de to Technology@lemmy.worldEnglish · 29 days agoWhat I learned from 3 years of running Windows 11 on “unsupported” PCsarstechnica.comexternal-linkmessage-square209fedilinkarrow-up1364arrow-down112
arrow-up1352arrow-down1external-linkWhat I learned from 3 years of running Windows 11 on “unsupported” PCsarstechnica.comkirk781@discuss.tchncs.de to Technology@lemmy.worldEnglish · 29 days agomessage-square209fedilink
minus-square🇦🇺𝕄𝕦𝕟𝕥𝕖𝕕𝕔𝕣𝕠𝕔𝕕𝕚𝕝𝕖@lemm.eelinkfedilinkEnglisharrow-up1arrow-down15·28 days agoUd think people would learn after they all blue screened.
minus-squareSaltySalamander@fedia.iolinkfedilinkarrow-up2·28 days agoHaven’t had a blue screen in probably a decade.
minus-squarewizardbeard@lemmy.dbzer0.comlinkfedilinkEnglisharrow-up2·28 days agoIf you’re talking about crowdstrike… They didn’t all blue screen. That was caused by third party software that caused the same sort of issue (kernel crash/panic) on Linux boxes not even 3 months earlier.
minus-squareTonyTonyChopper@mander.xyzlinkfedilinkEnglisharrow-up1·28 days agoprobably the CrowdStrike bug. Which is 3rd party software
Ud think people would learn after they all blue screened.
Haven’t had a blue screen in probably a decade.
If you’re talking about crowdstrike… They didn’t all blue screen. That was caused by third party software that caused the same sort of issue (kernel crash/panic) on Linux boxes not even 3 months earlier.
What are you referring to here?
probably the CrowdStrike bug. Which is 3rd party software