Modem Dongle not Working On Windows 10 Fall Creators Update

Hello,

Please refer this linkfor a workaround and updates regarding this issue.

Regards.

Hey,

I solved the problem by realizing that the modem isn't able to find itself an IP-address, so you have to do it yourself in the windows options.

1. Go to Control Panel, search for "Control panel"
2. Navigate to "Network and Internet" -> "Network & Sharing Center"
3. On the right sidebar, you will see "change adapter settings", go there.
4. There you will see a few devices, open the one that has a greyed text: "Remote NDIS based Internet Sharing Device" (some text probably cut out).
5. "Properties" -> Select Internet Protocol Version 4 (TCP/IPv4) by clicking it -> "Properties"
6. Click on "Use the following IP-address:" and fill in these values.

IP-address: 192.168.1.100

Subnet mask: 255.255.255.0

Default gateway: 192.168.1.1

these DNS-servers are google Public DNS, you can use your preferred one, if you want.

Preferred DNS server: 8.8.8.8

Alternate DNS server: 8.8.4.4

And check the tickbox that says "validate settings upon exit."

7. Click OK and it should work wonders after this.

    Hi, Microsoft Answers Community Forum Members.

    Thank you for creating this thread and for posting on it.

    I can myself acknowledge the fact that the E3372 dongle has the same issue.

    As I have answered Jan's comment here, I need to solve the issue in less than ten minutes on each Microsoft Windows installation that I am using anywhere. Also, one 10.0.1703.15063.674 installation that I am using is itself manifesting this issue.

    I have not attempted to apply Kalski's solution yet, but sometimes it might be difficult and time-consuming to apply.

    I have had myself a one-to-one remotely controlled session with a support agent from the telecommunication operator, to no avail.

    I guess that I shall be myself waiting for the date of Tuesday, 28-November-2017.

    _________________________________________

    I would like to report a slight improvement in the resolution of this Issue. I have tested again this Issue on the Installation previously referred to as (B) Microsoft Windows 10 Professional Edition x64 Version 1703 Operating System Build 15063.674.

    None of the Version Numbers (10.0.1703.15063.674) have changed in the meantime. However, it is possible that some of the Internals of the Operating System have been improved, updated and reconfigured in the meantime.

    Upon the insertion of the Dongle into a U.S.B. Port, the Auto-Run Feature of the Operating System has not been launched and therefore the expected Installation Procedure that had been developed by the Software Company that produces Device-Drivers and Software Applications for the HuaweiCompany did not take place.

    No Files or Folders have been presented to the user, but the Operating System has installed something related to the Dongle.

    Upon the manual start into execution of the AutoRun.EXE Executable Binary File that is present inside the Internals of the Dongle, I have had the surprise to see, instead of witnessing the commencement of the Installation Procedure, the launch into execution of the Microsoft EdgeDesktop Software Application that has automatically been pointed to an Uniform Resource Locator handled by the Telecommunication Operator.

    Not only that, but the Internet Connection has instantly got activated, without even requiring the insertion of a Personal Identification Number. I can guess that the Dongle had already been authenticated inside the 4G Mobile Data Network when a Sales Agent of the Telecommunication Operator had previously tested the Dongle in another Mobile Electronic Device inside a Show-Room. He had inserted the Personal Identification Number then. Maybe no more authentications have been necessary after that initial one.

    The Dongle has behaved extremely well so far. I shall keep monitoring this Issue in order to see what else is going on.

    Also, I shall further test this issue on some versions of the following Operating Systems:

1. Microsoft Windows XP;
2. Microsoft Windows 7;
3. Microsoft Windows 10.

Thank you very much.

Solution No.2 FIXED the problem.