missing you a lot :-)
Writing here because the 1709 upgrade have broken my USB LTE modem. Probably somebody knows the simple ways (like registry editing) to recover it, or can report the bug to MS.
The modem is Huawei E3372h-153 Hilink, which is a very popular device, re-branded and used by lots of cellphone operators all over the world - Austria, Russia, Sri Lanka, Indonesia, Vodafone somewhere etc.
The problem is that, with 1709, the modem's USB RNDIS adapter, managed by the MS's inbox drivers, does not work.
On some firmware versions (I have re-flashed the modem several times), the network adapter is shown as being OK and fine, but no packets go, so ping and ARP do not work.
On some other firmware versions, only the Windows DHCP client does not work with modem's RNDIS adapter. Setting the IP address manually is a solution.
With the help of some websites, I have found a workaround on how to solve this.
The workaround is: force update the driver for the RNDIS devnode, installing MISMATCHING AND NOT WORKING Huawei's driver for the different modem firmware, and then updating the driver on the devnode to the MS's inbox one again.
After this, the RNDIS devnode works fine with the MS's inbox driver.
So, the whole thing is that: mismatching Huawei's driver tweaks something somewhere in the registry, after which returning the devnode back to the same MS's inbox driver - solves the bug.
In the process, the Huawei's driver does not work (and it should not). It only succeeds to start the devnode in "cable disconnected" state, nothing more.
Yes, it really looks like an issue not with rndismp6.sys+usb80236.sys, but with either NDIS itself or INetCfg DLLs.
I did some research on comparing the PnP devnode keys and Tcpip keys for "good" and "bad" cases, but so far to no success.
More details on the bug are in this TechNet thread:https://social.technet.microsoft.com/Forums/en-US/9a44310c-c85a-4794-a927-198021b12b9f/1709-bug-with-rndismp6sysusb80236sys-dhcp-client-does-not-work?forum=win10itpronetworking