this post was submitted on 19 Jul 2024
169 points (96.7% liked)
Technology
58076 readers
4792 users here now
This is a most excellent place for technology news and articles.
Our Rules
- Follow the lemmy.world rules.
- Only tech related content.
- Be excellent to each another!
- Mod approved content bots can post up to 10 articles per day.
- Threads asking for personal tech support may be deleted.
- Politics threads may be removed.
- No memes allowed as posts, OK to post as comments.
- Only approved bots from the list below, to ask if your bot can be added please contact us.
- Check for duplicates before posting, duplicates may be removed
Approved Bots
founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
How did the update get through testing, if the bug has an immediately obvious catastrophic effect?
Agreed, this seems like a pretty obvious failed smoke test.
Three options seem likely to me: the build was untested, the final package got corrupted after testing, the test environment has some kind of abberant config that hid the defect.
Kernel drivers are "reviewed" and signed by Microsoft for exactly this reason. It's a security risk if any program an administrator runs could load malicious kernel drivers into windows
Something I have heard (take with a grain of salt) is that there was a new windows update that went out just before the crowdstrike update. And the issue happened with the new windows update.
Not the case. I have dozens of servers last updated in May that crashed.