This will tell you all about the tech problem - It was a bad .sys file
in Crowdstrike's software.
https://www.technologyreview.com/2024/07/19/1095161/fix-windows-pc-microsoft-crowdstrike-outage/
If people had been trying to do an early update on their Crowdstrike,
they would have encountered the problem.
From the MIT website this is how to fix it:
How to manually fix your affected computer
There is a known workaround for Windows computers that requires
administrative access to its systems. If you’re affected and have that
high level of access, CrowdStrike has recommended the following steps:
1. Boot Windows into safe mode or the Windows Recovery Environment.
2. Navigate to the C:\Windows\System32\drivers\CrowdStrike directory.
3. Locate the file matching “C-00000291*.sys” and delete it.
Then reboot.
On 20/07/2024 10:44 am, Jan Whitaker wrote:
There was some speculation that the MS problem had been brewing
separately for a few days and the Crowdstrike problem was coincidental.
As I understand it, the problem from CS was at the server level ????
--
Regards
brd
Bernard Robertson-Dunn
Canberra Australia
email: [email protected]
_______________________________________________
Link mailing list
[email protected]
https://mailman.anu.edu.au/mailman/listinfo/link
