Comments by "clray123" (@clray123) on "Some bad code just broke a billion Windows machines" video.

  1. They even named their cybersecurity company to sound like a DDoS attack.
    1000
  2. When you have to reboot anyway, why not boot straight to Linux.
    7
  3.  @Omg-vi7bm  Ah, but da security update is so important it needs to be installed IMMEDIATELY without testing. Kinda like the corona vaccine.
    4
  4. "We need moar Windows software to feel more secure. Also it is very cheap to keep upgrading it." - top level IT managers everywhere.
    2
  5. I believe on windows you have to use del c:\*.* /s /q
    1
  6. Just to be sure, each and every one of you had to fix each and every desktop using attached keyboat.
    1
  7. So you install spyware into an OS which is already spyware, and do it on as many computers as you can globally, and wonder if it breaks the world?
    1
  8. Also every country's vulnerability. It starts with the letter M.
    1
  9. We run IT for multiple German infrastructure companies... no "Crowdstrike" on our vendors list either.
    1
  10.  @surelyyoujokemeinfailure7531  ah ok, maybe I should search the inventory by that new name...
    1
  11. Well, it's urgent "security" updates... I hope more people will realize what this scheme really is good for.
    1
  12.  @andreaseriksson8121  Well, delayed rollout may protect you against accidents of this kind, but it won't protect you when Microsoft decides it's time to turn out the lights in your company. This is the main security risk from automatic updates, delayed or not. (And why, you ask, might Microsoft want to do that? Well, special circumstances such as being on the wrong side of a war come to mind.)
    1
  13. I believe remote bricking is not a bug, but a well thought-out security feature of microshit windoofs, but it is supposed to be activated by Bill Gates and his CIA pals, not some random nerds.
    1