kirk781@discuss.tchncs.de to Technology@lemmy.worldEnglish · 2 days agoWhat I learned from 3 years of running Windows 11 on “unsupported” PCsarstechnica.comexternal-linkmessage-square202fedilinkarrow-up1357arrow-down114
arrow-up1343arrow-down1external-linkWhat I learned from 3 years of running Windows 11 on “unsupported” PCsarstechnica.comkirk781@discuss.tchncs.de to Technology@lemmy.worldEnglish · 2 days agomessage-square202fedilink
minus-square🇦🇺𝕄𝕦𝕟𝕥𝕖𝕕𝕔𝕣𝕠𝕔𝕕𝕚𝕝𝕖@lemm.eelinkfedilinkEnglisharrow-up1arrow-down15·2 days agoUd think people would learn after they all blue screened.
minus-squarewizardbeard@lemmy.dbzer0.comlinkfedilinkEnglisharrow-up2·2 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-squareSaltySalamander@fedia.iolinkfedilinkarrow-up2·2 days agoHaven’t had a blue screen in probably a decade.
minus-squarestephen01king@lemmy.ziplinkfedilinkEnglisharrow-up1·2 days agoWhat are you referring to here?
minus-squareTonyTonyChopper@mander.xyzlinkfedilinkEnglisharrow-up1·2 days agoprobably the CrowdStrike bug. Which is 3rd party software
Ud think people would learn after they all blue screened.
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.
Haven’t had a blue screen in probably a decade.
What are you referring to here?
probably the CrowdStrike bug. Which is 3rd party software