Photo of a MacBook with a striped blue screen, indicating serious issues.


On Monday night, Range reported that movie editors around Los Angeles who had Avid Media Author software application set up were unexpectedly discovering that their Macs were not able to reboot. The publication hypothesized that malware might have been the cause. On Wednesday, Google revealed the genuine cause– a Chrome web browser upgrade.

Particularly, it was a brand-new variation of Chrome’s Keystone updater that triggered many Macs to stop restarting, according to this Chrome open bug post. When the upgrade was set up on Macs that had actually disabled a security function referred to as system stability avoidance and fulfilled a number of other conditions, an important part of the Mac system file was harmed, a Google staff member stated in the online forum.

” This seems a problem with a brand-new variation of Google Keystone,” a various Google staff member composed previously in the thread. “We have actually stopped the rollout and are dealing with removal today.”

When your Mac gets a “varsectomy”

SIP, as system stability defense is generally shortened, was presented in 2015 in the El Capitan variation of macOS (called OS X at the time). As its name recommends, SIP is developed to safeguard the stability of the OS by, to name a few things, securing specific files and folders from being erased or customized, other than by particular, authorized procedures.

It would appear a bug in the Chrome upgrade unintentionally tried to customize parts of the macOS file system. When SIP was allowed– as it is by default– SIP worked as developed and avoided the modification. When the defense was handicapped, nevertheless, the file system was customized in such a way that avoided Macs from restarting. Particularly, according to the Chrome bug thread, the buggy Chrome upgrade eliminated an important symbolic link indicating the/ var folder.

” This leads to system instability that might consist of failure to introduce brand-new UI applications, failure to deal with hostnames in the majority of already-running programs, and failure to reboot effectively,” among the Google workers stated.

The particular conditions needed for the Chrome upgrade to make this modification are:

  • SIP need to be handicapped (or not present, as holds true pre-OS X 10.11)
  • The root directory site,/, need to be writable by the logged-in user
  • A Keystone variation consisting of the bug, 1.2.1375, need to be set up
  • Keystone need to upgrade an item that it monitors.

The factor many users of the Avid Media Author program were impacted, Mac business blog site Mr. Macintosh reported, is that some users of the film-editing software application need to disable SIP when utilizing third-party graphics cards. The publication has actually called the/ var-killing bug “varsectomy.”

Google has directions for bring back unbootable Macs here The procedure includes booting into healing mode and after that opening a terminal window, which to name a few methods can be accessed from the energies folder. From there, run the following commands:

 chroot/ Volumes/Macintosh HD # "Macintosh HD" is the default.
rm -rf/ Library/Google/GoogleSoftwareUpdate/ GoogleSoftwareUpdate.bundle.
mv var var_back # var might not exist, however this is great.
ln -sh private/var var.
chflags -h limited/ var.
chflags -h concealed/ var.
xattr -sw ""/ var

Then reboot.

If whatever goes right, the Mac will reboot with the buggy Chrome upgrade no longer set up and with the harmed file system fixed. It wasn’t right away clear when a repaired variation of the Chrome upgrade will be readily available.