Windows continues to drop Ethernet connections and automatically switches to WiFi.
Windows continues to drop Ethernet connections and automatically switches to WiFi.
I've encountered a peculiar problem: my office desktop PC frequently loses internet connectivity over Ethernet, automatically switching to my WiFi 6 device. My setup uses a Netgear R7000 bridge-mode Ethernet port connected to a Netgear RAX120, while my homelab server/NAS (TrueNAS Core 12 with SyncThing and Pi-hole) is also linked via the same router. Both devices remain online without issues. I'm trying to determine if the issue lies with the router or stems from Windows 10 itself.
I'm currently running Windows 10 Pro Insider Preview 10.0.21322. The Ethernet card is a Realtek Gaming GbE Family Controller on my Asus Tuf Gaming Plus, and the Wi-Fi 6 AIC is an Asus AX3000. Despite appreciating the performance of WiFi 6 over distance and obstacles, I still favor the bridged connection for its stability and higher throughput to my server, which also uses Gigabit Ethernet ports.
I've experimented with various cables without resolving the problem. My assumption is that the stronger antenna configuration on my R7000 might have contributed to previous success. I'm seeking guidance on Windows 10 logs—specifically during the handoff from Ethernet to WiFi—to identify any anomalies. It seems the issue has recently emerged, suggesting a potential driver or software-related cause that should stabilize over time.
Currently, I'm transferring large volumes of data for an on-site backup and cloud storage. The bridged connection is significantly faster (around 100 Mbps) compared to WiFi 6 (previously 300+ Mbps), possibly due to the Ethernet path bypassing wireless limitations. I'm hoping this insight helps me troubleshoot further.
Recommend checking the settings across various routers connected to different networks. See if TOE or Jumbo Packets are activated on one device but not another.
Previously I set the speed to 100mbps rather than the default 1gbit in the adapter configuration. It looks like somewhere along the line it became unstable—someone changed the cable, others didn’t, so I’m just accepting it.
Review Attachments initially the log runs ipconfig /all after connecting to WiFi (post_switch_to_wifi_log01.txt). After turning off and back on the Ethernet adapter, it functions properly (pre_switch_to_wifi_log02txt.txt). Comparing the WinMerge files shows minor changes, possibly related to @Kisai’s notes. I noticed only a few offload options in the adapter settings, all enabled. Jumbo Packets was off, but turning it on didn’t resolve the issue—I’m not sure if either device supports it. It might be worth trying.
Checked the Windows Event Viewer and spotted a Server Error (EventID 2505) tied to NetBIOS. It seems your SMB share might be causing the issue. Details from the logs. network_logs.csv
Your WiFi card vanishes even with a wired link on, which is typical for laptops that switch off WiFi when connected to a wired port or dock. This suggests something is interfering with the wired Ethernet connection enough to trigger the switch. The event log points to the Hyper-V virtual adapter, indicating the wired card might be being reassigned to a virtual machine. If you're running Hyper-V (like VirtualBox, Bluestacks, MEMU), adjust settings so it emulates a network card instead of reassigning it. I doubt this is the main issue, as I haven’t experienced it with those tools. To check, try forcing the wired adapter to run at 100Mbit and see if the behavior changes. It could simply be power-saving features (like aggressive management) or an issue like a bent or damaged cable.
I ended up turning off WSL as a feature and also disabled SVM in bios, but it didn’t resolve the issue. Nothing changed with ethernet or power settings either. The fix came when I stopped using my SMB share, which seems linked to a NetBIOS change during the last update that affected SMB shares. I plan to set up a new connection and check the results. On one side, I’m relieved I solved the problem, but on the other, I really need access to my NAS.
Crap! I woke up and everything is still messed up again haha! I submitted my reports in the Insider Feedback Hub, so hopefully this gets fixed in the next update. Edit: Final note, just in case someone sees this later, the update actually messed up the option to assign the same network share as an admin network share (for higher-privileged apps) and a regular user share. It took re-installing Windows twice to resolve it. Since I've saved one as a drive letter and another as a different one, everything is now working perfectly.