If everything has gone as expected, your Mac is now successfully running High Sierra. (If things haven’t gone as expected, flip forward to Troubleshoot Upgrade Problems.) But there are still a few tasks left to do before you get to work—or play—with your new operating system. In this chapter I cover some important initial setup and configuration activities you should get out of the way right now.
My test installations of High Sierra have used various combinations of starting points, configurations, and upgrade paths. In some cases, after installing, I saw a normal Desktop and nothing more. In other situations—especially when I upgraded older versions of macOS, had a lot of third-party software, or wasn’t previously logged in to iCloud—I was immediately confronted with a large stack of overlapping dialogs and notifications.
Among the most common questions are requests for your user account password or Apple ID password. For example, certain apps may once again need an administrator’s authorization to make changes to your data, and various apps that use your Apple ID (including iTunes and iBooks) may need you to sign in again.
In some situations, you may also see a notification like the one in Figure 9. This appears to mean that, in the process of syncing your accounts via iCloud with your other Macs, High Sierra found one or more email accounts that were either missing from this Mac or had different settings. To add (or update) the accounts, click Continue; High Sierra then opens System Preferences > Internet Accounts, where you can verify all the settings. Or, click Not Now to leave your accounts as is for the time being.
Work your way through any such dialogs you see, even if they seem redundant. After that one-time process, most of them will not reappear.
The next thing you should do is to update macOS itself (and any other crucial Apple software) to the latest version. Sometimes Apple releases bug fixes and security updates almost immediately after a major upgrade, and if any such urgent updates are available, it’s in your best interest to install them right away.
In High Sierra, as in every version of the Mac operating system since Mountain Lion, all updates to Apple software—including macOS itself, built-in software such as Safari and QuickTime, and optional purchases such as Final Cut Pro and Pages—are delivered through the App Store app. And, of course, you can update all the third-party apps you’ve purchased from the App Store at the same time.
In some cases, the App Store notifies you automatically of updates, but I recommend checking manually, shortly after your Mac starts up under High Sierra for the first time. You can open the App Store by clicking its Dock icon, double-clicking its icon in /Applications
or in Launchpad, or choosing Apple > App Store. Then click the Updates button on the toolbar.
Then, to update a single application, click the Update button next to it. (In some cases, Apple groups multiple software updates together; click the More link to see details on each one.) Or, to update all the listed apps at once, click Update All. The App Store downloads and installs the updates automatically.
In addition to installing any updates, decide how you want the App Store to handle future updates. Your Mac can check for, download, and even install updates in the background. Some people turn off all aspects of automatic updates—perhaps because they never want to be interrupted with alerts about new software, dislike the idea of anything downloading behind their backs, or need to keep an eye on a bandwidth cap. Others want all the new things right away without manual intervention and…ahem…have sufficiently robust backups that they can recover from any problems that may arise due to a buggy update.
Follow these steps to configure software updates:
If the High Sierra installer encounters any known incompatibilities, it moves the problematic software to an Incompatible Software folder and explains what it moved on one of the final screens of Setup Assistant. (After Setup Assistant quits, you can find the Incompatible Software folder at the top level of your startup disk, at the top level of your home folder, or even in both places, depending on the location of the software that was disabled.)
This notice appears only for extensions and other low-level background software that would otherwise run automatically when you start up your Mac. As it says, the items in question are moved aside but not deleted. Whatever you do, don’t try to reenable this software manually! Instead, contact the developer and get a version that’s compatible with High Sierra, and then reinstall it.
You may encounter a few other peculiarities when first using High Sierra that cause some initial surprise.
If you’ve been using Apple Mail through a few macOS upgrades, you may not find this surprising, but if you’re new to the upgrade experience, a few aspects of Mail’s behavior are worth knowing about:
~/Library/Mail/Bundles
) into ~/Library/Mail/Bundles (Disabled)
and displays an alert telling you what it’s disabled. Don’t try to reenable these manually; Mail will thwart your every effort to get them working. Check with the developer to see if a High Sierra-compatible update is available.
If Mail hangs or crashes on startup or if Activity Monitor (found in /Applications/Utilities
) shows it to be using excessive CPU power, it could be due to an incompatible plug-in that Mail was unable to disable automatically. Force-quit Mail, look in ~/Library/Mail/Bundles
, and move anything you find there into ~/Library/Mail/Bundles
(Disabled)
. Then open Mail again. If it works, you can quit Mail, move a single plug-in back into ~/Library/Mail/Bundles
, and test again. Repeat until only the problematic plug-in(s) are disabled, and then see if the developers have updated versions of them.
~/Library/Mail
folder from a backup. If you do use Time Machine, open Mail, and then follow these steps:
Restored mailboxes are put directly in the On My Mac section of the Mail sidebar.
After upgrading to High Sierra, you may see an alert (Figure 11) the first time you open a previously installed third-party application that wasn’t downloaded from the App Store.
This alert doesn’t appear if you double-click the app icon, but only if you open it by an indirect method such as double-clicking one of its files. To confirm that you did intend to launch that app, click Open.
If, after upgrading to High Sierra, you install a new third-party app that includes a kernel extension (or KEXT), a warning appears to tell you that the extension won’t run unless you give it permission to run (Figure 12). This is a security feature to prevent malware from gaining low-level control of your Mac. (You can learn more about this new feature in Apple’s developer technical note Secure Kernel Extension Loading.)
If you see this alert, click OK. To approve the new kernel extension, go to System Preferences > Security & Privacy > General, look for the notice at the bottom (Figure 13), and click Allow. (If you don’t do this within 30 minutes, the extension won’t be permitted to run, and the notice will disappear until the next time that extension tries to load—but those subsequent load attempts won’t re-trigger the warning dialog from Figure 12.)
Apart from a few small cosmetic changes in System Preferences, the following new or modified preferences may be of interest:
To learn more about content caching, read Apple’s articles About content caching and Set up content caching.
The best way to confirm that you have all your software installed and configured correctly is to try each application:
/Applications
folder (including the Utilities
folder and anyplace else you’ve stored applications) and launch each app, one at a time. If an application uses plug-ins that you’re aware of, try to exercise at least one or two of them. When you’ve verified that the application works, quit it and move on to the next. Do the same with each of your third-party preference panes, by accessing them in System Preferences. (You needn’t do this all in one sitting—feel free to spread it out over several days or longer.)Similarly, if you use any third-party cloud storage services (such as Dropbox, OneDrive, or Google Drive), confirm that the relevant apps are running and that your data is in sync.
/bin
, /sbin
, or /usr
(except in /usr/loca
l or /usr/share
) in Yosemite or earlier, it will be gone—those are protected directories now, so you’ll have to reinstall those items in another location or restore them to a different directory from your backup.
Also, if you use one of the following package managers, you’ll want to update it and all the binaries you’ve installed using it:
fink selfupdate
first; if that doesn’t work, download a fresh copy.brew update
to update Homebrew itself, and then brew upgrade
to upgrade all your packages.After following these steps and using High Sierra for a few days, if you haven’t discovered any missing files or software that doesn’t work, you can conclude that High Sierra is working properly, and you can overwrite your just-before-upgrading bootable duplicate with a new version (remember, you turned off duplicates in Turn Off (Yes, Off) Automatic Duplicates?)—and turn automatic duplicates back on.
18.116.118.198