Nothing to write here, other than, entities have been screaming far too long for companies to vet, test and double test in a real world scenario BEFORE releasing updates to their software. Add-on suites, etc. Today's Crowd-Strike issue speaks for itself, and, SHOULD, serve as a wakeup call to companies not putting quality first. The thing is, most companies and consumers can't do squat to recover their loses.
https://www.crowdstrike.com/blog/statement-on-falcon-content-update-for-windows-hosts/
Meanwhile!! The Crowd Strike fiasco just got much worse.
https://www.msn.com/en-us/money/other/crowdstrike-gets-hit-with-some-more-bad-news/ar-BB1qDo16?ocid=winpstoreapp&cvid=26d5067c54ab4d33b2508e5f5cf72527&ei=9
This is NOT the first time, Microsoft has not vetted an update which then, allowed the Bitlocker issue to bork computers. Having drive encryption enabled as the cause is feltercarb. Some but not all OEM's image their new devices with drive encryption set in group policy for their standard image, even for Windows Home versions. Of course with Home versions that is the only way to enable drive encryption in the first place. SO. Once again this lands squarely on the shoulder of Microsoft.
Similar issues impacted Windows devices in August 2022 after the KB5012170 security update for the Secure Boot DBX (Forbidden Signature Database) triggered 0x800f0922 errors and caused some devices to boot into the BitLocker recovery screen.
More recently, in April 2024, Redmond fixed a known issue causing incorrect BitLocker drive encryption errors in some managed Windows environments, a bug the company tagged in October 2023 (when it was first acknowledged) as a reporting problem with no actual impact on drive encryption.
https://www.bleepingcomputer.com/news/microsoft/windows-july-security-updates-send-pcs-into-bitlocker-recovery/
SA
ONLY, took 5 years to get it right. ONLY!!
https://www.bleepingcomputer.com/news/security/docker-fixes-critical-5-year-old-authentication-bypass-flaw/
SA
For those in a managed environment or are managing Microsoft 365 devices. Microsoft releases at fix tool for the Crowd Strike driver fiasco.
https://www.bleepingcomputer.com/news/microsoft/microsoft-releases-windows-repair-tool-to-remove-crowdstrike-driver/
"The signed Microsoft Recovery Tool can be found in the Microsoft Download Center: https://go.microsoft.com/fwlink/?linkid=2280386."
SA
Amazing!!
https://www.neowin.net/news/crowdstrike-broke-debian-and-rocky-linux-months-ago-but-no-one-noticed/
https://www.digitaltrends.com/computing/southwest-cloudstrike-windows-3-1/