Windows 10 NVMe Set Feature HCTM returns ERROR_INVALID_FUNCTION

Question

Windows 10 NVMe Set Feature HCTM returns ERROR_INVALID_FUNCTION

Florian Leskovsek 20

As per Microsoft documentation, the NVMe Set Feature HCTM command is supported in Windows 10, beginning with 19H1 as stated here https://learn.microsoft.com/en-us/windows/win32/fileio/working-with-nvme-devices#protocol-specific-set

However, when I try to execute it on a Windows 10 Pro 22H2, the DeviceIoControl call with IOCTL_STORAGE_SET_PROPERTY fails. GetLastError returns 0x1 (ERROR_INVALID_FUNCTION).

I have also tried different features, all with the same error, so it must be an issue with the IOCTL IOCTL_STORAGE_SET_PROPERTY itself.

On Windows 11 it works fine.

So, what is going on? Is the documentation wrong or did some StorNVMe driver update break it?

Answer accepted by question author

0 additional answers

Your answer

Answer 1

Jack Dang (WICLOUD CORPORATION) 15,205 Microsoft External Staff Moderator

Hi @Florian Leskovsek ,

Thanks for reaching out.

The HCTM (Host Controlled Thermal Management) command you’re trying to use is supported in Windows, but in practice, it depends on the StorNVMe driver that comes with your OS. On Windows 11, the driver has been updated to fully understand the HCTM command, which is why your DeviceIoControl call succeeds there.

On Windows 10 Pro 22H2, even though the documentation says HCTM is supported, the default driver may not implement that command yet. That’s why you’re seeing ERROR_INVALID_FUNCTION, the OS is essentially telling your NVMe drive, “I don’t know how to do that yet.”

A few things you can try:

Check for Windows updates - there may be a driver update for StorNVMe that adds HCTM support.
Check your NVMe driver version - if your manufacturer provides a newer driver for Windows 10, installing that may resolve the issue.
If immediate support for HCTM is critical, Windows 11 has built-in support and works out of the box.

Hope this helps! If my answer was helpful - kindly follow the instructions here so others with the same problem can benefit as well.

Deleted

This comment has been deleted due to a violation of our Code of Conduct. The comment was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.
Florian Leskovsek 20 Reputation points

2026-03-02T06:48:04.7666667+00:00

Why was my comment deleted?
Florian Leskovsek 20 Reputation points

2026-03-02T06:57:49.7466667+00:00

Well then, here we go again.

My system is the latest Windows 10, no updates available (also not optional drivers):

Edition Windows 10 Pro

Version 22H2

Installed on ‎27/‎02/‎2026

OS Build 19045.6456

The StorNVMe driver in use: 10.0.19041.4355

I think the Microsoft documentation is misleading/confusing regarding the support for NVMe Set Feature command.

On this page https://learn.microsoft.com/en-us/windows/win32/fileio/working-with-nvme-devices it states that Windows 10 19H1 and later has support for the IOCTL_STORAGE_SET_PROPERTY.

Also here https://learn.microsoft.com/en-us/windows-hardware/drivers/storage/stornvme-command-set-support?source=recommendations it states that for "Set Feature", the StorNVMe supports it on Windows 10 version 1903 and later. It also has a comment saying "Currently only supports Host Controlled Thermal Management".

According to the documentation, the default Windows NVMe driver should support it. In practice, however, it does not work.
Jack Dang (WICLOUD CORPORATION) 15,205 Reputation points Microsoft External Staff Moderator

2026-03-02T10:17:33.4566667+00:00

Hi @Florian Leskovsek ,

Thanks for sharing the full OS and driver details.

Windows 10 1903+ does support IOCTL_STORAGE_SET_PROPERTY, and the StorNVMe page mentions HCTM support. However, supporting the IOCTL interface does not always mean every NVMe Set Feature path is fully implemented in all Windows 10 driver builds.

On Windows 10 (including 22H2), the StorNVMe driver is still based on the 19041 branch. In some cases, the HCTM Set Feature request can return ERROR_INVALID_FUNCTION, which indicates the driver does not implement that specific path for the current environment.

The fact that the same code works on Windows 11 suggests the newer storage stack there includes more complete NVMe feature handling.

Your system is fully updated, and there’s no issue with your code. This behavior is due to driver capability differences between Windows 10 and Windows 11.

If HCTM Set Feature support is required, Windows 11 or a vendor-specific NVMe driver would be the recommended path.
Florian Leskovsek 20 Reputation points

2026-03-04T07:48:50.31+00:00

@Jack Dang (WICLOUD CORPORATION)

Thanks for the help, appreciate it.

I just find it very confusing to read the official documentation that mentions support exists theoretically, but not in practice.

PS: do you have any resources to share if I would want to develop my own custom NVMe driver, just to issue NVMe admin commands?
Jack Dang (WICLOUD CORPORATION) 15,205 Reputation points Microsoft External Staff Moderator

2026-03-04T09:06:52.09+00:00
Hi @Florian Leskovsek ,

If your goal is to build tooling or your own driver that can issue NVMe admin commands directly, here are some resources and starting points you might find helpful:

The official NVMe admin command definitions in the Windows API: https://learn.microsoft.com/en-us/windows/win32/api/nvme/ne-nvme-nvme_admin_commands

Sample tooling on GitHub that demonstrates issuing NVMe admin commands via the inbox driver.

The xNVMe project’s Windows backend, which illustrates how to use passthrough IOCTLs to issue both admin and I/O commands.
Florian Leskovsek 20 Reputation points

2026-03-04T10:25:57.63+00:00

@Jack Dang (WICLOUD CORPORATION)

Thank you for your help.

However, I already did development using the NVMe passthrough mechanism (via https://learn.microsoft.com/en-us/windows/win32/api/winioctl/ni-winioctl-ioctl_storage_protocol_command) and the problem is it only allows vendor-specific commands but not standard admin/io commands. For example, a Get Identify Controller command fails. Usually what happens is that GetLastError() returns error ERROR_MR_MID_NOT_FOUND (0x13D).

That is also the reason I ended up having to use other IOCTLs like the IOCTL_STORAGE_SET_PROPERTY for changing HCTM.

I just don't understand why standard NVMe commands are blocked and I am forced to use custom IOCTLs, which also do not work depending on the StorNVMe driver build.

So I am left with having to write a custom NVMe driver.
Jack Dang (WICLOUD CORPORATION) 15,205 Reputation points Microsoft External Staff Moderator

2026-03-04T10:49:08.87+00:00

Hi @Florian Leskovsek ,

I totally get wanting to dig into this, it can be really frustrating.

One perspective: the inbox driver is designed for stability and compatibility, so Windows blocks some admin commands by design. It’s not ideal for development work like yours, but it’s how the system stays safe.

Really appreciate you walking through this so carefully.

If you have new questions in the future, feel free to post them on this platform and I'm happy to support.

Share via

Windows 10 NVMe Set Feature HCTM returns ERROR_INVALID_FUNCTION

0 additional answers

Your answer