Should have not trusted a third party to install proprietary code into the kernel. It's not a Windows issue directly, they have a Linux version too, but anything that allows third parties to put proprietary code into your kernel and automatically update it without your approval is untrustworthy.

[–] SatansMaggotyCumFart@lemmy.world 25 points 11 months ago (1 children)

Counterpoint: Windows bad.

[–] CalcProgrammer1@lemmy.ml 27 points 11 months ago

I can't disagree with you there.

[–] Damage@slrpnk.net 5 points 11 months ago (3 children)

They have a Linux version, but this happened only to the Windows one... Coincidence?!

[–] qjkxbmwvz@startrek.website 16 points 11 months ago (1 children)

Probably coincidence? It sounds (???) like this is a pretty simple fix on Windows.

The number of times I have borked my Linux machines so they wouldn't boot is, well, greater than zero for sure. Any operating system can be bricked to the point of requiring manual intervention by software with elevated privileges.

[–] Rentlar@lemmy.ca 5 points 11 months ago

The simple fix: turn it off and on up to 15 times

The simple fix 2: delete system32

[–] CalcProgrammer1@lemmy.ml 4 points 11 months ago

Yes, coincidence.

[–] pearsaltchocolatebar@discuss.online 4 points 11 months ago

It's not like they haven't caused Linux outages in the past.