A user waves you over: their Mac has shown the spinning rainbow cursor for five minutes, the app ignores every click, and the deadline is in an hour. What you do next, and what you deliberately don't do, is the whole discipline of macOS troubleshooting. Nearly every Mac problem has a built-in tool waiting to fix it; the skill is matching tool to symptom and reaching for the gentlest one first.
CompTIA A+ Core 2 (220-1202) covers macOS in its Operating Systems domain, and the exam expects you to troubleshoot, not just navigate. The testable tools are Force Quit, Activity Monitor, Disk Utility, Time Machine, and macOS Recovery, plus reaching Safe Mode and Apple Diagnostics on both Intel and Apple silicon hardware. Scenario questions almost always ask for the least-destructive next step, so this article walks the ladder from a single frozen app up to reinstalling the operating system, in the order you'd actually climb it.
A frozen app calls for Force Quit, not a reboot
The spinning wait cursor, the pinwheel users call the "beach ball," means an app has stopped responding. A brief appearance during a heavy task is normal; when it persists and the app ignores input, the app is hung, and the fix is to terminate that one app, not restart the machine.
macOS gives you three ways. First, the Apple menu: choose Force Quit, select the stuck app (flagged "not responding"), and click Force Quit. Second, the shortcut Option-Command-Esc opens the same window even when the frozen app covers the screen; memorize it, because the exam treats it as the macOS answer to Ctrl+Alt+Del. Third, Activity Monitor in Applications > Utilities can force quit any process, and it shines when you don't know which app is the problem: sort the CPU column and the runaway process floats to the top.
One caution: force quitting discards unsaved work in that app. It's still gentler than holding the power button, which risks unsaved work in every open app.
An app that won't launch usually has a permissions or preferences problem
A different failure mode is the app that never gets going: it bounces once in the Dock and quits, crashes on open, or throws a permissions error. Because only one app misbehaves, suspect its own files before suspecting macOS.
Start simple. Is the app up to date and compatible with the installed macOS version? An old app after a major upgrade is a classic crash-on-open cause. Next, check permissions: if the app needs the camera, the microphone, or certain folders and the user denied a prompt, it may fail. Those grants live in System Settings under Privacy & Security.
If the app still crashes, think corrupted preferences. macOS apps store settings in property list files, called plists, in the user's Library > Preferences folder, and a corrupted plist can crash an app at every launch as it chokes reading its own settings. The fix is to move the plist out of Preferences and relaunch; the app builds fresh defaults, and the user loses only settings, not data. The exam idea to keep: corrupted preference files cause repeatable crashes, and resetting them is low risk.
The last rung for one broken app is reinstalling it: drag it from Applications to the Trash, then reinstall from the App Store or the developer's site. Even that beats touching the operating system.
Recovery entry differs between Apple silicon and Intel Macs
When the Mac won't boot, the disk needs repair, or macOS must be reinstalled, you need macOS Recovery, a small hidden system that boots independently of the main operating system. How you reach it depends on the processor inside, and the exam tests this split directly.
| Task | Apple silicon (M-series) | Intel |
|---|---|---|
| Enter macOS Recovery | Hold the power button until "Loading startup options," then click Options | Restart and hold Command-R until the Apple logo appears |
| Enter Safe Mode | Hold power for startup options, select the startup disk while holding Shift, choose Continue in Safe Mode | Restart and hold Shift until the login window appears |
| Run Apple Diagnostics | Hold power for startup options, then press Command-D | Restart and hold D during boot |
On Apple silicon, one gesture rules them all: hold the power button until the startup options screen loads, then pick a destination. On Intel, each destination has its own key combination held immediately after power-on. One Intel variation is worth recognizing: Option-Command-R starts Internet Recovery, which downloads a recovery system from Apple's servers when the local recovery partition or the whole startup drive is damaged; a replaced drive booting to a spinning globe is Internet Recovery doing its job.
macOS Recovery bundles the big repair options in one menu
Once Recovery loads, you get a short menu of utilities, and the exam expects you to know what each does and how destructive it is.
Restore from Time Machine rolls the entire system back to a chosen backup, the right call after catastrophic corruption or a failed upgrade, but it overwrites the disk with the backup's contents, so anything created after that backup is lost.
Reinstall macOS downloads and reinstalls the operating system itself. Critically, a standard reinstall preserves user files, apps, and settings; it replaces only the system software, which makes it a legitimate fix for a corrupted operating system that keeps crashing or won't finish booting. Erasing the disk first and then reinstalling, a true wipe-and-reload, is the genuinely destructive version and belongs at the very end of the ladder.
Disk Utility is also available inside Recovery, which matters: you can run First Aid on the startup disk even when the Mac won't boot normally, and repairs are more reliable because the volume isn't busy running the system. For A+ purposes, anchor on the big three: reinstall macOS, Disk Utility, and Restore from Time Machine.
Safe Mode strips startup down to essentials to isolate software conflicts
Safe Mode answers one question: is this problem caused by third-party software that loads at startup?