Forum Discussion

ketanbaitule's avatar
ketanbaitule
Copper Contributor
Jun 23, 2026

Multiple Namespace Detection in Windows NVMe Over TCP Initiator

We are evaluating the Windows NVMe Initiator and have observed an issue with namespace handling.

Our NVMe subsystem contains multiple namespaces. When we connect to the subsystem over TCP and establish connections to all namespaces, they are all shown as connected under the controller. However, only one namespace (shared block device) is exposed and accessible within Windows.

Based on our testing, it appears that the initiator may be mapping only the first namespace associated with a given Friendly Name. We were able to connect another subsystem, whose friendly name was different.

Questions:

  • Is support for multiple namespaces within a single subsystem currently available in the Windows NVMe Initiator?

  •  

    If so, are there any configuration requirements or known limitations related to namespace discovery and mapping?

  •  

    Is the initiator expected to expose all connected namespaces as separate disks within Windows?

We would appreciate any guidance or clarification on the expected behavior.

storage

1 Reply

  • Jamony's avatar
    Jamony
    MCT
    Jul 05, 2026

    Hi, I’d test with unique subsystem names, updated target firmware, and the latest Windows build available to you. If Windows still exposes only the first namespace, it may be a current initiator limitation or a bug in how the namespaces are being mapped. The most helpful thing to provide Microsoft would be your target config, connection commands, and screenshots of what Windows sees