Intel Optane Drive Recovery: When the Computer Won’t Boot and the Drive Shows as RAW

The typical scenario is something like this. The computer was working normally. A Windows update installed overnight, or a planned upgrade to Windows 11 completed, or the laptop was simply restarted after sitting closed for a few days. The next time the computer powers on, it doesn’t boot. Maybe it goes straight into an “Automatic Repair” loop that never finishes. Maybe it gets to a blue screen with an error like PNP_DRIVER_WATCHDOG and reboots. Maybe it stops at “Preparing Automatic Repair” and spins forever. Eventually, an attempt to look at the drive from another computer or a Windows recovery USB reveals the problem: the storage partition shows up as RAW, or it doesn’t show up at all, and only a small portion of the drive — maybe 16GB or 32GB — is visible.

If this matches what you’re seeing, the chances are very high that your computer has an Intel Optane drive inside, and that the Optane configuration has broken. This is one of the most common failure patterns we see in our lab, and it’s the source of a lot of frustration because the well-meaning advice scattered across Intel, Dell, HP, and Microsoft community forums frequently points users toward steps that destroy their data permanently. This guide walks through what’s actually happening, why these drives fail this way (and especially why Windows updates trigger it), what not to do, and what realistic data recovery looks like.

What Intel Optane is, briefly

Intel Optane was a storage technology Intel sold from 2017 through 2022, when the product line was discontinued. In consumer machines, Optane most often showed up in one of two configurations:

• Optane Memory cache, where a small Optane module (typically 16GB or 32GB) was paired with a conventional hard drive or SSD to act as a fast cache layer. The system saw both as a single combined volume thanks to Intel Rapid Storage Technology (RST).
• Optane Memory H10 / H20 hybrid drives, where both the Optane cache and the NAND flash storage were physically combined on a single M.2 card. The H10 typically pairs 32GB of Optane with 256GB, 512GB, or 1TB of QLC NAND. The H20 is the newer version with similar capacity options.

The important detail for understanding why these drives fail: in both configurations, the Optane portion and the storage portion are physically separate at the hardware level, but logically combined by Intel RST software running inside Windows. The metadata that describes how the two halves fit together — which blocks live where, what’s in the cache, what’s on disk — is maintained by RST. When RST is healthy, the system sees one drive. When RST breaks, the system sees two strangers.

That’s the failure mode. Everything else in this article is a consequence of it.

The pattern: Windows update, then nothing works

Across the cases we see and the forums where these failures are discussed, the trigger is consistent enough to be predictable:

• A Windows 10 cumulative update or feature update installs.
• A Windows 11 upgrade installs (the 22H2 update is particularly well-documented as a trigger).
• A laptop sits closed for an extended period and then refuses to wake / boot.
• A laptop battery is replaced or the system goes through an unrelated repair that involves a power-down.

The common thread is a change of state on the boot drive’s software stack. The Intel RST driver that holds the Optane cache and the underlying storage together either gets updated to a version that’s incompatible with the existing pairing, gets disabled by Windows during the update process, or simply loses its connection to the cache metadata. The next time the system tries to boot, the Optane and the NAND can no longer be assembled back into a single coherent volume. The result is what users see:

• The computer enters an Automatic Repair loop and never recovers.
• The boot process fails with a “boot device not found” or “no bootable device” message.
• When examined from a recovery USB or another computer, the storage partition shows as RAW, or doesn’t appear at all.
• Disk Management shows only the small Optane portion (16GB or 32GB) and the main storage partition has either vanished or is listed with the wrong capacity.
• Recovery software run against the drive finds fragments but no usable folder structure — file names show up but the data behind them is gibberish.
• BSOD errors during boot attempts, most commonly PNP_DRIVER_WATCHDOG, INACCESSIBLE_BOOT_DEVICE, or CRITICAL_PROCESS_DIED.

Customers describe it in language like “failed shortly after windows 11 upgrade,” “stuck in auto repair loop,” “shows Intel RAID member when plugged in,” “flash partition went RAW,” and “recognized as a connected device but capacity and format of partitions are not able to be recognized.” On the lab side, our engineers see the same pattern week after week — usually on systems that haven’t been touched in months, where a recent Windows update finally caught up with the machine.

Why this is harder than it looks

If both physical halves of the drive are still alive — which they almost always are — recovering the data sounds like it should be straightforward. Image the NAND portion, parse the file system, get the files. The problem is that the file system on the NAND portion is deliberately incomplete. The Optane cache wasn’t just sitting there for performance; it was holding the most recently written copies of frequently-accessed blocks. The file system metadata on the NAND assumes the cache is present and provides those blocks. When the cache is unreachable, the NAND-side file system can’t be parsed normally — pointers go to addresses that should be in the cache, NTFS structures reference data that lives across the boundary, and recovery software sees a corrupted file system instead of a functional one.

This is why customers who pull the NAND portion and try to read it externally see “User folder and a lot of the Windows folder is missing.” The folders aren’t missing — they’re partially in the NAND and partially in the Optane, and without RST’s metadata to assemble them, what’s visible is the incomplete half.

