'Largest IT Outage in History' Sparks Global Chaos.

This is similar to what would have actually happened if not for the dilligence of IT workers fixing the Y2K code issues globally. Uninformed people were worried about missiles and apocalyptic violence, but IT workers withdrew some cash and made sure not to have travel plans.

The difference here is that this was caused by massive and widespread negligence. Every company affected had poor IT infrastructure architecture. Falcon Sensor is one product installed on Windows servers. Updates should go to test environments prior to being pushed to production environments. Dollars to donuts, all of the companies that were not affected had incompetent management or cheap budgets.

Y2K wasn't nonsense. It was unremarkable, ultimately, because of the efforts taken to avoid it for a decade.

20 Years Later, the Y2K Bug Seems Like a Joke—Because Those Behind the Scenes Took It Seriously

President Clinton had exhorted the government in mid-1998 to “put our own house in order,” and large businesses — spurred by their own testing — responded in kind, racking up an estimated expenditure of $100 billion in the United States alone. Their preparations encompassed extensive coordination on a national and local level, as well as on a global scale, with other digitally reliant nations examining their own systems.
“The Y2K crisis didn’t happen precisely because people started preparing for it over a decade in advance. And the general public who was busy stocking up on supplies and stuff just didn’t have a sense that the programmers were on the job,” says Paul Saffo, a futurist and adjunct professor at Stanford University.

What is worth noting about this event is how public concern grows and reacts out of ignorance. Just because a pending catastrophe results in something 'less-than' does not mean best efforts weren't taken to avoid it. Just because something isn't as bad as it could have been doesn't mean it was a hoax (see: covid19). Additionally, just because something turns out to be a grave concern doesn't mean best efforts didn't mitigate what could have been far worse (see: inflation).

After the collective sigh of relief in the first few days of January 2000, however, Y2K morphed into a punch line, as relief gave way to derision — as is so often the case when warnings appear unnecessary after they are heeded. It was called a big hoax; the effort to fix it a waste of time.

Written in 2019 about an event in 1999, it's apparent to me that not much has changed. We're doomed to repeat history even provided with the most advanced technology the world has ever known to pull up the full report of history in the palm of our hands.

The inherent conundrum of the Y2K [insert current event here] debate is that those on both ends of the spectrum — from naysayers to doomsayers — can claim that the outcome proved their predictions correct.

Minis are for painting at unspecified times in the future, not now

I fully support your sacrifice o7

Be sure to post the results to the corresponding communities.

So the hindsight is always 20/20 but was there like warning signs or red flags which should have been obvious this is going to happen or are you just lucky in hindsight?

Same. Had time for my trainees and used this for an extra learning session. :)

Your work and their work, since they can't log in.

Bro, why didn't you lie 😭

It kinda sounds like this ones more on the developers than sysadmins...

Probably, but the issue is in the interface between Windows and the CrowdStrike software causing Windows to go into a crashing bootloop.

Closed source is great, I tell you. /s

Hard to tell, fake news running both of their names, looks like both?

They are saying "up to 15 times" now.

CrowdStrike, not Microsoft, is responsible. Let’s put blame where blame is due.

This could happen to any OS that has cybersecurity where permissions are needed at deeper levels to protect systems.