The “Failed – Network error” message in Chrome’s download bar is one of those failures that lands at the worst possible moment — when you’re downloading a large file, a piece of software you actually need right now, or an important document. The download gets partway through and stops. Sometimes it shows a percentage, sometimes it dies immediately. The message is the same either way: no useful information about what actually went wrong. If you want the full context, see our Google Chrome Errors.
Before doing anything else, right-click the failed download in the bottom bar and check for a Resume option. Chrome supports resumable downloads for most files — if the failure was caused by a brief network interruption, resuming picks up from where it left off without starting over. If Resume isn’t available, click the retry arrow. If it fails at or near the same point again, the cause is consistent rather than random, and the fixes below apply.
At What Percentage Did It Fail? That Narrows It Down
The failure percentage is the most useful diagnostic information you have. Each pattern points to a different cause:
Fails at exactly the same percentage every time: an antivirus is scanning the partial download and blocking it at a consistent file size threshold, or the file itself has a corrupt segment on the server at that position. Antivirus is far more common — see Fix 1.
Fails at random, varying percentages: the network connection is dropping packets inconsistently. The connection looks stable for browsing (which is very tolerant of packet loss) but fails for sustained downloads (which require a stable TCP connection throughout). Fix 3 covers network stability testing.
Fails immediately at 0%: the problem is permissions on the download folder, insufficient disk space, or Chrome can’t write to the target location at all. Fix 2 covers this.
Every download fails, not just this one: something is blocking Chrome’s download capability entirely — antivirus with download protection, a system-level policy, or Chrome profile corruption. Fix 4 and Fix 5 apply.
Fix 1: Check Antivirus Real-Time Scanning
Antivirus interference is the single most common cause of Chrome download failures in my experience. Windows Defender and third-party antivirus products scan files as they download. When the scanner encounters a file it wants to inspect more thoroughly — usually at a specific file size threshold — it can interrupt the download stream, terminating it from Chrome’s perspective. The file is often completely legitimate; the antivirus just flagged it for a deeper scan at an inopportune moment.
The giveaway pattern: the download consistently dies at around the same percentage, especially 60-70% range where many real-time scanners trigger a full file inspection.
- Open Windows Security → Virus and threat protection → Real-time protection → toggle Off
- Retry the download immediately while protection is off
- Re-enable real-time protection as soon as the download completes
- If the download succeeds: add your Downloads folder to Windows Defender exclusions permanently — Virus and threat protection → Manage settings → Exclusions → Add an exclusion → Folder → select your Downloads folder
This keeps real-time protection active everywhere else while preventing it from interrupting Chrome downloads. For third-party antivirus products, look for a “Web Shield,” “Download Protection,” or “Safe Downloads” feature and temporarily disable it. If disabling it fixes the download, add the Downloads folder or Chrome as an exception in the antivirus settings.
Fix 2: Permissions and Download Location
If downloads fail immediately at 0%, or fail consistently with a specific “access denied” type of behaviour even though no error says that explicitly, the download folder’s permissions may have changed. This happens after Windows updates that reset folder permissions, profile migrations, and certain system cleanup tools that “fix” permissions in ways that break Chrome’s write access.
- In Chrome, go to three-dot menu → Settings → Downloads and note the download path
- In File Explorer, navigate to that folder
- Right-click the folder → Properties → Security tab
- Confirm your user account has Full Control listed
- If not: click Edit → select your user account → tick Full Control → Apply
Fastest workaround: change Chrome’s download location to a different folder temporarily — try the Desktop, or create a new folder in Documents. If the same file downloads successfully there, the original download folder is the problem. Fix the permissions as above or simply change the default download location.
Also check disk space. Chrome reports download failures without distinguishing between network errors and disk full errors. If your drive is nearly full, free up space or download to a different drive.
Fix 3: Test Network Stability
Downloads failing at random, inconsistent percentages is the signature of intermittent packet loss — brief network interruptions that don’t disrupt browsing (which retries automatically) but break the sustained TCP connection that large downloads require.
The test that confirms this: open Command Prompt and run ping 8.8.8.8 -n 100. This sends 100 pings and reports any that time out. More than 2-3 timeouts out of 100 confirms packet loss on your connection. Look at the packet loss percentage in the final summary line.
If you’re on Wi-Fi: switch to a wired Ethernet connection for large downloads. Wi-Fi packet loss — even minor, invisible packet loss — is one of the most common causes of download failures on otherwise healthy-seeming connections. A single Ethernet cable to the router eliminates this entirely and is worth trying before anything else if you’re on wireless.
Also restart the router if packet loss is detected. Unplug, wait 60 seconds, reconnect. Connection tracking table issues and memory leaks in consumer routers cause packet loss that clears after a power cycle.
Fix 4: Disable VPN or Proxy
VPNs introduce additional network hops that increase the chance of connection interruption during large downloads. Some VPN providers also throttle large file transfers — detecting the sustained high-bandwidth download and applying rate limiting that eventually causes the connection to drop. Proxies with short timeout settings fail downloads that take longer than their configured timeout.
- Disconnect VPN completely and retry the download
- Settings → Network and internet → Proxy → confirm “Use a proxy server” is Off
- If it downloads successfully without VPN: try a different VPN server location, or download without VPN and reconnect afterward
Fix 5: Alternative Download Methods
When Chrome’s built-in download manager keeps failing on a specific file despite all the above, bypassing Chrome entirely is often the fastest path to getting the file. Chrome’s download manager has less sophisticated retry and resume logic than dedicated tools.
Free Download Manager (fdm.io) handles interrupted downloads with automatic retry and resume, splits downloads into multiple parallel connections to improve speed and resilience, and generally handles the files Chrome struggles with. Install it, paste the download URL, and it handles the rest.
curl is built into Windows 11. Open an Administrator Command Prompt and run:
curl -L -o "C:Users[YourName]Downloadsfilename.exe" "paste-the-download-URL-here"curl automatically resumes interrupted downloads and handles redirects that Chrome’s downloader sometimes trips on. It’s not the prettiest approach but it works where Chrome doesn’t.
Microsoft Edge uses a different download implementation and sometimes succeeds on files where Chrome fails on the same connection. Worth trying for a specific file you urgently need without going through download manager setup.
| Failure pattern | Likely cause | Fix |
|---|---|---|
| Same percentage every time | Antivirus blocking at size threshold | Fix 1 — disable real-time protection; add exclusion |
| Fails immediately at 0% | Folder permissions or full disk | Fix 2 — check permissions; try different location |
| Random percentages | Network packet loss | Fix 3 — ping test; use Ethernet |
| Only with VPN active | VPN throttling or timeout | Fix 4 — download without VPN |
| All downloads fail | Chrome profile issue | Fix 5 — use alternative download method |
Our guide on Chrome not loading pages covers the connection failures that can accompany download errors when the network issue is severe enough to affect browsing and downloading simultaneously. For Wi-Fi instability causing random download failures, our Wi-Fi not working on Windows 11 guide covers the adapter power management and driver issues that cause packet loss. Additional Chrome download troubleshooting — including downloads blocked by Chrome’s Safe Browsing feature — is covered in the Google Chrome support documentation.
Chrome’s Safe Browsing feature adds a separate layer of download blocking that’s distinct from antivirus and network issues. When Chrome’s Safe Browsing determines that a downloaded file type is potentially dangerous, it may either warn you before allowing the download or block it outright. Files blocked by Safe Browsing show a specific warning with “Keep” and “Discard” buttons rather than “Failed – Network error” — but in some cases the blocking happens before Chrome completes the download, producing a network error appearance. If you’re downloading executable files, installers, or archive files from less well-known sites, Safe Browsing’s download protection may be the cause. To verify: go to Chrome Settings → Privacy and security → Security → Safe Browsing, and check whether “Enhanced protection” or “Standard protection” is enabled. Temporarily switching to “No protection” and retrying the download confirms whether Safe Browsing is blocking it. Switch back to your preferred protection level after testing.
File server configuration issues cause “Failed – Network error” on specific downloads from specific sites. Some file servers set HTTP headers that Chrome handles correctly in most situations but fails on in specific combinations — particularly Content-Disposition headers with unusual filename encoding, chunked transfer encoding without proper termination, or redirect chains that end at a server that drops the connection after the initial response headers. When this is the cause, the download fails consistently from Chrome but succeeds from curl or a download manager that handles these edge cases differently. Passing the download URL through curl confirms the server-side configuration as the cause — if curl completes the download successfully while Chrome fails, the problem is in how Chrome’s download manager handles that server’s specific response format.
Corporate network environments add download-specific complications. Web filtering proxies used by corporate networks often apply content inspection to downloads — scanning file contents for data loss prevention (DLP) policy violations, malware, or policy-prohibited content types. When this inspection takes longer than the proxy’s internal timeout allows, the download connection gets cut mid-transfer, producing “Failed – Network error” in Chrome. This typically affects larger files more than smaller ones (larger files take longer to inspect, hitting the timeout more often) and appears consistently on work machines connected through the corporate network but not at home. If this is the cause, the fix lies with IT — the DLP inspection timeout may need adjustment, or the specific download may need to be exempted from inspection if it’s a legitimate business file.
Download speed throttling by the file hosting server is worth distinguishing from network packet loss. Some file hosting services throttle download speeds for non-paying users, applying rate limiting that’s aggressive enough to eventually cause Chrome’s connection to time out and report “Failed – Network error.” The symptoms look similar to packet loss but are specific to that server — other sites download fine at normal speed. Checking the download speed in Chrome’s task manager (Shift + Esc → find the download process) shows whether speed is being throttled to near-zero before the failure. If it is, using a download manager that can resume and work around throttling, or finding an alternative download mirror, is the practical solution.
Browser extension interference with downloads is less common than with page loading but does occur. Download manager extensions, clipboard managers that intercept download links, and privacy extensions that modify request headers can all interfere with Chrome’s download process in ways that produce “Failed – Network error.” Testing in Chrome Incognito (which disables extensions) confirms extension involvement if downloads succeed there but fail in normal Chrome. The specific extension causing the issue can be identified by disabling extensions one at a time at chrome://extensions and retrying the download after each — a methodical process but one that definitively identifies the culprit rather than requiring guesswork about which extension might be intercepting download requests.
Download location on a network drive (NAS, mapped network drive, or OneDrive-synced folder) is an underappreciated cause of “Failed – Network error” that has nothing to do with Chrome’s network connection to the internet. When the download destination is a network path — even a locally-synced cloud folder — any instability in the connection between the PC and the network storage appears to Chrome as a network error, even though the internet download itself was fine. If your Chrome download location points to a NAS or network path, change it to a local folder (Settings → Downloads → Change → select a folder on the local drive like Documents or Desktop) and retry. If the download succeeds locally, the network drive connection is the issue, not Chrome or the internet connection. If this sounds familiar, Chrome Download Stuck? How to Fix Chrome Download Stuck at 0%, 100%, or Pending is worth a look.