Successful recovery on these drives requires either:

1. Imaging both physical portions of the drive (the Optane cache and the NAND storage) separately, then reconstructing the RST metadata in software to assemble the original logical volume — the way the system saw it before the failure.
2. In cases where the Optane portion is too damaged to image, reconstructing the file system from the NAND alone using knowledge of how RST stores its metadata and which blocks were typically held in the cache.

Both approaches require specialized tools that understand the Intel RST volume format, and neither is something Windows itself or generic data recovery software can do.

Which machines we see this on

The Optane failure pattern shows up across most of the consumer and small-business platforms that ever shipped with Optane. The machines we see most often in our lab:

• HP Pavilion and HP Pavilion gaming laptops and desktops with Optane + HDD or Optane + SSD configurations
• ASUS ZenBook and ASUS VivoBook laptops with H10 hybrid drives
• Dell OptiPlex desktops in the 3050, 5050, 7050, 3060, 5060, 7060 series (Dell specifically validated these for Optane and shipped many with the configuration)
• Dell Inspiron desktops, particularly the 3670
• Dell Vostro small business desktops
• Alienware Aurora R6 and Area 51 R4
• Various Lenovo, Acer, and Toshiba consumer laptops sold 2018–2021 with 16GB or 32GB Optane modules paired with conventional HDDs

If your machine was sold between roughly 2017 and 2022 in a tier above pure budget but below premium ultrabook, and it shipped with what was advertised as a “fast SSD + large HDD” configuration, there’s a meaningful chance Optane is involved even if you never thought about it. The Optane portion was largely invisible to end users in normal operation — it just made the HDD-backed system feel faster than HDDs usually do.

What not to do

The fastest way to convert a recoverable Optane failure into a permanent data loss is to follow the well-meaning advice that dominates Intel, Dell, HP, and Microsoft community forums on this topic. Specifically:

1. Don’t run “Reset to non-Optane” from the BIOS or Intel RST utility. This is Dell’s officially recommended troubleshooting step, and HP’s, and Intel’s. It also explicitly destroys all data on both portions of the drive. Dell’s own knowledge base says so in the fine print: “The option to Reset to non-Optane will clear all data including the operating system on the Hard Drive.” If the data on the drive matters, do not choose this option.
2. Don’t run diskpart clean on either portion of the drive — also commonly suggested as a fix in Intel community threads. Clean wipes the partition table. Both halves of the drive need their partition tables intact for recovery.
3. Don’t initialize either portion of the drive when Windows prompts you to. Initialization writes a new, empty partition table over the existing one.
4. Don’t run bootrec /fixmbr, bootrec /fixboot, or bootrec /rebuildbcd against the drive in the hope of fixing the boot problem. These commands write to the drive’s boot region — fine on a healthy boot drive, but on an Optane volume where the RST configuration is already damaged, they can finish off the partition metadata recovery depends on.
5. Don’t run CHKDSK on the storage partition. When it shows as RAW, CHKDSK will offer to fix file system errors. The “errors” it sees are the consequence of the broken Optane pairing, not actual file system errors. Letting it write changes makes things worse.
6. Don’t install a clean copy of Windows on the drive to “see if you can get to your files afterward.” A fresh Windows install repartitions the drive. The original data is gone.
7. Don’t physically pull the M.2 card and try to read it in a USB enclosure. For pure-Optane modules, this rarely produces anything readable. For H10/H20 hybrid drives, the USB enclosure typically only sees one half of the drive and the file system it presents is incomplete.

If you’ve already done one of these things, recovery may still be possible — outcomes depend on what specifically was written to which portion of the drive. But the recovery is harder, and in some cases the data is genuinely gone. The advice on the forums is not malicious; it’s just designed to get the computer working again, not to preserve the data on it.

What our recovery process looks like

The Optane recovery workflow in our lab depends on the specific failure type, but the general shape is consistent. The drive arrives. We identify which Optane configuration it is — pure Optane module + separate HDD, pure Optane module + separate SSD, or H10/H20 hybrid M.2 with both portions on one card. Each is imaged independently using hardware that doesn’t depend on the original system’s RST driver to read the drive. Both images are then taken offline and the Intel RST volume format is parsed manually — identifying which blocks lived on the Optane side, which lived on the NAND/HDD side, and how they were combined into the volume the operating system saw.

Once the original logical volume is reconstructed offline, the file system can be parsed normally and the customer’s files extracted. The data is delivered on a fresh destination drive. The original drive(s) are returned but typically can’t be put back into productive use without a full reset (which would destroy the recovered data again) — so they’re a recovery target, not a repair target.

In cases where the Optane portion is genuinely destroyed and only the NAND/HDD can be imaged, recovery is still often possible but partial — files that lived entirely on the NAND side come back cleanly; files that crossed the Optane boundary may be partially recoverable or unreadable. We can tell which category your case falls into during the free evaluation, before any work is committed.

