Fix Slow File Transfer on Windows 11: 2026 Guide

A 10 GB video file that should copy in a few minutes crawls along at 12 MB/s, and suddenly a quick backup turns into an afternoon project. Slow file transfers on Windows 11 are one of the most common complaints from people moving large files across a home network or between drives, and the frustrating part is that the cause is rarely obvious. The bottleneck could be a security setting Microsoft turned on by default, a tired network driver, a firewall profile, or a copy engine that simply isn’t built for big files.

The good news: almost every cause has a fix you can apply yourself, usually in under ten minutes. This guide walks through the settings that actually matter, in the order worth checking them, and flags the “tweaks” that sound smart but make things worse.

Start With the Basics Before Touching Settings

Before diving into registry keys and PowerShell commands, rule out the boring stuff. A surprising share of “slow transfer” complaints trace back to hardware that was never going to hit gigabit speeds.

• Check the link speed. Open Settings > Network & internet > Advanced network settings and look at the current link speed for your adapter. If it says 100 Mbps on a Gigabit network, you have a cable, port, or router problem, not a Windows problem.

• Test with a local copy first. Copy a large file from one folder to another on the same drive, then between two internal drives. If local copies are also slow, the issue is disk or driver related, not networking.

• Swap the cable and port. A damaged Cat5e cable or a router port negotiating down to 100 Mbps is a classic culprit. It costs nothing to test.

• Close background sync tools. OneDrive, Dropbox, and Steam downloads compete for the same disk and network bandwidth. Pause them and retest.

If the basics check out and transfers are still slow, move on to the settings below.

Check SMB Signing, the Most Overlooked Default

SMB signing is a security feature that verifies every packet on a file-sharing connection. It protects against tampering, and Microsoft has been enabling it by default on Windows 11 client connections. The trade-off is real: signing adds processing overhead to every packet, and on high-latency links or older hardware it can noticeably reduce throughput.

This is the first setting worth testing on a home or small-office network you trust. In PowerShell, run `Get-SmbClientConfiguration` and look at the RequireSecuritySignature value. If it’s enabled and you control both ends of the connection, testing with it disabled tells you quickly whether signing is your bottleneck. On a business network, though, think twice: signing exists for a reason, and turning it off to gain speed is a bad trade on untrusted networks. The balanced approach is to test it, confirm whether it matters, and then decide based on your risk tolerance rather than flipping it off permanently.

Try SMB Compression on Slow Links

Windows 11 and Windows Server support SMB compression, which shrinks data before sending it across the network. On a fast local network, compression usually hurts because the CPU cost outweighs the savings. On a slow or congested link, especially a VPN or a Wi-Fi connection with limited bandwidth, it can be a genuine win. (Server Message Block (SMB))

Compression is opt-in, not automatic. You enable it per mapping with the `-CompressNetworkTraffic` parameter in `New-SmbMapping`, or configure it at the client level. The practical rule: turn it on for slow links, leave it off for gigabit LAN transfers. If you’re copying large, already-compressed files like videos or ZIP archives, expect little benefit since there’s nothing left to compress.

Give SMB Multichannel and RSS a Look

SMB Multichannel lets a single file transfer use multiple network connections at once, aggregating bandwidth when a machine has more than one network adapter or supports RSS (Receive Side Scaling) across multiple CPU cores. On supported hardware, it can turn a single-stream transfer into a much faster one.

Check whether it’s active with `Get-SmbClientConfiguration` and `Get-SmbMultichannelConnection`. If your adapter supports RSS but it’s disabled, enabling it in the adapter’s advanced properties can help. Be aware that some network drivers handle multichannel poorly, and a buggy driver can cap speeds or cause disconnects. If transfers got slower after a Windows update, a driver rollback is often the fastest fix.

Don’t Let “Optimizer” Tools Break TCP Autotuning

Plenty of “network optimizer” utilities promise faster transfers by disabling Receive Window Auto-Tuning. This is almost always bad advice. Autotuning lets Windows scale the TCP receive window to match available bandwidth and latency, and disabling it can slash throughput on high-bandwidth connections.

Check the current state with `netsh int tcp show global`. If the autotuning level reads “disabled” or “restricted,” that’s a red flag, often left behind by a tweaking tool someone ran years ago. Setting it back to normal with `netsh int tcp set global autotuninglevel=normal` restores Windows’ default behavior. This single change fixes a surprising number of “mysteriously slow” network copies, and it’s one of the most useful Windows keyboard shortcuts everyone should know style fixes: simple, reversible, and easy to verify.

Rule Out Antivirus and Filter Drivers

Third-party antivirus software scans files as they’re written, and real-time scanning of network shares is a well-documented cause of slow transfers. The same applies to local copies of large files. This isn’t a reason to uninstall your security software, but it is a reason to test.

Temporarily disable real-time scanning (or exclude the destination folder) and rerun the transfer. If speed jumps, you’ve found your culprit, and you can add a permanent exclusion for that folder or share. If you suspect malware is involved rather than just a chatty scanner, running one of the best free virus removal tools for Windows is a sensible first step before blaming your antivirus configuration. Similarly, if you’ve ever wondered whether a downloaded installer is clean before running it, learning how to check whether an APK file is safe covers the same due-diligence mindset for mobile files.

