USBArmory on Windows 10

[valerio-click]

Hi all,

I tried to plug USBArmory on a fresh new windows 10 installation but the RNDIS doesn't seem to work.
Windows sees that an USB device has been plugged but it doesn't bring up the eth device.

Any idea on how to troubleshoot this?

regards,
Valerio

[Andrea Barisani]

I guess the RNDIS driver is not included by default, can you try and install it (there is one thread in the group with instructions for win 7).

Or maybe someone else with a win10 box can help with tips as we don't have a win10 installation.

Cheers

> regards,
> Valerio
>
> --
> You received this message because you are subscribed to the Google Groups "USB armory" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to usbarmory+...@googlegroups.com.
> To post to this group, send email to usba...@googlegroups.com.
> To view this discussion on the web visit https://groups.google.com/d/msgid/usbarmory/e8d457ee-0c42-46f0-bd99-39c801023d5e%40googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.

[valerio-click]

Thank for the reply!!

I tried to mimic the procedure as reported in 

https://github.com/ev3dev/ev3dev/wiki/Setting-Up-Windows-USB-Ethernet-Networking

but in the update driver list I didn't find any RNDIS driver.

I tried to google how to download RNDIS drivers for Windows 10 without any result.

regards,

Valerio

[Peter Hultqvist]

Previously on Windows 8.1 the USB armory appeared in the Device Manager as an unknown RNDIS device, from there I had to manually go in and select the correct driver, every time I inserted the device.

Now with Windows 10 that device no longer appears. Instead I get a "Serial USB device(COM3)" which I don't know how to change the driver to the RNDIS driver.

[valerio-click]

The same scenario also for me!!

