Fix: Storage Spaces Can't Add a New Drive, Error 0x00000032

The Frustrating Version of This Bug

I added an SSD to an existing Storage Spaces pool and Windows refused it: error 0x00000032. The drive showed up in Disk Management, looked healthy, and had never been used.

What I tried, and what did not work:

  • Reset Disk
  • Quick format, then full format
  • Offline, then online
  • Re-initialise the disk
  • chkdsk

None of them touched it, because none of them address the actual reason. Windows knows exactly why it will not pool the disk, and it will tell you if you ask the right question.

A photorealistic shot of a laptop screen showing a Windows Storage Spaces error dialog, a new SSD sitting on the desk beside a SATA cable, warm lamp light, realistic photography, no legible text.

Ask Windows Why

Open PowerShell as administrator and look at the physical disks:

Get-PhysicalDisk | Format-List

That returns a lot. Narrow it to the offending disk by friendly name:

Get-PhysicalDisk -FriendlyName "YourDiskName" | Format-List

Then ask the two fields that matter:

Get-PhysicalDisk -FriendlyName "YourDiskName" | Select-Object CanPool, CannotPoolReason

CanPool should be True. CannotPoolReason is the answer you have been guessing at.

Mine said "Insufficient space" on a brand-new 500 GB SSD added to a pool with terabytes free, which is genuinely funny until you understand what it means: this is not about free space in the pool. It means the disk itself does not have the space Storage Spaces needs, because it already carries partition or signature data — usually from a previous life in another machine, or from the manufacturer's test partition.

The Reasons You Will Actually See

CannotPoolReason What it means Fix
Insufficient space disk has existing partitions or signatures clear it (below)
Not eligible wrong bus type, or a USB-attached disk use SATA/NVMe; USB is not poolable
In a pool already a member of another pool remove it from that pool first
Offline disk is administratively offline Set-PhysicalDisk -Usage AutoSelect or bring it online
Sector size mismatch 4Kn disk in a 512e pool use a matching disk

The "Not eligible" one catches people who bought a USB enclosure to avoid opening the case. Storage Spaces will not pool a USB disk, at all.

Clearing the Disk

If the reason is leftover partitions or signatures, clear the disk. This erases it. Confirm you are pointing at the right disk before you run anything.

Get-Disk

Find the disk number by size and model — not by guessing. Then:

Clear-Disk -Number 3 -RemoveData -RemoveOEM -Confirm:$false

-RemoveData wipes partitions, -RemoveOEM removes the manufacturer's recovery partition that is usually the actual obstacle. Then bring it back into service:

Initialize-Disk -Number 3
Get-PhysicalDisk -FriendlyName "YourDiskName" | Select-Object CanPool, CannotPoolReason

CanPool should now read True.

If Clear-Disk refuses because the disk is claimed by a pool, the alternative is diskpart:

diskpart
list disk
select disk 3
clean
exit

clean is blunt and total. It is also the fastest way out when PowerShell declines to touch a disk that already belongs to a stale pool.

A photorealistic close-up of a PowerShell console window showing disk commands and a table of results, a tower PC with its side panel off in the background, realistic photography, no legible text.

If It Was in Another Pool

A disk that belonged to a previous pool carries a pool signature and will refuse to join a new one, even after a clean. The tidy fix is to remove it from the old pool first rather than wipe it:

Get-StoragePool
Get-PhysicalDisk | Where-Object {$_.CanPool -eq $false} | Select FriendlyName, CannotPoolReason

If the old pool still exists and is healthy, Remove-PhysicalDisk from it. If the pool is gone but the signature remains, Reset-PhysicalDisk clears the metadata:

Reset-PhysicalDisk -FriendlyName "YourDiskName"

That is the one command from my original list that was actually relevant, and only for this case — it does nothing for a disk with ordinary partitions on it.

A photorealistic shot of an open desktop PC case with two SSDs mounted in a drive cage and SATA cables routed neatly, a screwdriver on the bench, workshop lighting, realistic photography, no legible text.

After It Joins

Two things worth doing once the disk is in the pool.

Check the pool's resilience. If you are adding capacity to a pool with a two-way mirror, the new disk needs to be the same size or larger than the others to be fully usable; a smaller disk will join and contribute less than you expect.

Let it rebalance. Storage Spaces does not redistribute data immediately. Expect a period of elevated disk activity while it optimises. Do not pull a disk out during that window.

The Lesson

Error 0x00000032 is not an error about your pool, it is an error about the disk, and Windows always knows which condition it is refusing on. CannotPoolReason turns a guessing game into a two-command diagnosis — and it would have saved me the formatting and re-initialising entirely.

Check the reason before you touch the disk. Everything I tried first was destroying data to solve a problem that was not about data.

Don't trust the download button. Trust the hash.

If this was useful, More hands-on tech guides at TechGeek. No pressure — read it whenever it's useful.


Luke Keam
Spot a bug or want a custom utility built? I'd love to hear from you. Get in touch
Luke Keam | techgeek.biz