After I upgraded my laptop from Windows 8.1 to Windows 10, my network connectivity was gone because all protocols were unchecked in the adapter settings. When I went to go turn them all back on, I got my network connection back, but I couldn't (and still can't) enable the Multiplexor protocol. When I select it and click 'Ok', a dialog informs me that my selections will cause it to be disabled:
If I click
No, it returns me to the "Ethernet Properties" sheet with the multiplexor protocol disabled. If I click
Yes, it unchecks the multiplexor protocol and then closes the dialog and property sheet.
The googler wasn't very helpful, here. There are a few threads out there in which users express the same issue, but the support they received was quite useless.
I also tried to do this in PowerShell to see if it would either a) just work, or if it would b) give me a more useful error message.
C:\Users\Benjamin> Get-NetAdapterBinding -InterfaceAlias "Ethernet" -ComponentID ms_implat Name DisplayName ComponentID Enabled ---- ----------- ----------- ------- Ethernet Microsoft Network Adapter Multiplexor Protocol ms_implat False C:\Users\Benjamin> Enable-NetAdapterBinding -InterfaceAlias "Ethernet" -ComponentID ms_implat C:\Users\Benjamin> Get-NetAdapterBinding -InterfaceAlias "Ethernet" -ComponentID ms_implat Name DisplayName ComponentID Enabled ---- ----------- ----------- ------- Ethernet Microsoft Network Adapter Multiplexor Protocol ms_implat False
Turns out that was really too much to hope for.
While reading it did occur to me to make sure the NdisImPlatform service was running, and I made sure using
C:\Users\Benjamin> sc.exe config NdisImPlatform start= demand [SC] ChangeServiceConfig SUCCESS C:\Users\Benjamin> sc.exe start NdisImPlatform SERVICE_NAME: NdisImPlatform TYPE : 1 KERNEL_DRIVER STATE : 4 RUNNING (STOPPABLE, NOT_PAUSABLE, IGNORES_SHUTDOWN) WIN32_EXIT_CODE : 0 (0x0) SERVICE_EXIT_CODE : 0 (0x0) CHECKPOINT : 0x0 WAIT_HINT : 0x0 PID : 0 FLAGS :
After this, I tried the things I described above again, but to no avail.
Also, ultimately this is yak-shaving in order to get bridged networking to work in VirtualBox, and so I thought I might try to repair the VirtualBox installation (by running the installer again), but that didn't help either.
Anybody know why this is happening in Windows 10 and how I can fix it?