Shreyansh Goyal’s Post

The CrowdStrike caused Microsoft outage today is totally not a fault of Microsoft and is only being linked to it either because of massive non-technical user base or by media agencies for click-bait. Though CrowdStrike is at fault but we must understand bugs happen all the time with a software and there’s not a single software company that does this for a reason. The outage only shows what happens when the world depends on one or few outsourced vendors for managing their “critical” systems and they could unknowingly or decidedly crash everything. Resiliency in such scenarios, investing more efforts on owning your data, technology and its protection is as much as needed as acquiring another potential competitor. In addition, I think Microsoft Windows should have a way of unloading faulty drivers than crashing at all. #microsoft #crowdstrike #outage #microsoftoutage #crowdstrikeupdate #windowsbug #windowsbsod

I was wondering and searching for details on how exactly the Microsoft outage occurred, and here’s what I found out: Well we can say it wasn't entirely Microsoft's fault. The root cause was actually linked to an update from CrowdStrike for Windows. The update introduced a bug in a driver file named C-00000291.sys. This driver operates in kernel mode, which means it interacts closely with the system’s core functions. The buggy code attempted to access an invalid memory location, triggering a system panic and resulting in the notorious blue screen. To fix the issue, affected systems had to be rebooted in fail-safe mode, and the problematic driver had to be manually removed. This process needed to be done individually on each affected machine, which explains the widespread impact. This incident underscores the complexity of system updates and the critical importance of rigorous testing before deployment. #MicrosoftOutage #CrowdStrike #TechInsights #KernelMode #ITSupport

Still Dealing with the Microsoft Outage? Let’s Chat About It! Did anyone else spend yesterday fighting off the dreaded Blue Screen of Death? ☠️ The recent Microsoft outage, caused by a Crowd Strike update, highlights several important lessons: Importance of Testing: Even top-tier software can face issues when interacting with third-party applications. More comprehensive compatibility testing is a must. Ripple Effect: A small software problem can have far-reaching consequences, affecting businesses worldwide. We’re all interconnected! The Blue Screen of Death - Helpful or Harmful? While it can be incredibly annoying, the BSOD actually helps protect against data loss or hardware damage by shutting down the system during severe errors. Code Quality is Key: Rigorous testing during development (like unit testing, integration testing, and user acceptance testing) is crucial to catch issues before they become major problems. #Microsoft #CloudOutage #BSOD #SoftwareDevelopment #TechIndustry

I saw many engineers blaming the outage on Microsoft. Blaming others without identifying the problem is a problem. Microsoft takes some responsibility for checking third-party code providers, but it is CrowdStrike who released an update for Windows that had a bug. The patch runs in Kernel mode to monitor system activity at a low level. Because it was running in Kernel mode, the buggy code was trying to access an invalid memory location that triggered a panic and showed a Blue Screen of Death. The name of the driver file that had the buggy update is "C-00000291.sys." Deleting it fixes the issue, and unfortunately, this needs to be done manually. Microsoft has nothing to do with it. Let's make sure we understand the real source of the problem before pointing fingers. 🛠️🔍 #TechTruth #EngineeringExcellence #RootCauseAnalysis #Crowdstrike #Microsoft #TechCommunity

Microsoft has taken a step forward to assist users with system recovery by releasing a new tool over the weekend. This tool aims to help get your machines back up and running smoothly. However, it's important to note that the main challenge users may face is retrieving their bitlocker recovery keys. Find out more about this initiative here: https://lnkd.in/gKhQeFdC #Microsoft #SystemRecovery #Technology #CrowdStrike #GlobalITOutage2024

🚨 Patch NOW - Microsoft CVE-2024-21412 Under Active Exploit 🚨 A vulnerability in Windows Defender is actively being exploited. CVE-2024-21412 is an active zero-day vulnerability that was disclosed by Trend Micro Zero Day Initiative to Microsoft, and published for the first time today. Great work by ZDI Threat Research Team and Digital Vaccine Engineering to provide customers with advanced Protection/Detection cyber capabilities! #microsoftdefender #zeroday #zerotrustsecurity #microsoftcloud #intrusiondetection #zerodayvulnerabilities

