Hi everyone, novice sysadmin here looking into this in my homelab during my free time from work
I wanted to share a critical undocumented change (or potential API bug) I’ve encountered while deploying a cold data pool on Windows Server 2025, which completely breaks traditional ReFS performance optimizations that worked flawlessly in Windows Server 2022.
The Goal:
Deploying a 5-disk mechanical drive array in RAID 5 (Parity) using Storage Spaces.
(Before the Ryan Reynolds “But why?” meme drops in the comments: Yes, I know spinning rust and Storage Spaces parity isn’t the most glamorous setup for a homelab. However, this is the exact stack our organization is thoroughly used to at work, and I wanted to replicate it here to squeeze every bit of performance out of it!)
To prevent Read-Modify-Write (RMW) penalties and Write Amplification, the objective is to align the Stripe Data Width perfectly with the maximum ReFS Allocation Unit Size (64KB).
With 5 columns, we have 4 data columns (5 - 1 parity). In Windows Server 2022, setting -Interleave 16KB resulted in:
4 columns x 16KB interleave = 64KB stripe data width
This matched the 64KB ReFS AUS beautifully, providing atomic writes and native performance on spinning rust.
The “You shall not pass (this command, I might add)” problem in Windows Server 2025:
When executing the exact same deployment command in WS 2025, the StorageWMI provider throws a Not Supported error:
New-VirtualDisk -FriendlyName “RAID 5 Cold Data” -StoragePoolFriendlyName “RAID 5 Constellation” -Interleave 16KB -UseMaximumSize -ResiliencySettingName Parity -NumberOfColumns 5
New-VirtualDisk : Not Supported
Activity ID: {45a547e2-fce9-0006-8a48-a545e9fcdc01}
At line:1 char:1
- New-VirtualDisk -FriendlyName “RAID 5 Cold Data” -StoragePoolFriendly …
+ CategoryInfo : InvalidOperation: (StorageWMI:ROOT/Microsoft/...SFT_StoragePool) [New-VirtualDisk], CimException + FullyQualifiedErrorId : StorageWMI 1,New-VirtualDisk
The Inconsistency: Fixed vs. Thin
After extensive testing, I found a bizarre discrepancy in the API validation logic:
- If you create the Virtual Disk as
-ProvisioningType Fixed(or leave it default/maximum size), it strictly rejects any Interleave value below 64KB. - However, if you explicitly change the command to
-ProvisioningType Thin, the API happily accepts-Interleave 16KB(or lower) without throwing any errors.
This proves that the underlying storage architecture is technically capable of handling a 16KB interleave on the parity engine, but Windows Server 2025 is enforcing an undocumented API restriction specifically on Fixed disks. Forcing a minimum 64KB interleave on a 5-column fixed layout increases the Stripe Data Width to 256KB, resulting in heavy RMW performance degradation for standard 64KB ReFS clusters.
How to help:
I have already filed a high-priority feedback report directly to the Microsoft Core Storage engineering team. My organization is seriously considering dropping Windows Server entirely for our data storage if this isn’t addressed, as we cannot deploy our planned ReFS architecture.
If you are running Windows Server 2025 in your lab or enterprise environment, could you please try to replicate this behavior? If you want this feature back, please upvote my feedback report on the Feedback Hub using this link: https://aka.ms/AA11tvzr (Note: You need a Windows machine with Feedback Hub installed to open this link).
Has anyone found a clean registry bypass or workaround for this validation lock on W. S. 2025 Storage Pools?
P.S: To all the Proxmox + ZFS on TrueNAS enthusiasts out there: if “Microslop” (we all know we hate them for many reasons, and more) decides not to fix this issue, we will fully transition to ZFS in the end and become “part of the ship, part of the crew”.
Thanks in advance!