3 ms·
A year ago, a Chrome update (its Keystone auto-update agent) corrupted system files in Macs which had SIP disabled [1]. The result was that they didn't boot any
by gardaani 6y ago
A year ago, a Chrome update (its Keystone auto-update agent) corrupted system files in Macs which had SIP disabled [1]. The result was that they didn't boot anymore. Mac users who had SIP enabled were not affected.
I won't disable SIP and I'll avoid installing Google Chrome on my new Macs, if possible.
[1] https://support.google.com/chrome/thread/15235262?hl=en https://support.google.com/chrome/thread/15235262?hl=en
- dreamcompiler 6y agoIf you can figure out how to disable SIP, you can figure out how to disable Keystone. The latter is probably a much better idea.
- Wowfunhappy 6y agoA major application briefly had a (very bad) bug. It happens. It probably won’t happen the same way again.