How to Fix Storage Spaces Drive Not Recognised in Windows 11

Windows 11 Storage Spaces provides software-defined storage redundancy by aggregating multiple physical hard drives or solid-state drives into a single unified storage pool. However, following a major Windows update, cable disconnection, or unexpected power outage, users may discover that an entire storage pool displays the status: “Degraded”, “Unrecognized metadata”, or lists member drives as “Disconnected – reconnect drive”. Understanding how Storage Spaces manages drive pool metadata allows you to repair the array without risking data loss.

Verify Physical Connections and SATA or USB Controllers

Before executing command-line storage repairs, eliminate physical connection dropouts:

  1. Shut down your computer completely.
  2. If the storage pool relies on internal SATA or NVMe drives, verify that SATA power and data cables are securely seated in both the drives and motherboard ports.
  3. If using an external multi-bay USB enclosure, avoid connecting through passive USB hubs. Plug the enclosure directly into high-speed USB 3.2 or USB4 ports on the motherboard rear I/O shield.
  4. Power on your PC, press the BIOS setup key (Del or F2), and verify that all physical drives appear in the motherboard firmware device list before Windows loads.

Inspect Storage Pool Status via PowerShell

The standard Windows 11 Settings app offers limited diagnostic feedback for degraded arrays. The native Windows Storage PowerShell module provides complete operational insight:

  1. Right-click the Start button and select Terminal (Admin) or PowerShell (Admin).
  2. Query all active storage pools on the machine:
    Get-StoragePool
  3. Inspect the OperationalStatus column. If it reads Degraded or Read-Only, note the friendly name of the pool.
  4. Query individual physical disks registered to the pool:
    Get-PhysicalDisk | Select-Object DeviceId, FriendlyName, OperationalStatus, HealthStatus, CannotPoolReason
  5. Review the OperationalStatus column for entries stating Lost Communication, Split, or Unrecognized Metadata.

Re-attach and Clear Read-Only Flags on Virtual Disks

When Windows 11 detects missing parity data during boot, it automatically marks virtual disks as read-only and detaches them to protect filesystem integrity:

  1. Query the virtual disks inside your storage pool:
    Get-VirtualDisk
  2. If the virtual disk is detached (IsManualAttach: True), re-attach it to the system:
    Get-VirtualDisk | Where-Object {$_.OperationalStatus -eq 'Detached'} | Set-VirtualDisk -IsManualAttach $false
  3. Attach the virtual disk:
    Get-VirtualDisk | Connect-VirtualDisk
  4. If the storage pool is marked read-only, unlock it with administrative authority:
    Set-StoragePool -FriendlyName "YourPoolName" -IsReadOnly $false

Repair Storage Pool Metadata via Repair-VirtualDisk

If physical drives were reconnected but Windows has not reconstructed parity tables, run an automated rebuild job:

  1. In PowerShell (Admin), execute:
    Repair-VirtualDisk -FriendlyName "YourVirtualDiskName"
  2. Monitor the progress of the rebuild job in real time:
    Get-StorageJob
  3. Allow the regeneration job to reach 100% completion. Do not disconnect drives or power off the workstation while the storage job is active.

Re-register Disks Using Reset-PhysicalDisk

If a healthy physical drive was temporarily disconnected and Storage Spaces rejects it due to an out-of-sync sequence counter, resetting the disk metadata flag restores pool membership:

  1. Identify the device ID of the unrecognised disk using Get-PhysicalDisk.
  2. Execute the physical disk reset command:
    Reset-PhysicalDisk -FriendlyName "PhysicalDiskX"
  3. Open the classic Storage Spaces control panel: press Windows Key + R, type control /name Microsoft.StorageSpaces, and press Enter.
  4. Click Change settings and verify that the drive status switches back to OK.

Get the best tech tips delivered straight to your inbox.

Join thousands of readers mastering Apple, Google, Microsoft, and Linux.