A stuck update and a Mac that will not start can look similar, but the safest next step depends on where startup stops, whether storage is visible, whether data is recoverable and whether the Mac uses Apple silicon or Intel.

Do not make erase/reinstall the opening move. First protect what can be protected and establish the exact failure boundary.

Capture the situation

Record:

  • Mac model/year or exact identifier and Apple silicon versus Intel;
  • current/attempted macOS version where known;
  • owner and Apple ID/organisation management status without exposing credentials;
  • FileVault and recovery authority;
  • last known successful startup and recent update/software/storage/power event;
  • exact screen, symbol, message, progress and elapsed time;
  • external devices/docks/displays/power source;
  • whether Recovery and the internal storage are visible; and
  • current backup type/date plus irreplaceable-data risk.

Photograph the screen and note time. A blank display, prohibited symbol, flashing folder, restart loop, login hang and application crash are different evidence.

If the device is unusually hot, smells electrical, has liquid/impact damage, repeatedly disconnects storage or makes abnormal hardware noise, power it down and use an appropriate service/data-recovery path.

Protect data before broad repair

If macOS still starts, update the approved backup and verify representative files from it. If it does not, avoid repeated forced boots or repair attempts when data is irreplaceable and no recovery copy exists.

Recovery options may include an existing Time Machine/enterprise backup, an authorised share-disk/transfer path, or specialist recovery. Encryption and modern integrated storage change what is feasible. Do not remove storage, bypass ownership controls or promise recovery.

Record the accepted recovery point and what remains unprotected before continuing.

Remove simple external variables

Shut down normally where possible. Disconnect non-essential external storage, hubs, docks, printers and adapters while retaining reliable power, keyboard/mouse and display. Reintroduce devices one by one only after a stable baseline.

Do not disconnect a drive that is the only backup or an installation currently writing. Do not repeatedly force power off merely because an update screen appears still; use the exact Apple guidance for the displayed condition and elapsed time.

Separate update readiness from startup repair

If macOS starts normally, use Apple’s current Software Update path for that Mac and confirm:

  • compatible offered release;
  • reliable power/network;
  • adequate free storage;
  • current backup;
  • important application/security/management compatibility; and
  • time for multiple restarts.

Preserve the exact update error and logs/support evidence before retrying. Free space by moving reviewed user data or using supported storage management—not by deleting unknown system/library files.

If the failure is only one user/login item/application after login, diagnose that layer before treating the system volume as damaged.

Know the two startup paths

Apple silicon and Intel Macs do not use the same entry sequence.

Apple silicon

Shut down, then press and hold the power button until startup options appear. The gear labelled Options enters macOS Recovery. Apple also provides a safe-mode selection from Startup Options.

Intel

Shut down, power on and use the current Apple startup key combination for the required mode—such as Safe Mode or Recovery. Timing and keyboard availability matter; Apple recommends shutting down first when a restart key combination is not recognised.

Do not guess architecture from appearance. Confirm it from known inventory, About This Mac when accessible, or the exact model.

Use Safe Mode as an isolation result

Safe Mode performs startup checks and restricts some software that loads during normal startup. If the Mac starts there:

  1. capture available storage and the observed behaviour;
  2. preserve relevant recent software/login-item changes;
  3. restart normally once; and
  4. if the problem returns, investigate login items, extensions, security/management software and the specific user/application path.

Safe Mode working does not prove the disk, backup or all applications are healthy. Safe Mode failing does not prove the disk is defective.

Use Recovery deliberately

macOS Recovery is a tool environment, not an instruction to erase. From Recovery you can inspect startup disks, use Disk Utility and reinstall macOS; available tools vary by architecture and version.

Record whether:

  • Recovery opens;
  • the expected internal physical device, APFS container and system/data volumes appear;
  • volumes unlock/mount under authorised credentials;
  • Disk Utility reports errors; and
  • a compatible reinstall target is offered.

If the internal physical device is not visible, repeated filesystem actions will not fix that absence. Preserve data risk and seek service.

Run First Aid in the documented order

Apple says to have a current backup first. In Disk Utility choose View > Show All Devices, then run First Aid from the last volume upward: each volume, then each container, then the physical device.

For the startup disk, Recovery is the appropriate environment. Save the exact results. First Aid can find/repair certain formatting and directory-structure errors; it cannot detect or repair every storage/hardware/data problem.

If First Aid reports impending failure, an unrepairable error, or the device disappears, stop repeating it. Prioritise backup/recovery and Apple/qualified service. Erasing is destructive and is outside this diagnostic guide.

Consider a non-erasing reinstall only after evidence

Apple’s current Recovery reinstall is intended not to remove apps or personal data, but Apple still recommends backing up first. Reinstall only when:

  • the owner and recovery/management authority are confirmed;
  • protected recovery is adequate;
  • storage is visible and sufficiently healthy;
  • the installer offers the expected system volume;
  • power/network requirements are met; and
  • the exact compatible macOS outcome is understood.

Reinstalling replaces system components; it does not guarantee resolution of failing storage, incompatible third-party software, user-data corruption or hardware faults. Do not select erase/format because an installer cannot see a target without first treating that as a data-risk decision.

Verify the actual outcome

After recovery/update, confirm:

  • exact macOS build and expected update state;
  • normal startup and restart without external devices;
  • intended user login and FileVault/management posture;
  • storage visibility and saved First Aid result;
  • representative user files and backup completion;
  • required business applications, network and peripherals; and
  • no new repeated restart/update/storage errors.

Then reconnect external devices one at a time. A successful desktop login is not complete recovery if the user’s data, backup, management or required application is broken.

Escalate with useful evidence

Provide model/architecture, macOS/update target, exact screen/error/time, startup modes reached, internal-device visibility, First Aid details, external-device isolation, backup/data risk and ownership/management constraints. Do not send Apple ID passwords, recovery keys or unredacted personal data.

The goal is the least destructive supported route to a known-good, backed-up outcome—not the fastest route to a clean-looking setup screen.