- Messages
- 1,525
- Name
- Neil
- Edit My Images
- Yes
No, it is not MSs fault directly, but it was delivered through their update system, and that has caused many headaches in the past.
It also allowed FTDI to issue a driver update through microsoft updates that bricked and clone FTDI interfaces.
They attacked the innocent buyers, a move that was frowned on by MS and many people considered unethical.
However, it is possible for organisations to control updates to client machines with their servers, but I get the impressions this was a server update. Even then, they can be delayed, but that would involve extra time staff and money.
I'm sure there will be action behind the scenes though
The updates were controlled by Crowdstrikes agent on the hosts and not Windows Update, this is why people use Crowdstrike in the first place as content updates for CS can be deployed immediately minimising risk of day-zero exploits and attacks, and whilst I’d agree that extra resource (not huge) is required for managing the updates internally via SCCM, EM, WUfB or WSUS the reason people choose CS for that risk assurance and quality checking, not manageability.
How many cockups have we seen with day 1 iOS updates, and those don’t include other vendors updates either?