This should be setting of security alarms everywhere
The Crowdstrike remediation method requires a special boot sequence to a powershell environment to selectively delete certain .sys files that temporarily render crowdstike penetration protection OFFLINE
Then a reboot happens, then another update, and then another reboot. During that time, the Windows server is WIDE OPEN to penetration attacks, as the crowdstrike code is not fully active.
In other words, this crowdstrike bug that took down infrastructure all over the world, like Y2K coming to life, had the net effect of making potentially millions of servers DROP THEIR PROTECTION against cyber intrusions, at least temporarily.
During that time, what else is potentially being installed on their systems in preparation for a much larger cyber false flag event? My gut feeling is that this Crowdstrike BUG was no bug at all...
it's a tactic to install a Trojan horse
AND with those servers being down and OPENED I will bet you a $100.00 that the nefarious a$$hats are pinging all those servers ferociously to attack when that is taking place...IT ONLY take MS to get in and get out...HMMMMMM!!!!! Changing Vote Totals Maybe...with NO trace left behind???????
The fix should be sent out too all companies that have Crowdstrike and those servers taken offline (if more than one, take one down, fix it bring it back up) and continue on....
I agree with you on this and it bothers me greatly that this was done DELIBERATELY to open those servers up as you suggest...
F$cking A$$holes!!!!!!!!!! (keeping it nice for the children on the board!!!)