Intel Optane H10: Two Drives on One Stick

Written and maintained by the Desert Data Recovery lab team. · Updated September 4, 2026

We already wrote about SSDs that will not enumerate and about NAND wear. Those posts still apply when the media is one device. An Intel Optane Memory H10 is not. It is Optane plus QLC NAND on the same stick, and a shop that clones “the SSD” can walk past the side that still has files. We published what that split looks like in the case log.

What the H10 actually is

An Intel Optane Memory H10 is an M.2 NVMe module with two storage technologies on one board: a small amount of fast Optane memory (3D XPoint) and a larger QLC NAND flash area. Windows — and Intel RST when that stack is in the path — presents them as one volume. The laptop treats it like a single SSD. On the bench it is two devices sharing one stick.

That combined volume is why the failure is easy to misread. Disk Management sees one disk. A USB NVMe enclosure sees one namespace, or none. Consumer software scans whatever the host assembled. None of that tells you which physical side is answering, or whether the other side still holds data.

We do not invent capacities or SKUs here. The public cases we have are identified as Optane Memory H10, NVMe M.2, Optane + QLC NAND hybrid. That is enough to know you are not holding a normal single-namespace drive.

How it shows up on the bench

The laptop will not boot. Windows shows RAW, 0 bytes, or a format prompt. Sometimes only one NVMe namespace enumerates and the other is silent. A shop clones “the SSD,” or initializes the unknown disk in Disk Management, and hands back a volume that is missing half of what was on the stick.

How the class presents:

• A dead laptop; the M.2 looks like any other NVMe, so it gets treated like one
• RAW, unallocated, or “you need to initialize this disk”
• Only one namespace enumerates; the other side does not come up
• A clone or USB-enclosure job that copied whichever device the host could see
• Consumer recovery software run against the hybrid volume RST or Windows assembled

Those are presentation patterns, not a diagnosis. The published H10 we have had failed and stopped presenting the client’s data. We assessed each side independently. See why an SSD that will not enumerate is not a software problem if nothing comes up at all — and SSD & NVMe recovery for the service path.

The August 12 job — an honest partial

On August 12, 2026 we recovered an Intel Optane Memory H10 — public case DDR-2026-0009. The write-up is in the case log.

The QLC NAND side — the bulk storage — was not recoverable. The Optane portion was still readable. We imaged that Optane portion, decrypted it, and rebuilt the file system from the image. From there we recovered a large majority of the files the client specifically needed. We were clear that the NAND side was gone, so the client knew exactly what was and was not coming back. Partial recovery.

That is what happened on that module. It is not a prediction about yours. Two H10s can lose opposite sides. The files you need may be on the dead one. That split — one technology gone, the other still worth imaging — is also why we don’t advertise a success rate.

The case involved decryption of the imaged Optane portion. Imaging is not brute force. If the volume is encrypted, we still need the key. We cannot invent a protector, and we will not pretend a clone of ciphertext is your files. Same limit we already state on Windows Device Encryption / BitLocker and on encryption without the key.

What not to do

If the module is dropping off the bus, or the laptop is already dead, leave it powered off. Same rule as any unstable SSD. The second device on the stick does not change that.

Do not:

• Initialize the disk in Disk Management, Disk Utility, or diskpart. That writes a new partition map onto whichever device enumerated
• Format it to “see if it comes back”
• Clone only the namespace that shows up, or run a consumer clone of the hybrid volume, and treat that copy as the whole stick
• Run Recuva, PhotoRec, or other consumer recovery software against the RST/Windows combined volume. Those tools write, and they only see what the host assembled
• Keep powering a dying module hoping the missing side reappears. Every extra session is more controller time on media that may already be failing

What we do instead

Diagnosis first, in-house, at the Phoenix lab. Two devices, assessed independently. We do not guess from a photo of the M.2 which side is alive.

Each device is imaged separately, write-blocked, onto our copies. File-system work happens on those images, not on the patient’s modules. If a side will not read, we say so. If the QLC is gone and Optane still is not, or the reverse, that is the quote — not a promise that the surviving side holds what you need.

QLC NAND that has worn out is the same class of problem we already cover under NAND degradation. Direct chip reads, when they apply at all, still have to get through LDPC, and chip-off is not a bypass on modern encrypted NVMe. We will tell you which path you are on after we look. We will not promise chip-off up front. How long that takes depends on which side answers and what state it is in — see how long data recovery takes. We do not advertise a clock or a success rate.

What to do right now

1. Power it off. Leave the laptop or the module unpowered. Do not keep probing it in another PC.
2. Do not initialize it. Do not format it. Do not clone “the SSD.”
3. Send the module — the whole M.2 stick, not a desktop clone of whichever namespace enumerated. See how to ship a failed drive safely.
4. Get it evaluated. We will tell you which side is answering and whether the files you need are on it. Free evaluation, no data, no fee. Talk directly with a technician.

Laptop internals. Bare NVMe: SSD & NVMe recovery. If you are comparing labs, start with how to choose a data recovery company.