What Was Happening
The laptop had been working normally the previous evening. The next morning it powered on, displayed the Acer splash, transitioned to the spinning-dots Windows logo — and then sat there. No login screen, no error message, no recovery prompt. Forced shutdown and restart produced the same behaviour.
The customer was worried about losing their files. The right diagnostic decision in that situation is: don’t reinstall yet. A reinstall is a one-way trip for data unless the drive has been backed up first. Diagnose the cause, then choose the least-disruptive fix that actually works.
Our Diagnosis
A hang at the Windows logo can be hardware or software. Cheapest checks first:
- POST and BIOS health. Reached BIOS without issue. CPU, RAM and storage all enumerated correctly.
- Drive SMART check. Booted from a diagnostic USB, ran SMART read against the internal SSD. Clean — no reallocated sectors, no pending sectors, controller responsive. Storage ruled out.
- RAM test. Quick MemTest pass — no errors. RAM ruled out.
- Safe Mode attempt. Booted into Safe Mode successfully. That single result narrowed the cause significantly: if Safe Mode works but normal boot hangs, the issue is in the standard Windows startup chain — drivers, services, or system file corruption — not a hardware fault and not a bootloader problem.
- Boot log analysis. With Safe Mode reachable, examined the Windows boot logs. Found a partially-written update package and corruption in a couple of system files that load during the normal boot sequence.
Root cause: interrupted Windows update, most likely from a sudden shutdown during an update install. The system files left half-written caused the normal boot to hang on a driver that depended on them.
How We Fixed It
In-place repair preserves the user’s data and applications, which is the right outcome when the underlying drive is healthy:
- Booted into the Windows Recovery Environment from a recovery USB.
- Ran the boot configuration repair to ensure the bootloader was clean.
- Started Windows in Safe Mode and ran
sfc /scannowto repair corrupted system files from the Windows component store. - Followed up with
DISM /online /cleanup-image /restorehealthto repair the component store itself where SFC could not. - Removed the partially-installed update package that had triggered the original corruption.
- Restarted into normal mode — successful boot, login screen, desktop.
- Reapplied the originally-failed update cleanly, this time start-to-finish.
- Verified all user-installed applications launched normally and all user files were intact.
The Result
Laptop booting cleanly to the desktop on the first attempt and every attempt since. All user data and installed applications intact. Customer did not need to spend an evening reinstalling software or signing back into accounts.
Why This Happens
Windows updates are large and complex. They modify dozens of system files, registry keys and driver components. An update can be interrupted by:
- A forced shutdown mid-install (closing the lid, power button held, mains pulled)
- A power cut during the install
- Storage errors during the install that leave a file partially written
- An update package that conflicts with a third-party driver or anti-malware product
The Windows updater is fairly resilient and most interrupted updates self-recover on the next boot. The ones that do not tend to leave the system in this hung-at-the-logo state because a partially-written system file is loaded by something early in the boot chain and the loading process never returns.
How to avoid it
- Let updates finish. “Update and shut down” and “Update and restart” exist for a reason. Choosing them over a hard shutdown gives the updater a clean window to complete.
- Don’t force-shutdown a laptop that says “Working on updates”. Even if it has been an hour. The updater is doing exactly what it says.
- Charge before a major update. A laptop with under 20% battery and no charger is at risk of cutting out mid-update.
- Keep at least one recent backup. Even with the best precautions, occasionally an update goes badly and the laptop ends up needing a full reinstall. A current backup turns that from a disaster into an inconvenience.
Local Help in Putney SW15
A second opinion on a laptop quote often pays for itself.
We see customers from across South West London who’ve been quoted for a full part replacement when the actual fault is somewhere cheaper.
Bring the laptop into our Putney workshop (SW15) or call 020 7610 0500 for a quick conversation first.