Fri Jul 24, 2026 3:08 pm
That's quite vague...
If the problem is related to MS or the storage provider, the appropriate case needs to be logged with them. If the limitation is on their side, there's little we can do. Say, if the storage does not support reservation and therefore cannot be clustered over NVMe-oF, there's nothing we as an initiator vendor can do because the root cause is third-party hardware.
While StarWind's scope of support is limited only to our products, during break-fix support, we will do our best to stabilize our solution if the issue has happened due to a third-party product (e.g., MS Hyper-V or MPIO acting up). As a side note, if you have an active support contract, we might also help with the Windows-related side of the setup, but this should not be viewed as a general rule.
As a side note, You can install the StarWind NVMe-oF initiator in Windows Server or a desktop OS. Be it virtualized or bare-metal.