This is more of a BeagleBone Black issue, but I'm finding that we're having a lot of problems getting Windows 10 computers to talk to the BeagleBone/Bela over USB. As in, most of our Windows 10 machines here are unable to do it at all (as a fallback, we've used the ethernet). Typically, the device is recognized with the standard bone_d64.exe drivers, but only as a nonfunctional comm device, and not as a network device.
This primarily is just for "fresh install" Windows 10 PCs. Those upgraded from Windows 7 seem to operate fine.
Anyone else encountered this, and have a good, robust solution for this?
I've worked through the various techniques mentioned in this article:
https://answers.microsoft.com/en-us/windows/forum/windows_10-networking-winpc/windows-10-vs-remote-ndis-ethernet-usbgadget-not/cb30520a-753c-4219-b908-ad3d45590447?auth=1
But most of these don't seem to work:
Replacement drivers, signed or unsigned, won't load since Windows 10 refuses the driver with a "you've already got the best driver" error. This is with or without booting in "unsigned driver" mode.
Editing rndiscmp.inf hasn't seemed to work, either, still loading the BBB as a (nonfunctioning) COM device.
Anyone gotten around this by changing how the BBB reports itself for RNDIS?