Path: ...!eternal-september.org!feeder3.eternal-september.org!news.eternal-september.org!.POSTED!not-for-mail
From: mm0fmf <none@invalid.com>
Newsgroups: nz.comp,comp.misc
Subject: Re: Global Compu-Trouble
Date: Fri, 19 Jul 2024 16:30:08 +0100
Organization: A noiseless patient Spider
Lines: 37
Message-ID: <v7e0q1$31o7l$1@dont-email.me>
References: <v7d8ed$2tj7g$1@dont-email.me> <669a6ce0@news.ausics.net>
 <slrnv9ksmb.47d.candycanearter07@candydeb.host.invalid>
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Injection-Date: Fri, 19 Jul 2024 17:30:10 +0200 (CEST)
Injection-Info: dont-email.me; posting-host="2055a1402ae726c457bc504e05026dd0";
	logging-data="3203317"; mail-complaints-to="abuse@eternal-september.org";	posting-account="U2FsdGVkX1+TvWXzV6Z0EGXSVYiYc/ui"
User-Agent: Mozilla Thunderbird
Cancel-Lock: sha1:0lKws8DjiR3C/3AnTfwMBkjMU5Y=
Content-Language: en-GB
In-Reply-To: <slrnv9ksmb.47d.candycanearter07@candydeb.host.invalid>
Bytes: 2793

On 19/07/2024 15:10, candycanearter07 wrote:
> Computer Nerd Kev <not@telling.you.invalid> wrote at 13:40 this Friday (GMT):
>> In comp.misc Lawrence D'Oliveiro <ldo@nz.invalid> wrote:
>>> I thought this world-wide trouble might be due to some widely-used
>>> cloud service, but it appears the common factor may be something else,
>>> namely their dependence on a security service called ?CrowdStrike?.
>>
>> Yes, though it has in turn taken many VMs in Microsoft's Azure
>> cloud service offline, and amusingly Microsoft's official advice to
>> affected users is to turn their VMs off and on again, repeatedly:
>>
>> https://www.theregister.com/2024/07/19/azure_vms_ruined_by_crowdstrike/
> 
> 
> So what was actually affected?

Crowdstrike is an endpoint monitoring system that is meant to detect bad 
stuff on your computers and stop intrusions and shit. We have it on 
Windows laptops and Windows servers. Never seems to do anything apart 
from once when it decided the software my employer pays me to write was 
a threat when I was testing it ;-)

There was an update today that like many security updates, can get 
rolled out automatically. My employers don't do this... they do do some 
testing of all updates.  The update caused Windows (maybe just Win10) 
machines to BSOD when booting.

There is a manual fix, do a safe boot (doesn't load lots of extra 
drivers and utilities), go and find the erroneous file in one of 
Windows' folders and delete it. Reboot, job done. Repeat on all affected 
machines.

My place has about 17000 Windows laptops and servers (and almost as much 
Linux stuff) so I think IT will be quite pleased they didn't push the 
update out automatically.