Here's a detailed breakdown of what happened during the Microsoft-CrowdStrike incident!
1) A faulty update from CrowdStrike's Falcon platform caused widespread IT outages, affecting Microsoft Windows systems globally!
2) CrowdStrike released an update for its Falcon platform. This update was automatically pushed to systems with the Falcon agent installed.
3) Shortly after installation, conflicts between the new Falcon update and Windows kernel-level processes began to surface. These conflicts interfered with how Windows handled certain security protocols and system calls.
4) The conflicts caused memory corruption and improper interactions between the Falcon sensor driver and other system components, leading to widespread system crashes (blue screens of death).
5) To fix this issue, Boot into Safe mode, navigate to "%WINDIR% \System32\drivers\CrowdStrike" directory, and delete the file "00000291*.sys".
Tech Mapper
Here's a detailed breakdown of what happened during the Microsoft-CrowdStrike incident!
1) A faulty update from CrowdStrike's Falcon platform caused widespread IT outages, affecting Microsoft Windows systems globally!
2) CrowdStrike released an update for its Falcon platform. This update was automatically pushed to systems with the Falcon agent installed.
3) Shortly after installation, conflicts between the new Falcon update and Windows kernel-level processes began to surface. These conflicts interfered with how Windows handled certain security protocols and system calls.
4) The conflicts caused memory corruption and improper interactions between the Falcon sensor driver and other system components, leading to widespread system crashes (blue screens of death).
5) To fix this issue, Boot into Safe mode, navigate to "%WINDIR% \System32\drivers\CrowdStrike" directory, and delete the file "00000291*.sys".
1 year ago | [YT] | 0