How to get Win10 to remember the network adapter

[ptr727]

Hi, every time I re-insert the device Windows forgets the previous device configuration, and I need to reconfigure sharing and IP addresses.

It looks like the device ID or MAC or something changes every time, and Windows discards the previous configuration.

If I use a real USB ethernet adapter, Windows remembers the device.

How do I configure the device so it is remembered?

[bass]

https://github.com/inversepath/usbarmory/wiki/Host-communication has some suggestions under "Setup & Connection Sharing: Windows 7, 8, 10", such as adding "idVendor=0x04b3 idProduct=0x4010" to /etc/modprobe.d/usbarmory.conf

--
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+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/a57fddf0-ea66-4a65-bba4-6dd4d2b2e51b%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[ptr727]

The adapter is successfully detected, and works as expected, but when removed and re-inserted, the previous settings are lost, as if it is a brand new instance of the adapter.

[Andrea Barisani]

On Friday, March 10, 2017 at 3:06:23 AM UTC+1, ptr727 wrote:

The adapter is successfully detected, and works as expected, but when removed and re-inserted, the previous settings are lost, as if it is a brand new instance of the adapter.

I am unsure why this would happen, our default Debian image sets specific addresses:

options g_ether use_eem=0 dev_addr=1a:55:89:a2:69:41 host_addr=1a:55:89:a2:69:42" (/etc/modprobe.d/usbarmory.conf)

On my Windows 10 installation (using the Acer driver) I never have to re-configure it.

[ptr727]

I don't know, did anybody else test on Win10 Insider Fast ring?

Maybe it is a timing problem in the emulation driver (I did see posts that the NIC plus Storage driver no longer works on Win10)?

This is what I get in the eventlog:

Miniport USB Ethernet/RNDIS Gadget, {8c6ef319-e671-4e21-8098-6b19a260f616}, had event Network Interface deleted while PNP Device still exists. Note that this event is provided for informational purpose and might not be an error always (Eg: In case of vSwitch which was recently un-installed or a LBFO team was removed)

Initialization failed because the driver device could not be created. Use the string "1A5589A26942" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the  Globally Unique Interface Identifier (GUID) if NetBT was unable to  map from GUID to MAC address. If neither the MAC address nor the GUID were  available, the string represents a cluster device name. 

Driver Management concluded the process to install driver rndis.inf_amd64_1fb2b40d582448a7\rndis.inf for Device Instance ID USB\VID_0525&PID_A4A2\6&323B6903&0&2 with the following status: 0x0.

A service was installed in the system.

Service Name:  USB Remote NDIS Network Device Driver

Service File Name:  \SystemRoot\System32\drivers\usb8023.sys

Service Type:  kernel mode driver

Service Start Type:  demand start

Service Account: