Why do I need to reboot after updating Airport Utility to version 6.3.1? Is there some kind of serious kernel tweaks involved in Apple's new router tool? Since when does a robust UNIX operating system need to REBOOT after an update to a basic router utility. A device which has no bearing whatsoever on the core functions OS X. I'm dumbfounded by this. Not only that but it took a whopping 3 minutes to apply the patch.

Somebody please break this down for me.

  • Without more information from you it is not possible to answer. On my MBA 10.8.4 the update 6.3.1 did not require reboot! – Ruskes Jul 13 '13 at 7:56
  • I also didn't have to reboot. Likely Airport Utility wasn't the only update as I installed it on 3 of my Macs and none required a reboot. – user10355 Jul 13 '13 at 8:03
  • thanks. i had previously installed some other updates and already rebooted once. software update showed only the Airport Utility 6.3.1 update and nothing else. perhaps the second reboot was somehow related to my previous updates. pretty strange nonetheless, but at least it's reassuring to know that this isn't standard policy on this update. – billynoah Jul 13 '13 at 9:10
  • 1
    I've installed the AirPort utility on several Macs and there was no reboot required. Perhaps by editing in a link to the package you installed (or looking in /var/log/install.log you might see another package caused the reboot instead of product 091-7170 / Airport Utility) – bmike Jul 13 '13 at 14:56
  • 3
    Both the GUI and the terminal version of software update clearly mention the reboot for the security update and not for the airport update. Either you didn't read carefully enough or your software is broken in that respect. I don't see how anyone could tell which is the case given the lack of detail in your question. – bmike Jul 14 '13 at 13:15

There is no known reason why upgrading an Airport Basestation or Airport Utility should lead to a reboot (and I've never run into this situation either). The best guess (as already stated in the comments above) is that another upgrade was applied at the same time which required a reboot afterwards. Whether you just didn't realize the additional upgrade or it somehow "sneaked" into the upgrade process due to a bug/race condition in the Software Updater is something which is probably impossible to analyze post-factum.

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .