Google Chrome has killed a lot of Macs all over the world!

by Kelvin
Macbook Air Teclado

Google is one of the largest software companies in the world… However, it is not immune to mistakes! Sometimes errors that can even be catastrophic for the lives of many users.

After all, Google has just taken responsibility for a speech that eventually "killed" several Mac OS Operating System-based computers. Apple at the beginning of the week.

Google Chrome ‘killed’ several Macs after last browser update corrupted macOS file system

Macbook Air Keyboard "width =" 740 "height =" 420 "srcset =",ret_img,w_740/ /2018/10/macbook-air-2.jpg 740w,,ret_img,w_95/ 10 / macbook-air-2-95x54.jpg 95w,,ret_img,w_350/ /macbook-air-2-350x199.jpg 350w,,ret_img,w_730/ macbook-air-2-730x414.jpg 730w "data-sizes =" (max-width: 740px) 100vw, 740px


Therefore, the critical flaw began to be reported last Monday, hitting several users who simply did not suspect anything. Incidentally, those affected initially thought that the problem was Media Composer, an Avid software that was curiously found on the vast majority of affected machines.

By the way, we can even say that the average user does not have to worry too much about this! After all, this issue only affects those who have disabled System Integrity Protection (SIP) functionality, which in turn prevents modification of macOS protected data by software that is not self-signed. Apple.

So why did these users turn off SIP? Yeah… Video editing professionals need to disable functionality to be able to take advantage of external graphics cards on their Macs.

Thus, a few hundred machines were affected by this problem. However, the recovery is quite fast, including removing the affected software and recovering the parts of macOS that are ultimately damaged by the bug.

To remove the update from Google Chrome, users will need to sign in to their Mac from recovery mode by entering these commands:

  • chroot / Volumes / Macintosh HD (note: “Macintosh HD” is the default)
  • rm -rf /Library/Google/GoogleSoftwareUpdate/GoogleSoftwareUpdate.bundle
  • mv var var_back # var may not exist but this is fine
  • ln -sh private / var var
  • chflags -h restricted / var
  • chflags -h hidden / var
  • xattr -sw “” / var

Besides, what do you think about all this? Share with us your opinion in the comments below.


This site uses cookies to improve your experience. Accept Read more

Privacy Policy
escort malatya escort bursa escort antalya escort konya mersin escort
konya escort antalya escort malatya escort malatya escort bursa escort hatay escort kayseri escort kahramanmaraş escort niğde escort mersin escort