For more than a decade, Windows has forced modern NVMe solid-state drives to masquerade as legacy SCSI devices. This approach treats all storage devices as SCSI devices, a method traditionally used for older, slower drives. The translation layer introduced needless overhead. Now Microsoft is finally addressing it.
StorageReview has corroborated Microsoft's claims through independent testing, including higher read bandwidth with lower latency and decreased CPU usage across the board. Random read latency improved significantly, with 4K and 64K read times dropping by as much as 38.46% and 13.39%, respectively. In Microsoft's own testing, a system with 208 logical processors and a Solidigm NVMe device showed an approximately 80 percent increase in IOPS for 4K random read workloads on NTFS volumes when compared to Windows Server 2022.
The efficiency gains are equally compelling. The same test revealed a 45% reduction in CPU cycles per I/O operation, freeing computational resources for application workloads rather than storage overhead. For enterprises running databases, virtualisation platforms, or analytics workloads, that freed CPU represents tangible cost savings.
Yet beneath the performance headlines sits a sobering question: why did it take Windows 14 years to catch up? Windows users have been limited by Microsoft's outdated storage stack for almost a decade and a half, and it has been evident that it has struggled to keep pace with advances in SSD technology. Linux and VMware have offered native NVMe paths for years, while Windows Server releases stayed on the older stack.
The architectural problem was simple but consequential. SCSI-based I/O processing uses a single-queue model, originally designed for rotational disks, where protocols like SATA support just one queue with up to 32 commands, whereas NVMe was designed from the ground up for flash storage and supports up to 64,000 queues, with each queue capable of handling up to 64,000 commands simultaneously. By eliminating the need to convert NVMe commands into SCSI commands, Windows Server reduces processing overhead and latency.
Windows Server 2025's implementation arrives cautiously. Microsoft doesn't enable the driver by default; instead, it operates as an opt-in feature that Windows users need to enable via specific registry changes. Microsoft will first enable native NVMe by default in Windows Server vNext. The staged rollout reflects legitimate concerns about ecosystem readiness.
Third-party vendors present a genuine complexity. Some NVMe device vendors provide their own drivers, so unless using the in-box Windows NVMe driver, users will not notice any differences. Third-party tools, especially popular SSD management software like Samsung Magician or Western Digital Dashboard, aren't yet compatible and could malfunction. These compatibility issues explain why a wholesale default enablement remains risky.
Consumer Windows 11 users have discovered registry workarounds that unlock the same driver. Users hacking their way to run this on Windows 11 are seeing as much as an 85% improvement in random write speeds on the MSI Claw 8AI+, accompanied by a 12% uplift in random read speeds. However, such gains vary dramatically by hardware and workload; while the potential for improvement is massive, the impact on everyday hardware remains highly variable, and immediate speed doubling remains unlikely for the majority of consumer PCs.
For enterprises with strict validation requirements, the new driver offers genuine value, particularly in environments where storage IOPS per CPU core matters economically. SQL Server and online transaction processing databases experience shorter transaction times, higher IOPS, and lower tail latency under mixed read/write workloads. The CPU efficiency gains matter most at scale.
The question Microsoft faces is implementation pace. The opt-in rollout, community registry experiments, vendor driver variability, and early reports of feature interactions mean the path to broad adoption will be incremental. That gradualism may reflect prudent engineering, or it may reflect an organisation moving at a pace not entirely aligned with the technological realities its customers face.
For Australian IT leaders evaluating storage modernisation, the immediate takeaway is straightforward: if you run Windows Server 2025 with modern NVMe hardware using Microsoft's native driver, measurable gains are achievable. Testing in your own environment matters more than headline numbers. For consumer users, patience remains the sensible strategy; official support on Windows 11 will eventually arrive without the registry tweaks and compatibility risks that early adopters now face.