What Was Happening
The tower had been working fine, then started showing extended boot times, then stopped reaching the desktop at all. By the time it came in, the customer was getting an automatic-repair loop — the system would attempt repair, fail, then try again on the next power cycle.
The customer wanted two things: the tower working again, and the documents folder preserved. The documents folder is what mattered; the OS install itself was effectively replaceable.
Our Diagnosis
A tower with this symptom needs hardware ruled out first, because reinstalling Windows onto failing hardware just creates a new corrupted install in a few weeks:
- POST and BIOS. Cold boot, side panel off. Single beep, normal POST sequence, BIOS accessible. CPU enumerating correctly, RAM count matching the installed modules. Motherboard ruled out as a primary suspect.
- Boot device list. Drive present in BIOS with the correct model and capacity reported. That tells us the drive’s controller is at least talking to the motherboard reliably.
- SMART check from a bootable diagnostic USB. SMART returned cleanly, with no reallocated sectors, no pending sectors, and the controller responding to all ATA queries. Drive ruled out as a hardware fault — the problem was data on the drive, not the drive itself.
- RAM test. A quick MemTest pass — no errors over a full sweep. RAM ruled out.
- Boot from a Windows installer USB. Setup launched cleanly. Confirmed the machine could run Windows; the only fault was the existing install.
Outcome: hardware all healthy. The OS install on the drive was unrecoverable through in-place repair attempts — automatic repair had run several times without success before we saw it, which usually means the corruption is past what SFC and DISM can address.
How We Fixed It
Image the drive first. Connected the drive to our imaging setup, took a complete bit-for-bit copy. Even with Windows broken, the user’s files and folders sat on the drive readable through the image. This step is the difference between “reinstall and lose everything” and “reinstall and restore everything”.
Verified the image. Browsed the imaged user profile, confirmed Documents, Desktop, Downloads, Pictures and any other folders the customer flagged were readable. Cross-checked a representative file from each — opened in its expected application without error.
Clean Windows install. Wiped the drive completely, ran setup through to first boot. Skipped Microsoft account sign-in initially so the local user account was set up first; the customer can attach their Microsoft account later if they want.
HP driver bundle. This is where third-party PC repair often goes off-script and the result is a system that works “well enough” rather than properly. HP publishes a per-model driver pack covering chipset, network, audio, integrated graphics, system management and BIOS firmware. We use HP’s own tooling rather than third-party “driver updater” software. Stable, current, no spyware bundled in.
Windows updates run to current state on the bench so the customer is not waiting on “preparing updates” the first time they switch the tower on.
Restored user files from the image. Documents, Pictures, Downloads, Desktop folders back in the user profile on the new install. Browser bookmarks where the user’s master credentials were available.
Verification. Three full reboots, all completing under 30 seconds. Network connectivity confirmed. Standard suite of applications launched cleanly.
The Result
Tower booting reliably in under 30 seconds. User files restored. HP’s own drivers installed cleanly. The system is now in a known-good state that the customer can build on rather than the accumulated cruft of the previous install.
Why This Happens
Windows OS corruption that defeats automatic repair usually comes from one of a few causes:
- An interrupted update. Forced shutdown during “preparing updates” leaves system files half-written. The most common cause we see.
- Storage errors during normal operation. A drive that has been throwing occasional read errors corrupts files Windows depends on, until eventually one of those files is in the boot chain.
- Aggressive third-party “cleaner” or “optimiser” software. Some of these tools delete things they shouldn’t and break the boot configuration in the process.
- Malware that has been partially removed by antivirus but left the system in an inconsistent state.
A clean install is the right answer when in-place repair has already failed. Trying additional in-place repair attempts on a system that has already been through several automatic-repair cycles is rarely productive — and each attempt makes the eventual reinstall a little harder by adding more half-finished state.
How to make recovery easier next time
- Keep a recent backup of user data. The simplest answer is automatic backup software pointing at an external drive or cloud storage. Most of the work in a job like this is the data recovery, not the OS install.
- Don’t force-shutdown a machine that’s doing Windows updates. Even if it has been an hour. Let it finish.
- Use OneDrive or similar for the Documents and Pictures folders if you use Windows. It is the simplest way to have everything important synced to a second location automatically.
- Avoid “cleaner” and “registry optimiser” products. Most of them deliver no real benefit and a small number actively damage Windows installations.
Local Help in Fulham SW6
Desktop and all-in-one diagnosis is usually quicker than laptop work because the internals are easier to access and test individually.
We service custom-built desktops, branded towers, all-in-ones and gaming PCs from our Putney workshop.
Drop in to SW15, call 020 7610 0500, or book through the contact form.