
- #REMOTE NDIS DRIVER WINDOWS 10 NOT WORKING DRIVERS#
- #REMOTE NDIS DRIVER WINDOWS 10 NOT WORKING DRIVER#
However, starting with Vista (EDIT: probably Windows 8 as mentioned below), Windows has been enforcing a mandatory signing requirement for 64-bit drivers.
#REMOTE NDIS DRIVER WINDOWS 10 NOT WORKING DRIVER#
Windows has been shipping with the RNDIS driver bundled in for quite some time now, so it's basically a matter of a simple declaration. It is just a dummy driver that will tell the OS our "Linux USB Gadget" should be handled as a remote NDIS device. The solution is to provide a driver that will specifically handle USB\PID_0525&VID_A4A2.
#REMOTE NDIS DRIVER WINDOWS 10 NOT WORKING DRIVERS#
With some quick googling, it seems some VM users do not encounter this issue, perhaps because the class / subclass pair is tampered when it is presented to the guest?Īnyway, as a consequence, if you try to update its drivers, Windows will only show compatible drivers i.e. This is why for some people, their device is initially detected as a COM port instead of RNDIS. The Linux rndis gadget function has USB class of 2 and subclass of 2, which matches "USB\Class_02&SubClass_02" in the usbser.inf file. Note : please +Karma if you found this post useful! You should see a new network card Kindle USB RNDIS Device (USBNetwork enabled) in "Network and Sharing Center" > Change adapter settings. * You should not run random batch files from untrusted parties usually Browse for my computer for driver software > Select extract folder.In Device Manager, expand "Ports (COM & LPT)", R-click "Serial USB device (COM3)" > Update Driver Software.

