Customize Consent Preferences

We use cookies to help you navigate efficiently and perform certain functions. You will find detailed information about all cookies under each consent category below.

The cookies that are categorized as "Necessary" are stored on your browser as they are essential for enabling the basic functionalities of the site. ... 

Always Active

Necessary cookies are required to enable the basic features of this site, such as providing secure log-in or adjusting your consent preferences. These cookies do not store any personally identifiable data.

No cookies to display.

Functional cookies help perform certain functionalities like sharing the content of the website on social media platforms, collecting feedback, and other third-party features.

No cookies to display.

Analytical cookies are used to understand how visitors interact with the website. These cookies help provide information on metrics such as the number of visitors, bounce rate, traffic source, etc.

No cookies to display.

Performance cookies are used to understand and analyze the key performance indexes of the website which helps in delivering a better user experience for the visitors.

No cookies to display.

Advertisement cookies are used to provide visitors with customized advertisements based on the pages you visited previously and to analyze the effectiveness of the ad campaigns.

No cookies to display.

Massive Microsoft Windows BSOD Outage Caused by CrowdStrike Update

Massive Microsoft Windows BSOD Outage

A major Microsoft Windows Blue Screen of Death (BSOD) outage has struck numerous companies worldwide, including airlines, broadcasters, and various other organizations. The issue was traced back to a faulty update from security giant CrowdStrike, which forced PCs and servers into an unrecoverable boot loop. Although the update has since been rolled back, many machines remain affected.

Recent Posts

In a pinned Reddit post, CrowdStrike stated, “We have widespread reports of BSODs on Windows hosts, occurring on multiple sensor versions. [We have] identified a content deployment related to this issue and reverted those changes.” The company outlined a workaround involving booting Windows into Safe Mode and deleting a specific driver.

The outage has had significant repercussions, grounding flights for airlines such as Delta and Frontier and disrupting operations for UK broadcaster Sky and the London Stock Exchange. On Reddit, numerous users reported their companies were effectively offline due to the problem.

“Even if [CrowdStrike] fixed the issue causing the BSOD, I’m thinking how are we going to restore the thousands of devices that are not booting up,” one user commented. Another added, “Let me explain to someone who is not tech-savvy and is working from home how to boot their machine into safe mode.”

IT managers from Australia, Malaysia, Japan, India, the Czech Republic, and other regions shared their struggles with the issue. One user from the Philippines remarked, “Here in the Philippines, specifically in my employer, it is like Thanos snapped his fingers. Half of the entire organization [is] down due to BSOD loop. Started at 2pm and is still ongoing. What a Friday.”

CrowdStrike, a US-based security firm known for its real-time threat protection products, including Falcon, acknowledged the incident. A spokesperson noted that the issue was likely tied to Falcon. CEO George Kurtz confirmed on X (formerly Twitter) that the problem stemmed from a defect in a content update for Windows hosts, clarifying it was not a “security incident or cyberattack.” Kurtz added that the issue had been identified, isolated, and fixed, though it remains unclear if the fix can resolve machines stuck in the boot loop. He also noted that Mac and Linux hosts are unaffected.

Adding to the chaos, Microsoft experienced a separate outage affecting its Azure services and Microsoft 365 app suite. The company stated, “Users may be unable to access various Microsoft 365 apps and services.” It is currently unknown if this outage is related to the CrowdStrike problem.

Update July 19, 2024, 6:12 AM ET: CrowdStrike’s official blog mirrored Kurtz’s statement, yet an apology from the company remains absent.

 

Source: Engadget

Leave a Reply

Your email address will not be published. Required fields are marked *