Windows 10 vs Remote NDIS - Ethernet USB/Gadget not recognized

Workaround for Windows 10:

1. Look which .inf Files the Hardware you want install take. (By my EV3 Brick it was the usbser.inf)

2. Save the usbser.inf Files. You can find this Files with Windows Search. (Offline Boot CD)

3. Remove this Files. You need a third Party Programm. (Offline Boot CD)

4. Plug the Hardware in and Windows will find no Driver.

5. Now you can install over the DeviceManager the right Driver.

6. Copy the Files back.

I hope this will Help.

Thany you @dlech for providing those solutions. I have backported the os descriptors from Solution 2 to kernel 3.14 and was able to use the adapted Lego scripts on my own device.

If you want try the solution3 with already signed driver. It works for me.

source :http://www.mobileread.com/forums/showthread.php?p=3283986

----

1. Download & Unzip attachment kindle_rndis.inf_amd64-v1.0.0.1.zip
2. R-click "5-runasadmin_register-CA-cer.cmd" and "Run as administrator"*
3. In Device Manager, expand "Ports (COM & LPT)", R-click "Serial USB device (COM3)" > Update Driver Software...
4. Browse for my computer for driver software > Select extract folder

How do you add "USB\Class_02&SubClass_02&Prot_FF" to rndiscmp.inf ?

Just add a line with "USB\Class_02&SubClass_02&Prot_FF" ?

In which folder?

Hi,

This post has already aged. I highly suggest you to create a new thread and kindly put the right tagging and the information needed for us to assist you better.

Regards.

Hello all,

This is quite n intriguing problem with interfacing open hardware using RNDIS with Win 10. The best solution that helped me with minimal stress was found here:

http://developer.toradex.com/knowledge-base/how-to-install-microsoft-rndis-driver-for-windows-7

It basically entailed going to your device manager, right-clicking on the unrecognzed RNDIS device and clicking on "update software/driver". Then instead of automatically searching or indicating the driver location, click on the option that allows you to select the kind of device that is to be driven. Among the options available in the pop-up menu, select "Microsoft" as the manufacturer and "RNDIS Network compatible device/adapter" and click "next". The process is described step by step in the weblink pasted above.

Note that it may be glitchy on first run ad fail to install/drive the first time, returning a time-out error, it worked licke a charm the second time I tried it.

Cheers!