Fix Optane Memory Volume Stuck After Removing the Module on Windows 11

After physically removing an Intel Optane memory module from your PC, Windows 11 may still show the Optane volume as active in the Intel Rapid Storage Technology (IRST) application. The volume appears stuck, and you cannot delete it or reconfigure storage settings. This happens because Windows retains the logical volume configuration even after the hardware is gone, and the IRST driver does not automatically clean up the stale entry. This article explains why the volume gets stuck and provides step-by-step methods to remove it using Device Manager, Disk Management, and a registry edit.

Why the Optane Volume Stays Visible After Module Removal

Intel Optane Memory uses a special driver called iaStorA.sys, part of the Intel Rapid Storage Technology (IRST) driver suite. When you install an Optane module, Windows creates a logical volume that sits between the module and your primary drive. This volume is stored in the registry under the IRST driver parameters. Removing the physical module does not automatically delete the logical volume entry. The IRST driver continues to report the volume as present because the registry key remains untouched. The volume appears stuck in the Intel Optane Memory and Storage Management app and in Disk Management, and you cannot reformat or delete it through normal disk tools. The volume is also not visible in File Explorer, which makes the problem more confusing.

The root cause is that the IRST driver maintains a persistent cache of all Optane volumes at boot time. If the driver is loaded before the hardware change is detected, it holds onto the stale configuration. The driver does not have a built-in cleanup routine for removed modules. You must manually remove the driver binding and then delete the volume entry.

Steps to Remove the Stuck Optane Volume

Follow these steps in order. Do not skip the Device Manager step, because deleting the volume before removing the driver can cause the volume to reappear after a reboot.

Step 1: Uninstall the Intel Optane Driver from Device Manager

1. Open Device Manager
   Press Win + X and select Device Manager from the menu. Alternatively, open Settings > System > About > Advanced system settings > Device Manager.
2. Expand Storage controllers
   Click the arrow next to Storage controllers to show all storage-related devices. Look for Intel Optane Memory + System Acceleration or Intel Optane Memory.
3. Uninstall the device
   Right-click the Intel Optane device and select Uninstall device. In the confirmation dialog, check the box Delete the driver software for this device if available. Click Uninstall. Do not restart your PC yet.

Step 2: Delete the Stuck Volume in Disk Management

1. Open Disk Management
   Press Win + X and select Disk Management. You can also press Win + R, type diskmgmt.msc, and press Enter.
2. Locate the stuck Optane volume
   Look for a volume labeled Intel Optane Memory or a volume with no drive letter and a size matching your Optane module (usually 16 GB, 32 GB, or 64 GB). It may appear as a separate disk or as an unallocated space.
3. Delete the volume
   Right-click the volume and select Delete Volume. Confirm the action. The volume should now show as Unallocated.

Step 3: Restart and Verify

1. Restart your PC
   Click Start > Power > Restart. Do not use Shut down and then turn on manually, because Fast Startup may cache the old driver state.
2. Check Disk Management
   After the restart, open Disk Management again. The Optane volume should be gone, and the space should remain unallocated. You can now use that space for another purpose or leave it unallocated.

If the Volume Still Appears After the Main Fix

If the Optane volume reappears after following the steps above, the registry key that stores the volume configuration may need manual removal.

Delete the Optane Registry Key

1. Open Registry Editor
   Press Win + R, type regedit, and press Enter. Click Yes when prompted by User Account Control.
2. Navigate to the Optane key
   Go to: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\iaStorA\Parameters\IntelOptane. If the path does not exist, check under iaStorV instead of iaStorA.
3. Delete the volume entry
   In the right pane, look for a value named Volume0 or similar. Right-click it and select Delete. Confirm the deletion. Close Registry Editor.
4. Restart and verify
   Restart your PC and open Disk Management. The volume should no longer appear.

Volume Reappears After Each Boot

If the volume returns after every reboot, the IRST driver may be reinstalling itself through Windows Update. Disable automatic driver updates temporarily. Open Settings > Windows Update > Advanced options. Under Additional options, click Optional updates and uncheck any Intel Rapid Storage Technology driver. Then download the latest IRST driver from Intel’s website and install it manually. The new driver may clean up the stale entry automatically.

Removing Optane Module vs Disabling Optane Volume: Key Differences

Item	Remove Physical Module	Disable Optane Volume in Software
Description	Physically unplugging the M.2 Optane module from the motherboard	Using Intel Optane Memory and Storage Management app to disable acceleration
Effect on volume	Volume stays in Windows until manually removed	Volume is automatically deleted and the module becomes a standard drive
Risk of data loss	Low if you only remove the module; volume is orphaned	None; the volume is cleanly unmounted
Recommended approach	Only if the module is faulty or you cannot boot	Always disable in software before physical removal

Conclusion

You can now remove a stuck Optane volume after physically removing the module by uninstalling the driver in Device Manager and deleting the volume in Disk Management. If the volume persists, delete the registry key under the iaStorA service parameters. To avoid this problem in the future, always disable the Optane volume using the Intel Optane Memory and Storage Management app before removing the hardware. The app sends a proper detach command that cleans up the logical volume and the driver state. This approach also prevents boot failures caused by a missing acceleration target.