Zeitpunkt Nutzer Delta Tröts TNR Titel Version maxTL Fr 19.07.2024 00:00:14 2.017.153 0 97.520.672 48,3 Mastodon 4.3.0... 500 Do 18.07.2024 23:59:02 2.017.153 0 97.520.672 48,3 Mastodon 4.3.0... 500 Do 18.07.2024 23:58:33 2.017.153 0 97.520.672 48,3 Mastodon 4.3.0... 500 Do 18.07.2024 23:58:33 2.017.153 0 97.520.672 48,3 Mastodon 4.3.0... 500 Do 18.07.2024 23:58:19 2.017.153 0 97.520.672 48,3 Mastodon 4.3.0... 500 Do 18.07.2024 23:57:33 2.017.153 0 97.520.672 48,3 Mastodon 4.3.0... 500 Do 18.07.2024 23:57:33 2.017.153 0 97.520.672 48,3 Mastodon 4.3.0... 500 Do 18.07.2024 23:57:32 2.017.153 0 97.520.672 48,3 Mastodon 4.3.0... 500 Do 18.07.2024 23:56:14 2.017.153 0 97.520.672 48,3 Mastodon 4.3.0... 500 Do 18.07.2024 23:56:14 2.017.153 0 97.520.672 48,3 Mastodon 4.3.0... 500
boB Rudis 🇺🇦 (@hrbrmstr) · 03/2017 · Tröts: 7.228 · Folger: 2.110
Fr 19.07.2024 11:23
The attached is via Crowdstrike on X.
If Crowdstrike's agent is on end-user systems in orgs, this will be a nightmare. It's pretty straightforward to do this to servers in datacenters (provided you've got the right automation). It is still gonna take a while.
"There is a faulty channel file, so not quite an update. There is a workaround... 1. Boot Windows into Safe Mode or WRE. 2. Go to C:\Windows\System32\drivers\CrowdStrike 3. Locate and delete file matching "C-00000291*.sys" 4. Boot normally. That workaround won't help everyone though and I've no further actionable help to provide at the minute"
[Öffentlich] Antw.: 0 Wtrl.: 0 Fav.: 0 · via Fedica