14 Years Late: Windows Server Finally Gets Native NVMe Support

14 Years Late: Windows Server Finally Gets Native NVMe Support

Microsoft’s latest server update brings long-awaited I/O performance improvements, while taskbar flexibility remains missing in action

In a move that has left many IT professionals wondering “what took so long?”, Microsoft has finally introduced native NVMe support to Windows Server 2025—a full 14 years after the storage technology first emerged.

The feature arrives via the October cumulative update, promising dramatic performance improvements for administrators who have long worked around the operating system’s limitations.

The Most Windows-Friendly Linux Distributions for General Consumers: A Complete Guide

The Performance Breakthrough (With Manual Assembly Required)

For Windows Server administrators, this represents a genuine leap forward in storage performance. Previously, even when equipped with high-performance NVMe SSDs, Windows Server systems had to translate I/O requests into SCSI bus commands—a conversion process that created significant performance bottlenecks.

However, there’s an important caveat: while the feature is now built into the operating system, it’s not enabled by default. Administrators must manually activate it through registry modifications or by installing a group policy package (MSI). This extra step may seem inconvenient, but it reflects Microsoft’s cautious approach to rolling out fundamental infrastructure changes.

According to Microsoft’s engineering team, supporting NVMe required completely redesigning the system’s I/O processing pipeline. Beyond raw performance gains, the company optimized the I/O locking mechanism to reduce latency and round-trip response times across the board.

What is the best alternative to Microsoft Office?

Impressive Benchmark Results

Microsoft’s internal testing used a robust configuration: a system with 288 logical cores, 128GB of memory, and Solidigm D7-PS1010 3.5TB PCIe 5.0 SSDs. The results comparing Windows Server 2025 with NVMe enabled against Windows Server 2022 were striking:

Random IOPS performance improved by up to 45% with a single I/O thread
With 8 threads, performance jumped by an impressive 78%
Even at 16 threads, gains reached 71%
In 4K random read scenarios, CPU utilization dropped by 41% at 8 threads and 47% at 16 threads

Replacing Microsoft Outlook on Linux: The Best Email Clients Compared

Real-World Results Vary

Despite Microsoft’s promising benchmarks, early adopter experiences have been mixed. Some users report no noticeable changes, while others suggest that only PCIe 5.0 NVMe SSDs can fully leverage the new I/O stack’s advantages. Interestingly, some users have even reported performance regressions with certain Western Digital SSDs, highlighting the complexity of storage performance optimization.

This inconsistency may explain why Microsoft hasn’t yet brought the feature to Windows 11. With the consumer SSD market featuring countless brands and products of varying quality, the company likely needs to conduct more extensive testing before a broader rollout.

Why servers with Linux OS are much more than Windows server?

Meanwhile, the Taskbar Saga Continues

While server administrators celebrate their NVMe victory, Windows 11 users remain frustrated by a much simpler missing feature: the inability to move the taskbar to the top or sides of the screen—something Windows 10 users took for granted.

According to Windows Latest, Microsoft actually addressed this issue in an “Ask Microsoft Anything” (AMA) session shortly after Windows 11’s launch. Tali Roth, the product manager responsible for Windows core user experiences including the Start menu, taskbar, and notifications, offered a surprisingly candid explanation: Windows 11’s taskbar was completely rewritten from scratch, without carrying over Windows 10’s legacy code. The functionality to move the taskbar simply doesn’t exist in the current codebase.

Roth explained that building the taskbar from the ground up meant the team had to prioritize features for over a billion users, focusing first on capabilities that the majority rely upon. According to Microsoft’s internal data, the percentage of users who move their taskbar to the top or sides of the screen is extremely small—not enough to justify prioritizing this feature over other demands.

Why is it difficult for viruses to “infect” Linux OS?

The Data Dilemma

However, this explanation raises questions. In Microsoft’s own Feedback Hub, requests to restore taskbar positioning have consistently ranked among the top user demands. Windows Latest pointedly asks: which dataset is Microsoft actually relying on to conclude this is a minority need?

From a technical perspective, Roth noted that keeping the taskbar at the bottom allows both the operating system and third-party applications to reliably predict available horizontal space for interface elements and interaction logic. Moving the taskbar to the left or right breaks these “spatial assumptions,” requiring applications to recalculate layouts, adjust content sizing, modify window snapping behavior, and adapt to various screen sizes, DPI settings, and multi-monitor environments—all while maintaining compatibility with traditional Win32 apps, modern UWP applications, and everything in between.

Microsoft argues that avoiding visual misalignment and errors across all these scenarios would require enormous engineering resources, which their internal assessment suggests isn’t justified by the number of active users who would benefit.

Why Windows 10 Users Are Flocking to Zorin OS 18 Instead of Linux Mint?

The AI Priority Paradox

Ironically, Microsoft’s stated commitment to “serving the majority of users” contrasts sharply with recent taskbar modifications, which have largely centered on AI features—changes that have frequently provoked user complaints rather than appreciation.

As Windows continues evolving, these two stories illustrate an ongoing tension in Microsoft’s development priorities: groundbreaking improvements in specialized areas like server storage performance, alongside persistent gaps in basic user interface flexibility that many consider fundamental. Whether Microsoft will eventually address the taskbar issue—or if Windows 11 users will need to wait another four years for such changes—remains to be seen.

14 Years Late: Windows Server Finally Gets Native NVMe Support