When Ethernet drops only during large file transfers, the most likely cause is a weak point that shows up under steady load: a cable, port, NIC driver, power-saving setting, offload setting, or a storage drive that can’t keep up. Start by checking whether the Ethernet link itself is dropping. Then test the cable and port, and only after that change adapter settings or drivers. That order helps you avoid chasing the wrong layer.
What this symptom usually means
Large transfers keep the network path busy long enough to expose problems light browsing never finds. In practice, the cause is often a weak cable, a bad switch or router port, a driver that misbehaves under load, a power-saving feature that flaps the link, or a storage device that makes the copy fail and looks like a network problem.
A useful clue is what happens during normal use. If the connection is fine all day but falls apart during a big LAN copy or a large download, that points to a load-related fault, not a random Windows 11 outage. A desktop that only fails once traffic stays steady can also have a NIC that works until it heats up or hits a broken offload path. Some people see the network interface crash during big local transfers and have to disable and re-enable the adapter or restart before it comes back.
Before you start
Work through this on Windows 11 with one known-good cable, one known-good router or switch port, and enough time to rerun the same large transfer after each change. If this is a laptop or a USB Ethernet adapter, keep the charger connected and try to test on a cool machine first, because heat can make an already marginal adapter fail sooner.
Before you change settings, save anything open on the PC and know how to undo each setting you touch. If the link only fails on one destination drive, one NAS share, or one specific USB Ethernet adapter, treat that as a clue instead of forcing every possible fix on the whole system.
First, find out what is actually dropping
Before you change anything, separate three different failures: the Ethernet link itself, the IP connection, or just the file transfer. If the link is dropping, the adapter usually disconnects and reconnects in Windows, and the network icon may briefly show no connection. If only the IP path is changing, Windows may stay linked but the copy or download dies with gateway or timeout errors. If the copy fails while the link stays up, the problem may be the source drive, destination drive, or the transfer process.
Use the simplest checks first.
- Watch the Ethernet link light on the PC, router, or switch while you start the large transfer. If it goes out or changes right when the failure happens, that points to link loss.
- Open the network status in Windows and note whether the adapter shows disconnected, limited, or still connected when the failure happens.
- If you can, open Event Viewer and look for network or adapter events at the exact time of the drop. Repeated link-down and link-up events point toward the NIC, cable, or port rather than the copy itself.
- Try the transfer again and note whether the failure happens at about the same point, only on very large files, or only on one destination.
If the link stays up but the transfer errors out, stop treating it like a pure Ethernet problem until you check the drives and the app doing the copy.
Check the cable, port, and negotiated speed
The quickest fix path starts with the physical path. Reseat the Ethernet cable at both ends, then try a known-good cable that matches the speed you expect. Large transfers are the easiest way to flush out a marginal cable that looks fine during light traffic.
- Replace the cable first if you have a spare.
- Move the cable to a different router or switch port.
- If you use a USB Ethernet adapter, try a different USB port on the PC too.
- Check the negotiated speed and duplex in Windows and in your router or switch if it exposes link details.
You want the adapter to link at the expected speed and stay there. If it repeatedly falls back, renegotiates, or only behaves on one port, that is a strong sign of a bad cable path or a faulty switch port. A repeatable failure on one jack but not another is one of the clearest hardware clues you can get.
Tame adapter settings that can break under load
If the cable and port check out, the next place to look is the Ethernet adapter settings in Device Manager. Power management, Energy-Efficient Ethernet, and some offload features can stay quiet during casual use and then become unstable when traffic is steady. That pattern fits the symptom very well.
Start with the least risky changes and test one at a time.
- Open Device Manager, open your Ethernet adapter, and check the Power Management tab.
- If Windows is allowed to turn off the device to save power, clear that option and test again.
- In the Advanced tab, look for Energy-Efficient Ethernet or similar power-saving link options and disable them for a test.
- If the problem still happens, try disabling offload features one by one, such as Large Send Offload, TCP checksum offload, UDP checksum offload, or ARP offload. Reports from affected users point to offload settings and NIC crashes during big transfers.
- If you make a change, reconnect or reboot if the adapter asks for it, then test the same large transfer again before changing anything else.
Driver quality matters here too. Check whether the current Windows 11 Ethernet driver comes from the system maker, motherboard maker, or NIC vendor, and compare it with the support page for your exact model. If the driver is old, corrupted, or known to have trouble on your hardware revision, update it and retest. A BIOS or firmware update from the system maker is also worth checking when the release notes mention network stability, but only from the official support page for your exact model.
If you need to recover the adapter afterward, use Device Manager’s Action menu to scan for hardware changes so Windows redetects it.
If the link stays up, test the rest of the path
Once the cable, port, and adapter settings look sane, isolate where the failure really lives. First compare a LAN copy, such as PC to NAS, with an internet download. If only local transfers fail, the storage path or local switch path deserves more attention. If both fail, the adapter, driver, or router side is more suspicious.
A bad source or destination drive can mimic a network fault. If the PC writes to a slow, failing, or nearly full disk, the copy can stall, time out, or abort even though Ethernet is fine. The same is true if the NAS or remote PC is the weak link. Try a transfer to a different destination, or copy a large file from a different source, and see whether the symptom follows the drive or stays with the network path.
Router and switch firmware are worth checking before you blame Windows itself, especially if more than one device shows odd behavior on the same port. A bad switch port can look exactly like a bad NIC when the failure repeats on one path and not another. Heat is the other quiet suspect. If the adapter or the machine feels unusually warm near the drop, or if the failure gets worse after long transfers, suspect a marginal NIC or a failing USB Ethernet adapter. Test a different adapter or machine.
If one known-good cable and one known-good port still fail, the latest driver does not help, and the same drop follows the adapter to another machine or another adapter on the same PC, the hardware is the likely fault. At that point, replace the NIC, the USB Ethernet adapter, or the switch/router port instead of chasing more Windows settings.
Verify the fix
After each change, run the same transfer again and leave it long enough to reach the point where it used to fail. A clean run is more convincing than a quick reconnect.
You can also keep a continuous ping open while you test. Open Command Prompt and run ping -t google.com. If you see steady replies for several minutes and no drop while you repeat the large file transfer, the connection is holding. If the ping shows timeouts or the adapter drops again, the fault is still there.
For a real-world check, repeat the exact file copy or download that used to trigger the problem. If it still falls over, put the last setting back the way it was before trying the next one.
Conclusion
If the drop only happens under heavy transfer, work from the wire outward: cable and port, then adapter settings, then driver and firmware, then storage and hardware replacement. Stop once you find the layer that makes the failure follow the change, because that is usually the real cause.
Frequently Asked Questions
How do I tell if the cable link is actually dropping?
The cleanest sign is a brief disconnect and reconnect in Windows, often matched by the Ethernet link light going out or changing at the same moment. If the adapter stays connected and only the copy fails, look harder at the drives or the transfer path before you blame the link.
Should I update the driver before changing adapter settings?
Check the driver early, but I usually test the cable and port first because they are faster to rule out and safer to change. If the hardware path looks fine, a current Windows 11 driver from the adapter or system maker is worth trying before deeper setting changes.
Sources
- Network crashes with large file transfers - Software & Applications - Spiceworks Community (community.spiceworks.com)
- Network disconnects when downloading big files - Networking - Linus Tech Tips (linustechtips.com)
- Ethernet Connection Dropping Windows 11? Fix It Fast (vividrepairs.co.uk)