Alright, THAT did the trick. I now see the 10 LUNs provisioned to the host. If possible, in future releases, it would be great have this be either dynamic or at least set to a logical limit in line with the underlying operating system. Windows supports 26 lettered volumes by default, with 2 typicall...

The value was not in that location either, but I added it, rebooted, disconnected all paths and reconnected. Unfortunately, there is no change...still 8 LUNs connected out of 10.

Nope, confirmed that disconnecting all and reconnecting (following registry change + reboot) has no effect on LUNs connected. Still limited to 8. StarNVMeoF Controller Application v 2.0.0.672 Our Miniport #2 (ver 2.0 build 672) HostId 7958DA786AF086D7-A86FE9ADF955F16E, HostName a09-23 NET_LUID: 0x60...

Okay, I have done as suggested and the system comes up with the same 8 drives. Please see the attachment and let me know if this is correct.

Must I disconnect all paths and reconnect in order to see the change?

Only "BusType" is available under Parameters.

Thank you for this guidance, but I don't see MaxNamespaces in the location you specified. If this is something I can create, please let me know if it goes in the root of the 000# folder and the value type (dword, etc)

I have presented 10 LUNs from storage to my Windows 2019 initiator over RoCEv2, and while each connection is successful, it only sees 8 of the 10 volumes presented to the host from the array. Is this a Starwind Initiator limitation? Any settings I am overlooking which would unlock more volumes?