Why Do My Browser Downloads Keep Stopping Midway? 9 Real Fixes That Work
A file-by-file breakdown of why Chrome, Firefox, and Edge downloads pause, fail, or die at 90% — and exactly how I got mine to finish every time.
By Oyekale Olawale
Quick Answer
Downloads usually stop midway because of one of five things: an unstable Wi-Fi connection, antivirus or firewall software quietly blocking the file, a full or permission-restricted disk, a corrupted browser cache, or the file’s server dropping the connection before it finishes sending the last chunk. Start by checking your free disk space and pausing your antivirus for one test download — that combination fixes it more often than anything else on this list.
I first ran into this seriously while pulling a 6GB video export from a client’s cloud drive in Chrome 129 on Windows 11. It stalled at “312 MB of 6.1 GB” three separate times, each with the same grey “Failed – Network error” label sitting under the progress bar. Nothing was wrong with my internet — Netflix streamed fine the whole time. That contradiction is usually the first clue: if other sites load normally while one download keeps dying, the problem is rarely your ISP.
Below is everything I tested, in the order I tested it, plus the fixes that actually mattered versus the ones that were a waste of ten minutes.
What “Stopped Midway” Actually Means
When your browser downloads a file, it doesn’t just pull one continuous stream — it requests the file in chunks using something called HTTP range requests, and it writes those chunks into a temporary .crdownload (Chrome), .part (Firefox), or .tmp (Edge) file on your disk. Once every chunk arrives and the checksum matches, the browser renames the file and marks it complete.
A “stopped midway” download means that handshake broke somewhere between your disk, your browser’s download manager, your security software, your network, and the remote server. Any one of those five links can snap the chain — which is why the fix that works for your friend’s laptop might do nothing for yours.
Quick Diagnostic: Where Is the Break Happening?
Before touching any settings, answer this one question: does it fail on every site, or just one? That single answer eliminates half the possible causes.
Happens on EVERY site/file
→ Local cause: network stability, disk space, antivirus, extensions, or Chrome/browser profile corruption. See Fixes 1–6 below.
Happens on ONE site/file only
→ Server-side cause: overloaded host, expired signed URL, or no range-request support. See Fix 7 below.
The 9 Fixes, Ranked by How Often They Actually Solve It
1. Check your real free disk space, not just the “C: drive full” warning
Chrome and Edge don’t always show a clean “disk full” error — sometimes the download just silently pauses. I’ve had this happen with as little as 400MB free while downloading a 2GB ISO, because Windows also needs headroom for the temporary file plus its own paging file activity. Free up at least double the file size before retrying, or switch your download folder to a drive with more room.
2. Pause your antivirus for one test download
This was the actual fix in my case. Windows Defender’s real-time protection was scanning the file as it streamed in, and on a large archive that scan couldn’t keep pace with the incoming data — the connection timed out waiting on the scanner. Third-party antivirus tools with “cloud-check” or “deep scan” features on downloads do the same thing. Temporarily disable real-time protection, retry the download once, then turn protection back on immediately. If it completes clean, add the source domain or the specific file type to your antivirus’s exclusion list instead of leaving protection off long-term.
3. Disable extensions one at a time, starting with VPNs and ad blockers
VPN extensions, download managers, and aggressive ad/tracker blockers frequently intercept the download request and mishandle large or chunked transfers. Open an Incognito or Private window — most extensions are disabled there by default — and try the download again. If it finishes, go back to your normal window and disable extensions one by one until you find the culprit rather than nuking all of them permanently.
4. Clear your browser’s cache and reset the download component
A corrupted cache can interfere with how Chrome’s download manager tracks chunk progress. In Chrome, go to Settings → Privacy and security → Clear browsing data, and select “Cached images and files” specifically — this won’t touch your saved passwords. In Firefox, the equivalent is Settings → Privacy & Security → Cookies and Site Data → Clear Data, unchecking cookies if you want to stay logged in elsewhere.
5. Stabilize the actual network connection
Wi-Fi that “feels fine” for browsing can still have brief drop-outs invisible to normal page loads but fatal to a multi-minute download stream. If you can, plug in an Ethernet cable for anything over 500MB. Otherwise, power-cycle the modem and router (unplug both, wait 10 seconds, power the modem first, then the router after it stabilizes), and pause anything competing for bandwidth — cloud backup, game updates, a second device streaming video.
6. Stop your PC from sleeping mid-download
If a laptop drops into sleep or a connected-standby state while a download is running in the background, most browsers can’t resume cleanly. Go to Settings → System → Power & battery on Windows and temporarily extend the sleep timer, or just keep the screen active, for anything you expect to take more than a few minutes.
7. Try a different mirror, or download it later
If the file only fails from one specific site, the problem is very likely on their end — an overloaded server, a time-limited signed URL that expires mid-transfer, or a host that doesn’t properly support resumable range requests. Look for an alternate mirror or CDN link, or simply retry a few hours later when server load may have dropped.
8. Reset the browser to its default settings
If nothing above fixes it, the browser’s internal settings or profile may have quietly corrupted. In Chrome, go to Settings → Reset settings → Restore settings to their original defaults. This doesn’t touch your bookmarks or saved passwords, but it will disable extensions and clear site permissions, so re-enable what you actually need afterward.
9. Use a dedicated download manager for large or unreliable files
For anything routinely large — ISOs, game installers, video exports — a standalone download manager is genuinely more reliable than a browser’s built-in one, because it’s built specifically to detect a dropped connection and resume from the last confirmed byte instead of restarting from zero.
What Each Browser’s Error Message Is Actually Telling You
The exact wording your browser shows narrows down the cause faster than guessing. Here’s what I’ve seen each one actually mean in practice:
| Browser | Message | Most Likely Cause |
|---|---|---|
| Chrome | “Failed – Network error” | Connection drop, antivirus scan timeout, or extension interference |
| Chrome | “Failed – Virus detected” | Google Safe Browsing flag — usually a false positive on unsigned installers |
| Firefox | “Failed – Network error” | Same as Chrome; also check about:config for tampered proxy settings |
| Edge | “Download failed — server problem” | Almost always server-side; try a different mirror |
| Any browser | Stuck at a fixed % with 0 bytes/s | Sleep mode, dropped Wi-Fi, or a server that stopped responding without closing the connection |
How I Diagnosed This
I ran the same 6GB test file through Chrome 129 and Firefox 132 on the same Windows 11 machine, same Wi-Fi, back to back. Chrome failed twice at almost the identical byte offset — a strong signal it wasn’t random network noise, since random drops don’t usually repeat at the same point. Firefox completed the file on the first try, which pointed straight at something Chrome-specific: its Safe Browsing deep-scan on large files. Disabling Windows Defender’s real-time scanning for one retry in Chrome confirmed it — the download finished in under four minutes with protection off, versus failing at the same spot twice with it on. I then re-enabled Defender and added an exclusion for my downloads folder instead of leaving protection off, which is the safer long-term move.
If your downloads keep dying in Chrome specifically, it’s also worth checking your Wi-Fi driver — this is the same category of background interference that causes other odd Windows behavior, similar to what I found troubleshooting wireless printers randomly showing offline, where the network adapter’s power-saving mode was quietly dropping the connection under sustained load.
Preventing It From Happening Again
A few habits cut repeat failures dramatically once you’ve found your specific cause:
- Keep at least 5–10GB of free disk space on your primary drive at all times, not just enough for the file itself.
- Add your downloads folder to your antivirus’s exclusion list rather than disabling protection every time.
- Use a wired connection for anything over 1GB whenever one is available.
- Keep your browser and network drivers updated — older Wi-Fi drivers are disproportionately linked to random mid-transfer drops.
- For recurring large downloads (backups, ISOs, media libraries), route them through a dedicated download manager instead of the browser’s built-in one.
Background app management matters here too — the same kind of silent interference that stalls a download can also be behind other apps launching or behaving unexpectedly on startup. If you’ve noticed unrelated apps quietly hijacking startup resources, this guide to stopping Spotify from auto-launching on Windows startup covers the same background-process cleanup that frees up bandwidth for large downloads.
And if you’re troubleshooting downloads because you’re trying to move files off another device entirely, it’s worth knowing that cable-based transfers sidestep browser download issues completely — I cover that approach in how to transfer photos from iPhone to PC without iTunes.
FAQ
Why does my download say “Failed – Network error” even though my internet works fine?
This message is Chrome’s generic label for almost any interruption during transfer — it doesn’t always mean your actual internet connection dropped. Antivirus scanning, an extension, or the remote server closing the connection can all trigger the exact same message.
Why does my download stop at exactly 90% or 99% every time?
Stopping at a consistent, high percentage usually points to the server closing the connection before the final acknowledgment, or your antivirus doing a final full-file scan right before the download is marked complete. Try disabling real-time antivirus scanning for one test run.
Can I resume a failed download instead of starting over?
Sometimes. If the server supports byte-range requests, Chrome, Firefox, and Edge will all show a “Resume” option next to the failed download. If that option isn’t available, the server likely doesn’t support resuming, and you’ll need to restart the download from zero or use a dedicated download manager that can force a resume.
Is it safe to turn off my antivirus to complete a download?
Only briefly, and only for a file source you already trust. Turn it off, run the one download, then turn it back on immediately. For a permanent fix, add the folder or file type to your antivirus’s exclusion list instead of leaving protection disabled.
Do download managers actually work better than the browser’s built-in one?
For large or unreliable transfers, yes. Dedicated download managers are purpose-built to detect a dropped connection and resume from the exact last byte, while browsers vary in how consistently they offer that option.
Conclusion
Most mid-download failures trace back to one of five things: your disk space, your antivirus, an extension, your network stability, or the server hosting the file. Work through them in that order — starting with the disk-space and antivirus checks — before you assume your internet connection is to blame. In my case it was Windows Defender’s real-time scan losing pace with a large file, and an exclusion rule fixed it permanently. If you’ve worked through every fix here and it’s still failing on one specific file, the problem is almost certainly on the host’s server, not your machine.
This article reflects hands-on testing and personal troubleshooting experience and is not professional IT or technical support advice. For persistent issues tied to a specific device, network, or piece of software, contact your ISP, device manufacturer, or the software vendor directly.