A note on cost

Optane recoveries involve real engineering time because of the need to reconstruct the RST volume offline. They’re generally not the cheapest category of recovery we do, but they’re not at the high end either — most cases land somewhere between low-mid hundreds and low thousands of dollars depending on the specific configuration and how much of the original Optane data survived. The standard Gillware engagement applies: free evaluation, flat-rate quote in writing before any work begins, you only pay if we successfully recover your data. If the quote doesn’t make sense for the specific value of the data on the drive, you can decline and have the drive returned at no charge.

Frequently asked questions

How do I know if my computer has Optane?

If you bought a Windows machine between 2017 and 2022 advertised as having “fast SSD performance with the storage of a hard drive” or with a configuration like “16GB / 32GB + 1TB” or “32GB + 512GB,” there’s a good chance Optane is involved. You can also check from a working Windows install: open Device Manager and look under “Disk drives” for an “INTEL MEMPEK” or similar entry, or open Intel’s Rapid Storage Technology utility if it’s installed. From outside the system, a BIOS or boot menu that shows two separate drives — one very small (16GB or 32GB) and one larger — that the operating system normally sees as one combined drive is the signature.

Why did this only happen after a Windows update?

Windows updates frequently touch storage drivers, and the Intel RST driver in particular is sensitive to mismatches between the version the operating system thinks should be running and the version that actually started up. When the driver fails to load correctly on first boot after an update, the Optane pairing can’t be assembled, and the system sees the two physical drives as unrelated. The Windows 11 22H2 update is the most-documented offender, but the pattern goes back to various Windows 10 cumulative updates over the years.

Can I just disable Optane in BIOS and use the storage drive normally?

Sometimes, but with major caveats. If the drive was configured with Optane acceleration (where the storage drive holds a complete copy of the data and Optane is just speeding things up), then turning Optane off may let the system boot from the storage drive directly. If the drive was configured for write-back caching (where some blocks live exclusively in the Optane), turning Optane off leaves the storage drive in an incomplete state. There’s no universal way to tell which configuration was used without inspecting the drive. The safe assumption: if you can’t boot and the data matters, don’t experiment with BIOS changes — get the drive evaluated first.

My computer is in an Automatic Repair loop. Is it safe to let it keep trying?

No. The Automatic Repair process can write to the drive in ways that compound the original Optane failure. The repair process is designed for healthy boot drives with damaged boot configurations, not for Optane volumes where the underlying storage pairing has broken. Every additional repair attempt is a chance for Windows to write changes that aren’t recoverable. Better to power the machine off and remove the drive (or evaluate it externally) than to let auto-repair continue.

Intel discontinued Optane. Does that mean my drive can’t be recovered?

No — the product discontinuation has no effect on data recovery. The hardware still exists, the data structures are still parsable, and labs that work on Optane drives have the tools and knowledge to recover them. What the discontinuation does mean is that Intel is no longer producing replacement modules or supporting the RST software as actively, so the long-term outlook for keeping these machines in service is limited. After recovery, most customers either move their data to a non-Optane system or have the system re-provisioned with a single conventional SSD.

Can I just buy a new SSD and migrate my Optane data to it?

Yes — and this is generally the right path forward after a successful recovery. Modern NVMe SSDs are large enough and fast enough that Optane’s original performance niche no longer exists; a 1TB consumer NVMe SSD costs less than what Optane modules originally cost and outperforms the combined Optane + HDD configuration. Once your data is recovered, replacing the Optane setup with a single NVMe SSD typically restores normal performance and eliminates the failure mode entirely.

Is BitLocker involved?

Sometimes. Many Optane-equipped systems shipped with BitLocker enabled by default, particularly Dell and HP business laptops. If your data is BitLocker-protected, recovery is still possible but requires the BitLocker recovery key to actually access the recovered data. The key is typically saved to your Microsoft account or printed/saved when BitLocker was first turned on. Find your recovery key before assuming you’re stuck — even on Optane drives, the BitLocker layer behaves the same way as on any other drive.

The bottom line

Intel Optane drives that detect partially, show the storage portion as RAW, or refuse to boot the computer after a Windows update are one of the most consistently recoverable categories of failed storage we work on — as long as no one has tried to “reset” the configuration before the drive arrives. The data is still on the drive. The Optane and NAND portions are still physically alive. The problem is logical: the metadata that combines them has broken, and reassembling that metadata requires specialized tools that work outside the original operating system.

The most important thing not to do is follow the standard troubleshooting advice that appears on Dell, HP, Intel, and Microsoft community forums. “Reset to non-Optane,” diskpart clean, fresh Windows installs, and Intel RST utility resets all do exactly what they say — destroy the existing data so the system can be set up fresh. If you’re past the point of wanting to boot the original Windows install and just need your files back, none of those steps will get you there.

If your Optane-equipped computer has stopped booting and the data on it matters, the safest move is to power the system off, remove the drive if possible, and have it evaluated before anything else is done. Recovery success on these is high when the drive arrives untouched.