The USBArmory is seen as Serial USB device(COM3) and there is no network driver for an RNDIS device :-(

regards,

Valerio

[Andrea Barisani]

On 2 Aug 2015 9:19 pm, "valerio-click" <valeri...@gmail.com> wrote:
>
> The same scenario also for me!!
> The USBArmory is seen as Serial USB device(COM3) and there is no network driver for an RNDIS device :-(
>

We will try to get access to a win 10 box in the coming days (some of us are traveling/vacationing in August so we can't address this as quickly as we woud like).

If others have insights or suggestions they are most appreciated.

I am confident that win10 would not permanently break compatibility with RNDIS devices (which is a generic kind of support and not specific to the USB armory) and that one way or another we can sort this out.

Cheers

> To view this discussion on the web visit https://groups.google.com/d/msgid/usbarmory/fcb34756-092b-437b-b53b-ad619759d0a9%40googlegroups.com.

[Andrea Barisani]

On Saturday, August 1, 2015 at 12:13:01 PM UTC+2, valerio-click wrote:

Thank for the reply!!

I tried to mimic the procedure as reported in 

https://github.com/ev3dev/ev3dev/wiki/Setting-Up-Windows-USB-Ethernet-Networking

but in the update driver list I didn't find any RNDIS driver.

I tried to google how to download RNDIS drivers for Windows 10 without any result.

Once you "Update driver software" and select from "Browse my computer for driver software" and then "Let me pick from a list of device drivers on my computer", you will find the driver under "Network adapters" and "Microsoft".

Additionally, before doing this process, you can also try to install the Linux driver for windows from https://www.kernel.org/doc/Documentation/usb/linux.inf

Once installed it will place a driver under "Linux Developer Community" instead of "Microsoft".

Would it be possible for you to try this?

Thanks!

[Peter Hultqvist]

Den torsdag 6 augusti 2015 kl. 02:46:02 UTC+2 skrev Andrea Barisani:

On Saturday, August 1, 2015 at 12:13:01 PM UTC+2, valerio-click wrote:

Thank for the reply!!

I tried to mimic the procedure as reported in 

https://github.com/ev3dev/ev3dev/wiki/Setting-Up-Windows-USB-Ethernet-Networking

but in the update driver list I didn't find any RNDIS driver.

I tried to google how to download RNDIS drivers for Windows 10 without any result.

Once you "Update driver software" and select from "Browse my computer for driver software" and then "Let me pick from a list of device drivers on my computer", you will find the driver under "Network adapters" and "Microsoft".

It is different here since the device is already recognized as a serial port device.

I can right click and pick "Update driver...", "Pick driver already on my computer", "Let me pick from a list of device drivers on my computer".

But from here the dialog is different, there is no list for type of driver where I can choose. Instead I can only pick from serial USB drivers. Even if I uncheck "Show compatible hardware" the list is still limited to serial devices.

(note that all quoted paths above are my translations to English)

 

Additionally, before doing this process, you can also try to install the Linux driver for windows from https://www.kernel.org/doc/Documentation/usb/linux.inf

I tried to install it both directly by right clicking it and by picking it from the "Upgrade driver..." process but both failed because of a missing signature.

[Andrea Barisani]

On 5 Aug 2015 11:18 pm, "Peter Hultqvist" <hult...@silentorbit.com> wrote:
>
> Den torsdag 6 augusti 2015 kl. 02:46:02 UTC+2 skrev Andrea Barisani:
>>
>> On Saturday, August 1, 2015 at 12:13:01 PM UTC+2, valerio-click wrote:
>>>
>>> Thank for the reply!!
>>>
>>> I tried to mimic the procedure as reported in 
>>> https://github.com/ev3dev/ev3dev/wiki/Setting-Up-Windows-USB-Ethernet-Networking
>>>
>>> but in the update driver list I didn't find any RNDIS driver.
>>> I tried to google how to download RNDIS drivers for Windows 10 without any result.
>>>
>>
>> Once you "Update driver software" and select from "Browse my computer for driver software" and then "Let me pick from a list of device drivers on my computer", you will find the driver under "Network adapters" and "Microsoft".
>>
> It is different here since the device is already recognized as a serial port device.
> I can right click and pick "Update driver...", "Pick driver already on my computer", "Let me pick from a list of device drivers on my computer".
> But from here the dialog is different, there is no list for type of driver where I can choose. Instead I can only pick from serial USB drivers. Even if I uncheck "Show compatible hardware" the list is still limited to serial devices.
> (note that all quoted paths above are my translations to English)

We tried with a win10 installation today and the device was being recognised as CDC Composite Gadget.

Also we could install the Linux driver by giving permission to install the unsigned driver. We were also able to see the Microsoft RNDIS driver.

I am not sure why you see it as serial device, is the LED blinking (meaning a correct boot from microSD) ?

We were using a USB armory with Arch Linux and win10 virtualized on a Mac with VMWare.

The virtualization might make a difference here, so we will try to test on a native setup.

>  
>>
>> Additionally, before doing this process, you can also try to install the Linux driver for windows from https://www.kernel.org/doc/Documentation/usb/linux.inf
>>
> I tried to install it both directly by right clicking it and by picking it from the "Upgrade driver..." process but both failed because of a missing signature.
>
>  
>>
>> Once installed it will place a driver under "Linux Developer Community" instead of "Microsoft".
>>
>> Would it be possible for you to try this?
>>
>> Thanks!
>
>
>
>

> --
> You received this message because you are subscribed to the Google Groups "USB armory" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to usbarmory+...@googlegroups.com.
> To post to this group, send email to usba...@googlegroups.com.

> To view this discussion on the web visit https://groups.google.com/d/msgid/usbarmory/642384a8-85ba-4122-8606-f5067de7248e%40googlegroups.com.

[Peter Hultqvist]

Den torsdag 6 augusti 2015 kl. 09:07:35 UTC+2 skrev Andrea Barisani:

On 5 Aug 2015 11:18 pm, "Peter Hultqvist" <hult...@silentorbit.com> wrote:
>
> Den torsdag 6 augusti 2015 kl. 02:46:02 UTC+2 skrev Andrea Barisani:
>>
>> On Saturday, August 1, 2015 at 12:13:01 PM UTC+2, valerio-click wrote:
>>>
>>> Thank for the reply!!
>>>
>>> I tried to mimic the procedure as reported in 
>>> https://github.com/ev3dev/ev3dev/wiki/Setting-Up-Windows-USB-Ethernet-Networking
>>>
>>> but in the update driver list I didn't find any RNDIS driver.
>>> I tried to google how to download RNDIS drivers for Windows 10 without any result.
>>>
>>
>> Once you "Update driver software" and select from "Browse my computer for driver software" and then "Let me pick from a list of device drivers on my computer", you will find the driver under "Network adapters" and "Microsoft".
>>
> It is different here since the device is already recognized as a serial port device.
> I can right click and pick "Update driver...", "Pick driver already on my computer", "Let me pick from a list of device drivers on my computer".
> But from here the dialog is different, there is no list for type of driver where I can choose. Instead I can only pick from serial USB drivers. Even if I uncheck "Show compatible hardware" the list is still limited to serial devices.
> (note that all quoted paths above are my translations to English)

We tried with a win10 installation today and the device was being recognised as CDC Composite Gadget.

Also we could install the Linux driver by giving permission to install the unsigned driver. We were also able to see the Microsoft RNDIS driver.

I am not sure why you see it as serial device, is the LED blinking (meaning a correct boot from microSD) ?

We were using a USB armory with Arch Linux and win10 virtualized on a Mac with VMWare.

The virtualization might make a difference here, so we will try to test on a native setup.

I've in the past found a big difference with the ArchLinux and the Debian releases.

I would rather run ArchLinux but something made it identify as a completely different device that I could not get to work on both windows, mac and Linux so I ended up using the Debian version instead.

This was a year ago so it might have changed but to be sure you should still check with both images.

[valerio-click]

I tried on a fresh new Windows 10 host and I still got the USBArmory recognized as Serial USB device (COM 3).

best

Valerio

[Andrea Barisani]

On 6 Aug 2015 2:58 pm, "valerio-click" <valeri...@gmail.com> wrote:
>
> I tried on a fresh new Windows 10 host and I still got the USBArmory recognized as Serial USB device (COM 3).
>
> best
> Valerio
>

Can you confirm that this happens with Debian and that the LED was blinking (indicating successful boot) ?

Are you able to successfully use the board on other OSes?

Thanks

> To view this discussion on the web visit https://groups.google.com/d/msgid/usbarmory/6bdfdcc9-161b-4fed-a597-0c8faf617c84%40googlegroups.com.

[valerio-click]

Andrea,

On Friday, August 7, 2015 at 12:01:03 AM UTC+2, Andrea Barisani wrote:

On 6 Aug 2015 2:58 pm, "valerio-click" <valeri...@gmail.com> wrote:
>
> I tried on a fresh new Windows 10 host and I still got the USBArmory recognized as Serial USB device (COM 3).
>
> best
> Valerio
>

Can you confirm that this happens with Debian and that the LED was blinking (indicating successful boot) ?

yes

 

Are you able to successfully use the board on other OSes?

yes it works perfectly on Mac OS X, Linux and Linux on VM

best

Valerio 

[Andrea Barisani]

On 6 Aug 2015 3:08 pm, "valerio-click" <valeri...@gmail.com> wrote:
>
> Andrea,
>
> On Friday, August 7, 2015 at 12:01:03 AM UTC+2, Andrea Barisani wrote:
>>
>> On 6 Aug 2015 2:58 pm, "valerio-click" <valeri...@gmail.com> wrote:
>> >
>> > I tried on a fresh new Windows 10 host and I still got the USBArmory recognized as Serial USB device (COM 3).
>> >
>> > best
>> > Valerio
>> >
>>
>> Can you confirm that this happens with Debian and that the LED was blinking (indicating successful boot) ?
>
>
> yes
>  
>>
>> Are you able to successfully use the board on other OSes?
>
>
> yes it works perfectly on Mac OS X, Linux and Linux on VM
>

Ok thanks, I will get back to you once we get access to a non virtualized instance for testing later this month.

> To view this discussion on the web visit https://groups.google.com/d/msgid/usbarmory/9d215833-9f2a-4328-9238-d69a057ff26b%40googlegroups.com.

[Andrea Barisani]

On Friday, August 7, 2015 at 12:11:08 AM UTC+2, Andrea Barisani wrote:

On 6 Aug 2015 3:08 pm, "valerio-click" <valeri...@gmail.com> wrote:
>
> Andrea,
>
> On Friday, August 7, 2015 at 12:01:03 AM UTC+2, Andrea Barisani wrote:
>>
>> On 6 Aug 2015 2:58 pm, "valerio-click" <valeri...@gmail.com> wrote:
>> >
>> > I tried on a fresh new Windows 10 host and I still got the USBArmory recognized as Serial USB device (COM 3).
>> >
>> > best
>> > Valerio
>> >
>>
>> Can you confirm that this happens with Debian and that the LED was blinking (indicating successful boot) ?
>
>
> yes
>  
>>
>> Are you able to successfully use the board on other OSes?
>
>
> yes it works perfectly on Mac OS X, Linux and Linux on VM
>

Ok thanks, I will get back to you once we get access to a non virtualized instance for testing later this month.

Non virtualized environment still recognizes it as CDC Composite Gadget, however the driver (both Microsoft own one as well as Linux one installed by disabling driver signature verification) do not work as the device reportedly cannot "start".

This windows 10 bug is affecting all devices using Linux USB Ethernet Gadget and some tracking of it can be seen at the following URLs:

http://answers.microsoft.com/en-us/windows/forum/windows_10-networking/windows-10-vs-remote-ndis-ethernet-usbgadget-not/cb30520a-753c-4219-b908-ad3d45590447?auth=1

https://github.com/ev3dev/ev3dev/issues/376

We are going to get in touch with Microsoft and linux-usb-devel to see if we can sort this out.

Cheers

 

> best

> To unsubscribe from this group and stop receiving emails from it, send an email to usbarmory+unsubscribe@googlegroups.com.

[Andrea Barisani]

On Thursday, August 13, 2015 at 6:22:56 AM UTC+2, Andrea Barisani wrote:

On Friday, August 7, 2015 at 12:11:08 AM UTC+2, Andrea Barisani wrote:

On 6 Aug 2015 3:08 pm, "valerio-click" <valeri...@gmail.com> wrote:
>
> Andrea,
>
> On Friday, August 7, 2015 at 12:01:03 AM UTC+2, Andrea Barisani wrote:
>>
>> On 6 Aug 2015 2:58 pm, "valerio-click" <valeri...@gmail.com> wrote:
>> >
>> > I tried on a fresh new Windows 10 host and I still got the USBArmory recognized as Serial USB device (COM 3).
>> >
>> > best
>> > Valerio
>> >
>>
>> Can you confirm that this happens with Debian and that the LED was blinking (indicating successful boot) ?
>
>
> yes
>  
>>
>> Are you able to successfully use the board on other OSes?
>
>
> yes it works perfectly on Mac OS X, Linux and Linux on VM
>

Ok thanks, I will get back to you once we get access to a non virtualized instance for testing later this month.

Non virtualized environment still recognizes it as CDC Composite Gadget, however the driver (both Microsoft own one as well as Linux one installed by disabling driver signature verification) do not work as the device reportedly cannot "start".

This windows 10 bug is affecting all devices using Linux USB Ethernet Gadget and some tracking of it can be seen at the following URLs:

http://answers.microsoft.com/en-us/windows/forum/windows_10-networking/windows-10-vs-remote-ndis-ethernet-usbgadget-not/cb30520a-753c-4219-b908-ad3d45590447?auth=1

https://github.com/ev3dev/ev3dev/issues/376

We are going to get in touch with Microsoft and linux-usb-devel to see if we can sort this out.

Cheers

Good news!

Using Arch Linux I am able to connect with Windows 10 by changing g_cdc module to g_ethernet in the relevant files in /etc (/etc/modprobe.d/gadget-deadbeef.conf, /etc/modules-load.d/gadget-deadbeef.config). The same should be possible on Debian.

This might affect Mac OS X (I will test this) but it does not affect connectivity with a Linux host.

[Andrea Barisani]

I confirm that g_ether works fine with win7, win10, Linux and OSX. We will update the Debian image to include the module and update the wiki with some win10 tips later this month.

[Andrea Barisani]

I also confirm that the issue concerning g_cdc not being detected correctly by Windows 10 is limited to Arch Linux image default configuration, our Debian image uses g_ether and I just tested it as working correctly with a Windows 10 installation.

[ela...@gmail.com]

Just received my USB Armory, which is not showing up on Windows 10.

Using a Windows 7 computer, where it is working perfectly, I was able to check that it is using g_ether with debian. But when connecting on Windows 10 it keep showing as a "Serial USB device".

I did tried to install the Acer Driver but it seems to be unavailable now :

http://www.catalog.update.microsoft.com/ScopedViewRedirect.aspx?updateid=37e35bd4-d788-4b83-9416-f78e439f90a2

Any idea of what am i supposed to do get it work as it should on W10 ? I would like to get it work without installing an unsigned driver... if possible...

Thanks in advance.

[ela...@gmail.com]

Hello Again, short update : I found the Acer Driver (http://www.catalog.update.microsoft.com/Search.aspx?q=USB%20Ethernet%2FRNDIS%20Gadget) and installed it on Windows 10.

But as stated by Peter :

since the device is already recognized as a serial port device.
I can right click and pick "Update driver...", "Pick driver already on my computer", "Let me pick from a list of device drivers on my computer".
But from here the dialog is different, there is no list for type of driver where I can choose. Instead I can only pick from serial USB drivers. Even if I uncheck "Show compatible hardware" the list is still limited to serial devices.

Any idea on how to force this driver on the Serial USB Device ? 

Thanks in advance.

[Andrea Barisani]

On Wed, Jan 11, 2017 at 3:53 PM, <ela...@gmail.com> wrote:

Just received my USB Armory, which is not showing up on Windows 10.

Using a Windows 7 computer, where it is working perfectly, I was able to check that it is using g_ether with debian. But when connecting on Windows 10 it keep showing as a "Serial USB device".

I did tried to install the Acer Driver but it seems to be unavailable now :

http://www.catalog.update.microsoft.com/ScopedViewRedirect.aspx?updateid=37e35bd4-d788-4b83-9416-f78e439f90a2

Any idea of what am i supposed to do get it work as it should on W10 ? I would like to get it work without installing an unsigned driver... if possible...

Thanks in advance.

Could you try downloading any Acer driver from this list and see if any works for you?

http://www.catalog.update.microsoft.com/Search.aspx?q=USB%20RNDIS%20Gadget

Thanks

 

To unsubscribe from this group and stop receiving emails from it, send an email to usbarmory+unsubscribe@googlegroups.com.

To post to this group, send email to usba...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/usbarmory/18143a73-6187-4498-be19-eda5f5158228%40googlegroups.com.

[ela...@gmail.com]

Hello again, Thanks !

It did worked with : "Acer Incorporated. - Other hardware - USB Ethernet-RNDIS Gadget" from your search. 

Acer Incorporated. - Other hardware - USB Ethernet/RNDIS Gadget

Windows 7,Windows 8,Windows 8.1 and later drivers

Drivers (Other Hardware)

13/01/2010

1.0.0.0

21 KB

SHA1 - 4B9970E3174B23B5CB2371AF0837F939A71271EA

MD5   - F25297DD3129CE891B4015E27B37BBD8

And note that : "Acer Incorporated. - Other hardware - Acer USB Ethernet-RNDIS Gadget" did not, go figure this out...

In case it'll help someone, here are the steps I followed to install the driver on Windows 10:

1. Download the .cab file from www.catalog.update.microsoft.com
   
2. Start a PowerShell Console, and in it :
1. cd "C:\Path\To\Your\DownloadDir"
2. mkdir Tmp
   
3. expand '.\Acer Incorporated. - Other hardware - Acer USB Ethernet-RNDIS Gadget.cab' .\Tmp\ -f:*
   
4. pnputil.exe /add-driver .\Tmp\RNDIS.inf /install
   
3. And That's it, It worked immediatly after that for me (note, you still got to configure the network adaptater)

And thanks again for your help ! 

Best Regards,