Field note: the laptop that hung on every boot device, and the dead M.2 behind it

A work laptop came in after a Windows update attempt went bad. It sat on a spinning circle and never got any further. It looked like a broken Windows install, but by the end the question wasn’t how to repair Windows. It was whether the laptop would ever boot anything again.

What it looked like

The useful part was how many different things hung in the same way:

1. Windows stopped at the spinning circle.
2. Recovery mode stopped at the same spinning circle.
3. A USB Windows installer did it too.
4. A Clonezilla USB hung early, at Waiting for single CPU status.

Windows being broken explains the first two. It doesn’t explain the last two, because neither one needs anything from the Windows install on the internal drive. Once a separate operating system on a separate USB stick hangs too, the problem is below the OS.

The BIOS was the one thing that still opened.

What I tried

Secure Boot and Fast Boot were already off, so there was nothing to change there. I reflashed the BIOS with its built-in flash tool, which didn’t help.

The next step was to pull the internal drives and look at them directly. This laptop had two: an M.2 and a separate 2 TB spinning disk.

• The 2 TB spinning disk was readable, and I recovered its data.
• The M.2 showed as Unknown and Not Initialized, with no readable size.

If you end up here, don’t click through the initialize prompt on a disk you still hope to read. Microsoft warns that initializing can erase what’s on it. Its troubleshooting guide also says the most common reason for a disk showing Not Initialized is that the disk is failing, and the suggested test is to try it on another PC. If it fails there too, the disk is the likely problem.

What I concluded

The drive died, and it took the PCIe bus with it. That’s why nothing would boot, no matter where the boot was coming from. An NVMe M.2 drive connects straight to PCIe rather than sitting behind a separate disk controller, so a drive failing badly enough to upset the bus has a path to affect the whole machine, not just one volume.

To be clear about what that is: nothing above is a board-level test. It’s the conclusion the evidence points to, and the laptop is DOA.

The data side turned out far better than the hardware side. Mail was on Exchange Online with an OST cache on the laptop. An OST is only a local copy of what’s on the mail server, so losing it cost nothing. With the 2 TB disk recovered, no local data was lost.

What I took away from it

• Count how many things hang, not just where. One OS failing is a software question. Everything failing the same way, including tools booted from USB, is a hardware question.
• A working BIOS doesn’t clear the hardware. It got me into setup and that was all. It proved very little about whether the drive and bus were healthy.
• Try a USB boot before spending time on Windows repairs. Two different boot sticks hanging says the problem isn’t Windows.
• Pull the drives and look at them directly. That’s what turned “it won’t boot” into a diagnosis.
• Know where the data lives before the laptop dies. Mail in Exchange Online and an OST that’s only a cache made this an inconvenience instead of a loss.

Sources

• Microsoft Learn: Troubleshoot Disk Management: what Not Initialized and Unknown mean, disk failure as the most common cause, the warning about initializing, and testing the disk on another PC
• Microsoft Support: Open or import items from an offline Outlook Data File (.ost): OST files are copies of items saved on the mail server
• Microsoft Learn: Plan and configure Cached Exchange Mode: the local mailbox copy in an offline data file
• Red Hat: NVMe vs. M.2: M.2 as a form factor and NVMe’s direct connection to PCIe