this post was submitted on 19 Jul 2024
62 points (100.0% liked)

Technology

37719 readers
183 users here now

A nice place to discuss rumors, happenings, innovations, and challenges in the technology sphere. We also welcome discussions on the intersections of technology and society. If it’s technological news or discussion of technology, it probably belongs here.

Remember the overriding ethos on Beehaw: Be(e) Nice. Each user you encounter here is a person, and should be treated with kindness (even if they’re wrong, or use a Linux distro you don’t like). Personal attacks will not be tolerated.

Subcommunities on Beehaw:


This community's icon was made by Aaron Schneider, under the CC-BY-NC-SA 4.0 license.

founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
[–] CalcProgrammer1@lemmy.ml 21 points 3 months ago (14 children)

I don't disagree, but today the blame lies with CrowdStrike, not Windows. As much as I hate defending Windows.

[–] Cube6392@beehaw.org 10 points 3 months ago* (last edited 3 months ago) (13 children)

I've seen a weird number of people blaming Microsoft for this today, and an even weirder number of people making fun of people saying this isn't on Microsoft

[–] mobius_slip@beehaw.org 4 points 3 months ago (12 children)

Microsoft chose to work with these people and accepted their faulty input. How is it not Microsoft's fault?

[–] andrew@radiation.party 5 points 3 months ago

Because Microsoft isn’t responsible for every program that runs on their OS.

CrowdStrike is an EDR that enterprises choose to install. The bug was caused by a dodgy content bundle update, which is something that’s meant to be 100% safe but evidently they found and triggered a bug.

load more comments (11 replies)
load more comments (11 replies)
load more comments (11 replies)