Windows 10: 1903: After reboot, why isn't both Ethernet and Wifi connected at the same time?

What's the trick in 1903 to have both Ethernet and Wifi connected at the same time after a reboot?

Steps to reproduce:

• Make sure you're connected to a wifi network
• Plug in an ethernet cable
• Note you're connected now with 2 IP addresses - one via ethernet, one via wifi
• Reboot laptop and log back into Windows 10 without unplugging ethernet.
• Note that you're only connected via Ethernet with one IP address.
• Disconnect ethernet
• Note that Wifi takes a moment but connects, giving you another IP address.
• Plug ethernet back in
• Now both remain connected with 2 IPs

I believe this changed in 1903. What I want is to have my Windows 10 laptop always connect to both Ethernet and Wifi, like it used to before 1903. The fixes I've read online about this issue don't seem to work with 1903.

Thanks for any help. Note that I'm trying to solve an internal problem with a custom built series of devices at work, and several of my Windows 10 laptops connect to those. I require both ethernet and wifi to be active with their own IPs even after a reboot (which worked fine pre-1903), so with all due respect and politeness, I don't want to get into a lengthy explanation of why I need to do this, I just need to. Thanks

submitted by /u/decker12
[link] [comments]

:)

 

Windows 10 No Longer Connects to Ethernet and WiFi

This week brought Win10 ver 1903 and I can no longer get WiFi to connect if the ethernet cable is plugged in. If I boot with ethernet, manually trying to connect WiFi silently fails. If I boot without ethernet, WiFi is automatically connected yet drops
if I plug in the ethernet cable. Both the WiFi and the ethernet work fine by themselves, just not at the same time so I don't think it is a driver problem.

Any suggestions would be appreciated

 

Windows 10 No Longer Connects to Ethernet and WiFi

For a number of months I have used an ethernet connection to a device in my lab and a WiFi connection to the Internet via a DSL modem. Upon boot up the ethernet connection was on (albeit without Internet) and I just manually connected the WiFi to the DSL
modem. Worked fine.

This week brought Win10 ver 1903 and I can no longer get WiFi to connect if the ethernet cable is plugged in. If I boot with ethernet, manually trying to connect WiFi silently fails. If I boot without ethernet, WiFi is automatically connected yet drops
if I plug in the ethernet cable. Both the WiFi and the ethernet work fine by themselves, just not at the same time so I don't think it is a driver problem.

I searched for any others finding a similar problem with 1903, but do not find any. I do note earlier advice to add the fMinimizeConnections=0 register key and tried that. No luck with that.

Any suggestions would be appreciated,

Cliff

 

WIFI Works, Ethernet won't

OK but why?

NOT YELLING, JUST EMPHASIZING

Please note, I installed the new Lynksis, it worked just fine for 3-4 days on both my MACBOOK PRO when in ethernet connect and the Dell, then the ethernet just quit working for both my MacBook Pro and Dell desktop. It did work, then just quit for no apparent reason. WIFi for iPhone, iPad, Andriod Phone, and when I set to wifi for my MacBook pro all work fine.

Detailed history: I first noticed that on my Desktop dell that is CAT5 ethernet connected to the WIFI ROuter, that it stopped, no internet access. I began to trouble shoot, and turned off my WIFI on my MAcbook and it wouldnt work either, plugged into same router but different cat5 cable. At that time, all WIFI devices still worked. I figured that it must be the ethernet side of the WIFI router, so I replaced the router with brand new one. the Lynksys N900 listed in original thread. Ethernet and everything worked just fine for 3-4 days. But then ethernet quit, but wifi still works.

Whatever the problem, it affects both my MacBook Pro and Dell with WIN 7. I'm guessing it is NOT a computer problem, if it is it is affecting both my Mac and Dell, separate cat 5 cables to same wifi router

To remixedcat, I don't know for sure how to check IP settings, see above post, no damage apparent to anything.