If you are using Microsoft defender please read this article

🚨 The Microsoft and CrowdStrike Incident: How a Tiny Glitch Almost Sent Us Back to the 90s 🚨 Remember the good old days of dial-up internet, floppy disks, and Windows 95? Well, thanks to a tiny component hiccup in Microsoft and CrowdStrike's systems, we nearly got a front-row ticket back to that era! 🤯 Who knew that a small issue could have such massive consequences? It's like finding out that the fate of the world rests on a single paperclip. 🖇️ 🔍 **Key Takeaways:** 1. Interconnected Systems: Our modern tech world is like a giant Jenga tower. Pull out one piece, and the whole thing might come tumbling down. 2. Attention to Detail: Maybe it's time we start appreciating the little things more—like that one screw holding your desk together. 3. Collaborative Effort: It takes a village (or at least a well-coordinated tech team) to keep our digital world from turning into a nostalgic trip down memory lane. So, here's to the tiny components that keep our modern world running smoothly—and to the people who make sure we don't accidentally time travel back to the 90s! #TechNews #Microsoft #CrowdStrike #BackToThe90s #Innovation #QualityControl

Interesting that all news channels are quizzing Crowdstrike for a failed update, and no-one appears to be quizzing Microsoft, when the OS is also to blame, the OS couldn’t handle a simple updated driver error, surely Windows OS should have simply ignored the rogue update and continued on. I realise this is too simple and the reality is more complicated, but looking at the Global impact and focusing on travel and health which have been vastly impacted, says a lot about how fragile the windows OS is when a 41kb update to a driver can cause such wide spread disruption costing £B’s. Ultimately Microsoft, which is an amazing company should do something about this and beef up how the Windows OS should handle failed drivers and fail back to last steady working state.

Leaked conversation between #Microsoft and #CrowdStrike before the late press clarifications to the whole world: 𝗠𝗶𝗰𝗿𝗼𝘀𝗼𝗳𝘁: Hey CrowdStrike, what's up with all these Windows crashes today? Did we miss an update or something?⁣ ⁣ 𝐂𝐫𝐨𝐰𝐝𝐒𝐭𝐫𝐢𝐤𝐞: Uh, about that... We might've pushed a tiny, harmless update that accidentally caused a global outage. Oops.⁣ ⁣ 𝐌𝐢𝐜𝐫𝐨𝐬𝐨𝐟𝐭: Tiny? Harmless? Airports are down, banks are panicking, and my coffee machine won't even boot up!⁣ ⁣ 𝐂𝐫𝐨𝐰𝐝𝐒𝐭𝐫𝐢𝐤𝐞: Look, we're really sorry. We isolated the issue, and we're rolling out a fix. Just tell everyone to reboot. Classic IT solution, right?⁣ ⁣ 𝐌𝐢𝐜𝐫𝐨𝐬𝐨𝐟𝐭: Reboot? You mean the solution we use when we have no idea what's going on? Nice.⁣ ⁣ 𝐂𝐫𝐨𝐰𝐝𝐒𝐭𝐫𝐢𝐤𝐞: Hey, it works! And remember, no cyberattacks here. Just a little oopsie on our part.⁣ ⁣ 𝐌𝐢𝐜𝐫𝐨𝐬𝐨𝐟𝐭: Good to know. Next time, maybe test those updates a bit more? My inbox is exploding!⁣ ⁣ 𝐂𝐫𝐨𝐰𝐝𝐒𝐭𝐫𝐢𝐤𝐞: Lesson learned. Our bad. Coffee's on us next time we meet. Deal?⁣ ⁣ 𝐌𝐢𝐜𝐫𝐨𝐬𝐨𝐟𝐭: Deal. But only if the coffee machine actually boots up by then. #Microsoft #windows #Bluescreen #crowdstrike ----------------------------------------------- Just for fun, please like and share if you like it 😀 😀