Windows 11 NVMe ‘block’ might not be a block after all – here’s what’s really going on

• Windows 11 includes a native NVMe driver (nvmedisk.sys), but it’s disabled by default.
• Enthusiasts enabled it via registry tweaks and reported better performance and lower latency.
• New preview builds appear to break the tweak, leading to claims Microsoft “blocked” it.
• According to some people, this is likely due to a feature ID change, not a deliberate restriction.

Microsoft appears to have shut down a popular Registry tweak that unlocked faster NVMe performance on Windows 11, but the situation is more complicated than it looks.

Recent preview builds seem to stop users from forcing the system to load the native NVMe driver, nvmedisk.sys. When enabled, some users reported better responsiveness, lower latency, and noticeable performance gains in storage-heavy tasks. The driver is already included on Windows 11, but it’s turned off by default, even as Windows Server 2025 already supports it natively.

At first, it looked like Microsoft had closed a loophole that let enthusiasts push their hardware further. That idea spread quickly, sparking frustration and raising questions about why a modern operating system still relies on an older storage path. But that may not be the full picture.

According to @PhantomOfEarth, this might not be a deliberate block. The operating system relies on feature IDs to control how features are tested and rolled out, especially in preview builds. When those IDs change, tweaks tied to them can stop working without warning. In other words, what looks intentional could just be a side effect of normal development.

That detail hasn’t stopped the backlash. Some users point to real issues with the tweak, including problems with SSD tools, disk detection, and encryption features. From that view, keeping the feature disabled is about avoiding instability across a wide range of hardware.

Others are more critical. For them, this reinforces the idea that Windows 11 is becoming more restrictive. Questions about why the feature isn’t enabled, or why it exists in one version but not another, quickly turn into speculation about limitations or delayed rollouts. Whether those claims are accurate matters less. The perception gap is growing.

Part of the problem is that both sides are working with limited information. Microsoft hasn’t said when native NVMe support will arrive on Windows 11, even though the technology is already there. At the same time, enthusiasts continue to uncover hidden features using unofficial methods, often without the full context. When those methods stop working, it’s easy to assume something was taken away.

In reality, this looks more like a matter of timing than Microsoft blocking a feature. The presence of the driver suggests the company is still working on broader NVMe improvements, but isn’t ready to roll them out widely. Changes at this level can affect compatibility, recovery, and system stability, especially across millions of different devices.

However, the way these features are handled creates confusion. Microsoft ships them hidden and controls them through internal flags, while users try to unlock them early. When something breaks, the lack of clear communication leaves room for assumptions.

Whether this was intentional or not, the result is the same. It reinforces the sense that Windows 11 is evolving behind the scenes with little transparency.

Until Microsoft is clearer about what’s coming and why it’s being held back, even routine changes will continue to feel like something bigger.