For months, power users and system builders had a workaround. A simple registry edit could unlock native NVMe performance on Windows 11, bypassing a software bottleneck that Microsoft had seemingly ignored. That workaround is now dead.
Microsoft’s latest Windows 11 update — KB5058405, part of the May 2025 cumulative patch — has quietly neutralized the registry hack that allowed users to disable the inbox Microsoft StorPort driver in favor of the device manufacturer’s native NVMe driver. The result: millions of high-end NVMe drives are once again running below their potential, throttled by a driver layer that independent benchmarks have repeatedly shown to be slower than what Samsung, Western Digital, and other manufacturers provide, as first reported by Tom’s Hardware.
The implications stretch far beyond hobbyist PC builders. Enterprise workstations, content creation rigs, and data-intensive workloads all stand to feel the drag. And Microsoft hasn’t offered a public explanation for why it closed the door.
The story begins with a problem that has festered since Windows 11’s early days. Microsoft’s built-in StorPort NVMe driver — the default handler for virtually all NVMe solid-state drives — has consistently underperformed compared to vendor-supplied drivers. Samsung’s own NVMe driver, for instance, has shown measurably better sequential and random I/O performance on drives like the 990 Pro and 990 Evo Plus. The gap isn’t trivial. In some configurations, users reported double-digit percentage improvements in sustained write speeds and queue-depth performance when switching from the Microsoft driver to the manufacturer’s version.
The technical explanation is straightforward. Microsoft’s inbox StorPort driver is designed to be universally compatible. It works with every NVMe drive on the market. But that universality comes at a cost: it doesn’t take advantage of device-specific optimizations that manufacturers bake into their own drivers. Features like advanced thermal throttling management, firmware-level command queuing optimizations, and host memory buffer tuning are left on the table when the generic driver is in control.
Earlier this year, a registry workaround surfaced in enthusiast communities and was widely shared across forums and tech publications. By modifying a specific registry key, users could force Windows 11 to load the manufacturer’s NVMe driver instead of the Microsoft default. The hack worked. Benchmarks confirmed it. And for a brief window, users who cared about storage performance had a viable solution.
That window has now closed.
Microsoft’s Patch Seals the Registry Path — With No Alternative in Sight
According to Tom’s Hardware, the May 2025 cumulative update specifically targets the registry path that the workaround relied on. After installing KB5058405, the registry modification no longer takes effect. Windows 11 reverts to the StorPort driver regardless of what the user has configured. The change appears deliberate — not a side effect of an unrelated patch.
Microsoft has not issued any documentation explaining the decision. No blog post. No support article. No acknowledgment that the performance gap exists in the first place. This silence is itself notable, given how vocal the company has been about other Windows 11 performance improvements in recent months, including DirectStorage optimizations and improvements to the NTFS file system.
The timing is particularly awkward. Just weeks before the patch dropped, Samsung had updated its own NVMe driver package and recommended that users install it for optimal performance on Windows systems. Western Digital’s Dashboard software similarly encourages users to install the WD-specific NVMe driver. These manufacturers clearly believe their drivers deliver better results than what ships with Windows. Microsoft’s patch effectively overrides that recommendation.
Community reaction has been sharp. On Reddit’s r/hardware and r/Windows11 forums, users have expressed frustration not just with the performance regression but with the lack of communication. “If Microsoft’s driver performed the same, nobody would care,” one highly upvoted comment read. “But it doesn’t, and they know it doesn’t, and they patched out the fix anyway.”
Some have speculated that the change is related to system stability concerns. The registry hack, while effective, was never officially supported. It’s possible that Microsoft encountered edge cases — blue screens, data corruption risks, or compatibility issues with certain drive models — that prompted the lockdown. But without an official statement, that remains speculation.
Others have pointed to a more strategic motive. Microsoft has been pushing its own storage stack hard in recent years, particularly with DirectStorage, which is designed to allow game assets to stream directly from NVMe drives to the GPU with minimal CPU overhead. Keeping all NVMe traffic flowing through the StorPort driver gives Microsoft a single, controlled pipeline to optimize. Third-party drivers, by definition, introduce variables that Microsoft can’t predict or test against.
There’s precedent for this kind of consolidation. Microsoft has progressively tightened control over driver installation in Windows 11, from requiring signed drivers to restricting certain kernel-level access. The NVMe driver lockdown fits a broader pattern of Microsoft preferring its own components over third-party alternatives, even when those alternatives perform better.
The performance data is hard to ignore. Independent testing by multiple outlets, including Tom’s Hardware, has shown that Samsung’s native NVMe driver delivers meaningfully better results in CrystalDiskMark, ATTO Disk Benchmark, and real-world file copy tests. Random 4K read and write performance — the metric that matters most for everyday system responsiveness — shows the starkest difference. In some tests, the Samsung driver outperformed the Microsoft driver by 15% or more at low queue depths, which is the access pattern most representative of typical desktop usage.
For enterprise customers, the stakes are even higher. Database servers, virtual machine hosts, and high-frequency trading platforms that rely on NVMe storage are acutely sensitive to I/O latency. Even small percentage improvements in random read performance can translate into measurable gains in transaction throughput. IT administrators who had deployed the registry fix across fleets of workstations now face a choice: delay the security update to preserve storage performance, or accept the regression.
That’s not a choice anyone should have to make.
Security patches and performance shouldn’t be in conflict. Yet here they are. KB5058405 includes fixes for multiple security vulnerabilities, some rated critical. Skipping it to maintain NVMe performance is a genuine risk. But so is accepting a permanent performance penalty on hardware that cost hundreds — or thousands — of dollars.
The broader question is whether Microsoft will address the performance gap in its own driver. The company has the engineering resources to do so. StorPort is under active development, and Microsoft has made significant improvements to it over the years. But closing the gap with vendor-specific drivers would require Microsoft to either work more closely with NVMe manufacturers or implement device-specific optimizations in its generic driver — neither of which appears to be on the current roadmap.
There’s also the question of user choice. Windows has historically allowed power users to select their own drivers. The Device Manager still technically permits manual driver installation, but the May update ensures that the StorPort driver takes precedence for NVMe devices regardless. This erosion of user control is part of a larger trend in Windows 11 that has drawn criticism from advanced users who feel the operating system is increasingly designed for the lowest common denominator.
So where does this leave things? In the short term, users who depend on maximum NVMe performance are stuck. The registry workaround is gone, and no new bypass has emerged. Some users on enthusiast forums have reported experimenting with driver injection techniques and Group Policy modifications, but nothing reliable has surfaced yet.
In the medium term, pressure on Microsoft is building. Storage manufacturers have a financial incentive to push back — if their drives can’t perform to spec on the world’s most popular operating system, that’s a sales problem. Samsung and Western Digital both have the clout to escalate this behind closed doors. Whether they will is another matter.
And in the long term, this episode highlights a fundamental tension in modern operating system design. The push toward tighter integration and control — which Microsoft frames as improving security and reliability — inevitably collides with the needs of users who want to extract every last drop of performance from their hardware. Both goals are legitimate. But when Microsoft closes a performance loophole without offering an alternative, it sends a clear message about which priority wins.
For now, the fastest NVMe drives on the market are running with one hand tied behind their back on Windows 11. Microsoft has the key. It just isn’t sharing it.
WebProNews is an iEntry Publication