MacBook troubleshooting guide · Singapore
MacBook problems after a macOS update
A bar that stopped moving, a Mac that will not boot, a battery gone by lunchtime, a drive that no longer appears. What the installer is doing to your MacBook, which symptoms settle on their own, and when an update has exposed hardware that was already failing.
An update in progress needs patience and mains power, not a force restart — the riskiest minutes show nothing on screen. Heavy drain, hot fans and sluggishness for a few days are background indexing, and they settle. Wireless faults and missing drives are usually drivers or permissions. What does not settle — panics, a disk that will not repair, a Mac that still fails after a clean reinstall — is hardware the update uncovered rather than caused. Erase nothing while your files are unbacked.
On this page
What actually happens during a macOS update
Software Update looks like one operation with one bar. It is really four stages, and knowing which one you are in tells you whether a stalled machine is working hard or in trouble.
Download, staging and the snapshot. The package is staged on the internal drive while the Mac stays usable, and the usual failure here is running out of free space: the installer needs considerably more room than the download itself. macOS then takes an APFS snapshot. Snapshots copy nothing — they pin the volume's state at one instant and keep the old blocks alive while new writes go elsewhere — which is why an update that fails this early usually leaves you where you started.
Rebuilding the sealed system volume. Modern macOS boots from a read-only system volume that is cryptographically sealed: every file hashed, the hashes reduced through a tree to a single seal checked at every start-up. An update cannot patch that in place, so it builds a new system volume, seals it, and only then marks it bootable. The install is all-or-nothing, and it writes a complete operating system to the SSD in one sustained session. Hold that last point.
The firmware stage. The part that matters, and the part nobody sees. An update can also write low-level firmware: on Apple silicon, the boot chain that starts the SoC before macOS exists; on Intel Macs with a T2 chip, bridgeOS, a small operating system running on the T2 itself; on older Intel Macs, the EFI boot ROM. It is brief, often shows only a black screen with silent fans, and is the one window in which losing power can leave a Mac unable to start even its own recovery environment.
Post-install housekeeping. Spotlight rebuilds its index, Photos re-analyses the library, iCloud reconciles what changed, and the first backup is huge because the system volume is new. That runs for hours or days, and causes most "slow and hot since updating" complaints.
Quick diagnosis
Match your symptom to the stage
A guide, not a guarantee — certainty means reading the disk and the board on a bench.
Not sure whether to keep waiting or pull the plug?
Send us the model and what is on the screen. A technician will say whether that is a normal stage or a stalled one.
The update is stuck: how long is too long
No clock is trustworthy: the same screen means different things on an ageing Intel MacBook Pro with a full drive and on a half-empty M-series Air. The bar tracks work completed rather than time elapsed, and the work is not evenly sized, so a long pause followed by a sudden jump is normal.
Still alive: the case is warm and the warmth moves, fans change speed rather than holding one note, the keyboard backlight responds, and the Mac restarts itself once or twice — several automatic restarts during a major upgrade are by design. Possibly stalled: stone cold for hours, nothing moving all evening, or "less than a minute remaining" since yesterday. Wait in hours, on mains power, overnight for a big upgrade.
Cut power while the system volume is being written and you usually get an incomplete, unsealed system — recoverable, because the Mac still boots into recovery and a reinstall over the top leaves your files alone. Cut power during the firmware stage and you can be left with no display, no chime and no recovery environment, because the code that starts the Mac is half written; that is fixable only with a second Mac and a DFU revive. You cannot tell from the screen which stage is running, so assume it is the dangerous one.
It will not boot after the update
"Won't boot" is several faults wearing the same coat, and the first fifteen seconds of screen behaviour narrows it down.
- Nothing at all — no light, no fan, no chime. The Mac never reaches the point where software matters: see a MacBook that will not turn on. If the backlight is on but nothing is drawn, see MacBook black screen faults.
- Logo with a bar that fills and loops. An install that did not finish; recovery and a reinstall over the top fix most of these without touching your data.
- A circle with a line through it. The Mac has found a system it will not boot — after a failed update, usually one left half-built.
- A folder with a question mark. No bootable system found at all — see the folder with a question mark explained.
- Boots, then restarts with "your computer restarted because of a problem". A kernel panic, and after an update the symptom most likely to be hardware. See MacBook kernel panics.
One useful check: if the Mac still reaches recovery, most of what follows is a software repair. If recovery will not load, or the internal disk is missing from Disk Utility once you are there, the problem is already hardware.
Battery draining fast after an update
The question we get most after a major release, and the most misdiagnosed. Four jobs start when you reach the
desktop: Spotlight rebuilds its index across every
file (mds, mds_stores and mdworker in Activity Monitor);
Photos re-runs face and scene analysis; iCloud re-verifies everything that
syncs; and the first backup is far larger than usual. Ignore any time-remaining estimate for
the first day — it is extrapolated from a power draw nothing like your normal week. Settling takes days rather
than weeks.
When it is not normal. A week on and still hot and short-lived is something else: a Mac shutting down abruptly while the charge indicator still shows plenty left, which is a pack that can no longer hold its voltage under load; a Service Recommended status newly appearing in Settings; or a case that no longer sits flat, which is a swelling cell and a safety matter. The update caused none of it — it asked the pack for sustained current and got an honest answer. Cycle count and condition are in System Information, and our guide to a MacBook battery that drains too fast covers what they mean.
Wi-Fi and Bluetooth misbehaving after an update
An update replaces the wireless drivers, often the radio firmware with them, and rewrites the network configuration. A configuration already carrying a corrupt preference file passes the mess straight on: a network that will not rejoin, a connection that authenticates then drops, a stuttering Bluetooth mouse, AirDrop finding nothing.
Rebuild it rather than tinker with it. Forget the network and rejoin, remove and re-add the Wi-Fi service in Network settings, renew the DHCP lease, and unpair and re-pair Bluetooth devices. Then check the local network permission for whatever broke, because recent macOS versions make apps ask before reaching other devices on your network and an update can reset that answer, so printers and NAS boxes fail silently. If instead Wi-Fi reports no hardware installed, or both radios vanish through a reinstall, the logic board is the suspect — and on Apple silicon the module is soldered to it, so it is component-level work rather than a card swap. MacBook Wi-Fi problems has the full diagnosis.
External SSDs and drives that no longer mount
A major release reveals which of your storage tools depended on a low-level driver. Apple has spent several releases moving third-party code out of the kernel into user-space system extensions, and each step strands some vendors — usually NTFS write drivers, encryption tools and virtualisation software. The drive is fine; the software that taught macOS to read it is not, and the fix is a vendor update rather than a reformat.
Permissions come next: macOS asks before an app may use removable volumes, and on Apple silicon laptops before a new accessory may connect at all — answers that can revert during an update, so check Privacy & Security. Then plug the drive straight into the Mac on a cable you trust: a bus-powered 2.5" drive already marginal on a shared hub fails first when power management changes.
That prompt appears for two very different drives: a healthy one whose partition map is momentarily unreadable, and a failing one. The initialise button takes you to Disk Utility, and erasing from there writes a new empty map over the old one — in both cases. Choose Ignore or Eject. If the drive clicks or keeps vanishing, stop using it: every further attempt costs you recoverable data. Bring it in for data recovery and we will read it before anything is written to it.
Slow after the update: the OS, or a drive being exposed?
Separate the two by timing. For the first two or three days, watch the CPU and Disk tabs in Activity Monitor: if indexing processes are at the top, that is housekeeping. If they are not and it still crawls, the benign explanations are memory pressure sitting in amber or red with gigabytes of swap in use, which is paging rather than a fault, and a drive with almost no free space, since APFS needs headroom and local snapshots consume it invisibly.
The reading that matters is disk behaviour. Beachballs tied specifically to reading or writing, apps taking
minutes to open, or First Aid running unusually slowly all mean the drive is retrying operations internally.
That is a failing SSD, and the update did not cause it — it read and wrote the whole surface in one go and
found the weak blocks. Our guides to MacBook slow performance and
MacBook SSD failure go deeper, including kernel_task on
Intel machines, which is macOS throttling to control heat.
Updates expose marginal hardware, they rarely break healthy hardware
An update is a heavier workload than almost anything else your MacBook does in a year: a complete operating system written to the SSD in one session, the processor flat out, memory kept full, sustained current drawn from the battery. Components that were quietly marginal pass everyday use and fail that test.
- Storage. NAND with worn blocks serves light use for months, then surfaces read retries and I/O errors when asked to write a whole system volume at once.
- Memory. A weak cell in soldered LPDDR goes unnoticed at low utilisation and panics once the installer fills memory and keeps it full.
- Battery. A pack near end of life reports a plausible charge but sags under load, so the Mac dies mid-install. That looks like the update killing the machine; the order is the reverse.
- The board. A marginal solder joint, or a via corroding since an old spill, moves with heat. An hour at temperature does what months of browsing never did.
Two questions separate them. Does the fault appear in recovery or Apple Diagnostics, neither of which uses your installed macOS? And is it load-linked — a long file copy, a sustained export — rather than tied to one app? Either answer points at hardware, as does a spill, a drop, or a battery flagged for service before you pressed Update.
What is safe to try at home
Least disruptive first, and none of these erases your files.
Wait, on mains power
Hours rather than minutes, overnight for a major upgrade. Do not close the lid, unplug, or press anything.
Force restart, then strip the accessories
Hold the power button until the Mac switches off, then start it with nothing attached but the charger. Hubs, docks, displays and drives can each stall a boot.
Safe Mode
It skips login items and third-party extensions, which is what a new release tends to reject. The key sequence differs between Apple silicon and Intel; the stuck-on-logo guide lists both.
Recovery, First Aid, reinstall over the top
First Aid repairs the file system without deleting anything. If it passes and the Mac still will not boot, reinstalling macOS from recovery replaces the system and keeps documents, apps and settings — the most effective fix for a failed update.
Intel only: NVRAM and SMC
NVRAM holds boot selection and display settings; the SMC holds power and thermal state. Neither reset exists on Apple silicon, where both are re-evaluated at every start.
Apple silicon last resort: DFU revive
If the firmware stage was interrupted, a second Mac and a data-carrying USB-C cable can rewrite it, and only one specific port accepts a DFU connection. Revive keeps your data; Restore erases the machine.
Your files are not backed up and the Mac will not boot. The disk is missing from Disk Utility, or First Aid fails. It panics in recovery as well as normal use. It has ever had liquid through it. Or you are being invited to erase, initialise or reset something. On Apple silicon and T2 Macs the SSD is soldered to the logic board and cryptographically paired with it, so a failed drive cannot be moved to another Mac: recovery is component-level work, and every further attempt reduces what can be saved.
When to stop and bring it in
Bring it to us when the fault has outlived a reinstall, when recovery cannot see the disk, when the machine panics without a pattern, or when the data matters more than the experiment. We are an independent workshop, not affiliated with or authorised by Apple, and we work at component level — tracing the failed part rather than quoting a whole replacement board. A post-update failure is worked in a fixed order: current draw measured on the bench rather than guessed, suspect storage read before anything else is attempted, and only then software separated from hardware under sustained load rather than at idle.
Before the next update, spend five minutes on prevention: check that a backup has actually completed, clear genuine free space, and confirm that any NTFS driver, encryption tool or virtualisation software you depend on has a build for the new release.
Diagnosis is free on walk-ins, you get a written quote before any work begins, and if we cannot fix it you do not pay a repair fee. Every completed repair carries a written warranty on parts and labour. See our MacBook repair cost guide, the full MacBook repair service, or the MacBook logic board repair bench.
Find us at iDevice Repair Centre, 6 Harper Road, Leong Huat Building #05-02, Singapore 369674 — a three-minute walk from Tai Seng MRT on the Circle Line. Call or WhatsApp +65 9823 2527 before you travel; if the machine cannot travel, we arrange islandwide courier collection and return.
Questions we get every week
MacBook update problems — frequently asked questions
How long should I wait before deciding a macOS update is stuck?
Wait in hours rather than minutes, on mains power. A major upgrade can hold one bar position for a long stretch, and can show a black screen with silent fans while it writes firmware. Read the machine rather than the bar: warmth that moves around the case, changing fan speed and a responsive keyboard backlight all mean work is still happening. Stone cold for hours with nothing moving is the point to force restart.
Is it safe to force restart a MacBook in the middle of an update?
Treat it as a last resort, because it is the one action that can turn a software problem into a hardware one. Interrupting while macOS writes the system volume is usually recoverable: the Mac boots into recovery and a reinstall over the top puts it right with your files intact. Interrupting the firmware stage, which shows nothing useful on screen, can leave a Mac with no display and no recovery environment.
Why is my MacBook battery draining so fast after a macOS update?
For the first few days this is background work rather than a fault. Spotlight rebuilds its search index across every file, Photos re-analyses the library, iCloud re-verifies what syncs, and the first backup afterwards is unusually large. Check the CPU and Energy tabs in Activity Monitor: if indexing processes sit at the top, the answer is patience. Still hot and short-lived a week later is the battery.
Can a macOS update actually damage my MacBook's hardware?
Very rarely. An update tests hardware harder than anything else your Mac does in a year: a complete operating system written to the SSD in one session, the processor flat out, memory kept full, sustained current drawn from the battery. Components already marginal fail that test and look as though the update broke them. The check that settles it is whether the fault also appears in recovery or Apple Diagnostics, neither of which uses your installed macOS.
My Wi-Fi or Bluetooth stopped working properly after updating. What should I try?
An update replaces the wireless drivers and rewrites the network configuration, so rebuild that configuration rather than tinkering with it. Forget the network and rejoin, remove and re-add the Wi-Fi service in Network settings, and renew the DHCP lease. For Bluetooth, unpair and pair again. Check the local network permission for anything that talks to printers or NAS boxes, since recent macOS versions make apps ask and an update can reset the answer.
My external hard drive will not mount after the update. What should I do?
Do not take up the prompt offering to initialise the disk — choose Ignore or Eject, because that route ends in Disk Utility and an erase writes an empty partition map over your data. Usually the cause is benign: a third-party NTFS, encryption or virtualisation driver the new release no longer loads, or a removable-volume permission that reverted. Update the vendor software, check Privacy and Security, and plug the drive straight into the Mac. If it clicks or keeps vanishing, stop and have the data read professionally.
Can I roll back to the previous version of macOS if the new one is worse?
Sometimes, and it is more work than people expect. If you made a Time Machine backup before updating, restoring it is the clean route back. Without one, going back means erasing the drive, installing the older version from scratch and restoring your data — and on Apple silicon you cannot install a version older than the one the machine shipped with. Back up first, and check the symptom is not just unfinished indexing.
Update left your MacBook stuck? Get it looked at before you erase anything
Free diagnosis on walk-ins, a written quote before any work begins, and your data read first. If we cannot fix it, you do not pay a repair fee.