Fix the Network Profile and Firewall

Windows treats Public and Private network profiles very differently. On a Public profile, file sharing is blocked by default, and discovery and SMB traffic can behave unpredictably. If your home network is marked Public, switch it to Private in Settings > Network & internet.

Also check that File and Printer Sharing is allowed through Windows Defender Firewall for the Private profile. A blocked or partially allowed rule can cause transfers to fall back to slower paths or stall entirely. This is a two-minute check that resolves a lot of “it works on my other PC” confusion.

Stop the Network Adapter From Sleeping

Network cards have power-saving features that can quietly hurt throughput. In Device Manager, open your adapter’s properties, go to the Power Management tab, and clear “Allow the computer to turn off this device to save power.” Then check the Advanced tab for Green Ethernet, Energy-Efficient Ethernet, and similar options. These save power by reducing link speed when traffic is light, and some drivers are slow to ramp back up, causing brief but noticeable slowdowns at the start of large transfers.

This is one of those fixes that sounds like folklore but genuinely helps on laptops and on Realtek and Intel adapters with aggressive power management.

Use the Right Copy Tool for the Job

Windows Explorer’s copy engine is fine for everyday files but not always ideal for huge ones. Two alternatives are worth knowing:

• Robocopy with the `/J` switch uses unbuffered I/O, which is designed for very large files and can be faster and more reliable than Explorer. Add `/MT:8` when copying many small files to use multiple threads.

• Command-line copy sometimes avoids shell overhead entirely, though results vary by hardware.

A quick comparison of when each approach makes sense:

If you’re transferring files to a Steam Deck or similar device and running into odd behavior, some of the same driver and service issues show up there too, which is why guides like Decky loader not working Steam Deck fix 2026 cover overlapping troubleshooting ground.

Avoid SMB1 Fallback

SMB1 is deprecated and disabled by default in recent Windows versions for good reason: it’s slow and insecure. If an old NAS or printer forces a fallback to SMB1, both speed and security suffer. Check with `Get-SmbConnection` to see which dialect is in use. If it says SMB1, update the firmware on the other device or replace it. Falling back to a 1990s protocol to keep old hardware alive is rarely worth the performance hit.

Common Mistakes That Make Things Worse

A few well-intentioned moves backfire regularly:

• Disabling autotuning because a forum post said so. It usually hurts.

• Turning off SMB signing on a public or untrusted network to chase speed. The security cost isn’t worth it.

• Installing multiple “optimizer” tools that fight each other and leave conflicting registry settings behind.

• Blaming Windows when the actual bottleneck is a 100 Mbps router port or a failing drive.

The disciplined approach is to change one thing at a time, retest with the same file, and keep notes. That’s how you find the real bottleneck instead of guessing. (Speedtest by Ookla)

Conclusion

Slow file transfers on Windows 11 are almost never caused by one mysterious flaw. They come from a stack of small settings, each shaving off a little throughput: SMB signing overhead, a disabled TCP autotuning setting, an antivirus scanner reading every byte twice, a network adapter dozing off, or a firewall profile blocking the fast path. Work through them in order, starting with the free checks like cable and link speed, then move to SMB signing and compression, then the network stack and drivers.

The fixes that matter most are the ones you can verify. Test one change, measure the result, and keep what works. Most people find their answer within the first three or four checks, and the whole process takes less time than the slow transfer they were trying to avoid.

FAQ

Why are my file transfers so slow on Windows 11 even on a fast network?

The most common causes are SMB signing overhead, a disabled TCP autotuning setting left behind by an optimizer tool, real-time antivirus scanning, or a network adapter negotiating at 100 Mbps instead of 1 Gbps. Check link speed first, then test SMB signing and autotuning.

Does disabling SMB signing actually speed up transfers?

It can, especially on high-latency connections or older hardware, because signing adds per-packet processing. However, it weakens protection against tampering. Test it to confirm it’s your bottleneck, but avoid disabling it permanently on untrusted or business networks.

Should I turn on SMB compression?

Turn it on for slow or remote links such as VPNs and congested Wi-Fi, where shrinking data saves real time. Leave it off for fast local networks, where the CPU cost usually outweighs the benefit. It also does little for already-compressed files like videos.

Is Robocopy faster than File Explorer for large files?

Often, yes. Robocopy with the `/J` switch uses unbuffered I/O designed for very large files, and `/MT` multithreading helps when copying thousands of small files. Results vary by hardware, so benchmark with your own files before committing.

Can antivirus software slow down network file copies?

Yes. Real-time scanning inspects files as they’re written, and scanning network shares or large files can noticeably reduce throughput. Temporarily disabling scanning or excluding the destination folder is a quick way to confirm whether your security software is the cause.

Why does my transfer speed drop after a Windows update?

Updates sometimes install new network drivers or change default security settings like SMB signing. If speed dropped right after an update, roll back the network adapter driver in Device Manager and recheck SMB client settings before assuming hardware failure.