I have been using the RNDIS feature of the USB port to allow my customers to connect to my PXA and T20 based systems for several years and it has been working very well. But I have run into problems when trying to support users of Windows 10.
The first problem was that Windows 10 will not allow unsigned drivers to be installed. I have solved that by buying a code signing certificate and using it to generate a signed .cat file from my .inf file.
The second problem is that Windows 10 thinks my product is a USB serial port when I first connect it and it loads the wrong driver. I can then click on the device in the device manager and browse to the correct driver and everything then works correctly. But I can’t have my customers go through a manual process like that.
The problem is described here on MSDN. The problem is that Windows 10 has a new default driver which is installed for USB\Class_02&SubClass_02 and the RNDIS interface of the T20 matches that class and subclass, so Windows 10 loads the USB serial port driver instead of the RNDIS driver.
I think a potential solution would be for the T20 to report a different subclass than 02 in order to force the PnP manager to search for a driver based on the USB PID and VID. I though the USB class and subclass might be specified in the T20 registry, but I can’t find them.
Has anyone else made the RNDIS feature work with Windows 10? I feel that I am very close, but I am also stuck!