Chrome downloads failing — files stop partway through, “Failed – Forbidden” or “Failed – Virus scan failed” errors, the download button doing nothing, or specific file types blocked silently — has a small set of common causes. Network issues, Safe Browsing blocking, antivirus interception, and download location permissions cover roughly 90% of cases. If you want the full context, see our Google Chrome Errors.
First quick test: try the same download in Incognito (Ctrl+Shift+N). If it works there, extensions or profile settings are the issue. If it still fails in Incognito, the cause is browser-wide, system-side, or the file itself is being blocked by Chrome’s built-in protection. This 60-second test routes you down the right diagnostic path immediately.
Safe Browsing flagging the file
Chrome’s Safe Browsing actively scans downloads and blocks files it considers risky — even legitimate ones get caught sometimes, especially executables, ZIP archives, and PDFs from less-known sites. The block message varies: “Failed – Virus scan failed,” “Failed – Forbidden,” or sometimes just “Failed” with no explanation.
To check what Chrome did: chrome://downloads → look at the recent failed entry. There’s often a “Keep” or “Recover” link if Safe Browsing flagged but didn’t fully delete the file. Clicking “Keep” downloads it anyway, with the understanding that Chrome thought it risky.
If “Keep” isn’t visible: Safe Browsing flagged the file as definitively malicious and refused to save it. Override path: chrome://settings/security → set protection level to “No protection (not recommended)” → retry download → set it back to “Standard protection” afterward. This is risky behaviour — only do it for files from known-trustworthy sources.
Where downloads actually go
The default save location is the Downloads folder, but Chrome can be configured to ask each time or save to a specific path. If Chrome can’t write to the save location (permission denied, drive full, removable drive disconnected), downloads fail silently.
Check: chrome://settings/downloads → “Location” should be set to a valid, writable folder. Common breaks:
- Path points to an external drive that’s no longer connected
- Path was on OneDrive and OneDrive sync is paused or unlinked
- Free space on the destination drive is critically low
- Folder permissions changed (after running ownership commands or after sharing changes)
Reset to default: change the location back to C:Users[yourname]Downloads. Try the download again. If it works after the reset, your previous location had a permission or path issue.
Antivirus blocking the file
Antivirus software intercepts downloads either before or after Chrome saves them. Bitdefender, Norton, Kaspersky, McAfee all do real-time scanning of downloads. Sometimes they identify legitimate files as threats and quarantine them silently, leaving you with a “successfully downloaded” file that’s actually been moved by the AV.
Check your antivirus quarantine: open the AV interface → look for “Quarantine,” “Vault,” or “History” → see if the missing file is there. If yes: restore it (only if you trust the source) and add an exclusion for the file or folder.
For downloads that fail at exactly the moment they should complete: AV is intercepting. Disable real-time scanning temporarily to test, or add Chrome’s download folder to the AV exclusion list (not all of Chrome — that’s overkill — just the Downloads folder). This usually resolves the conflict.
The Chrome safety check intervention
Chrome has a “Safety Check” feature that periodically reviews extensions, passwords, and security state. Sometimes Safety Check enables additional download protections that cause new blocking. If downloads suddenly started failing without you changing anything:
Go to chrome://settings/safetyCheck → click “Check now” → review what Chrome found. If it identified any malicious extensions or unsafe sites you’ve visited recently, that’s the context. After resolving any flags, downloads usually return to normal.
Our guide on Chrome connection problems covers the broader page-loading issues that sometimes manifest as download failures, and our Chrome stability troubleshooting covers download interruptions caused by Chrome processes crashing mid-transfer. For Safe Browsing policy details and how to whitelist specific sites or domains, Google’s Chrome security documentation covers the security settings page and reporting false-positive Safe Browsing flags.
Network interruptions during download
Long downloads can fail when the network drops even briefly. Chrome attempts to resume but doesn’t always succeed, especially for files larger than a gigabyte or on flaky Wi-Fi connections. Symptoms: download progress freezes, then “Failed – Network error” appears.
For chronic large-file download failures: switch to wired ethernet if possible while downloading. Or pause downloads in chrome://downloads when you know the network is about to be interrupted (someone walking through a Wi-Fi dead zone, switching networks, etc.). Pause first → resume after stable connection returns. Chrome handles paused-resumed downloads more reliably than dropped-and-retried ones.
For users on metered or limited connections: chrome://settings/downloads → “Ask where to save each file before downloading” → On. This makes Chrome stop and confirm before starting a large download, preventing accidental data overage on cellular connections.
Specific file type blocks
Chrome implements stricter handling for “dangerous” file types: .exe, .msi, .bat, .ps1, .scr, .com. Files of these types get extra warnings, and some are blocked outright if from HTTP (non-HTTPS) sources.
Symptom: certain extensions fail consistently while others work fine on the same site. Specifically: any executable from a non-HTTPS site usually fails. Chrome’s “mixed content” download block intentionally prevents downloading executables over insecure connections.
Solution: if the site has an HTTPS version, switch to it. If only HTTP is available: this is a security warning worth heeding — find an HTTPS source for the file. Sometimes the actual file is hosted on HTTPS but the download link goes through HTTP redirects; right-click the link → “Copy link address” → paste in address bar starting with https:// → see if HTTPS works.
Extension interfering with downloads
Some extensions hook into Chrome’s download flow. Download managers (Internet Download Manager browser extension), ad blockers (sometimes catch download links if they look like ad redirects), and security tools all can block or intercept downloads.
The Incognito test from earlier already isolates this — if downloads work in Incognito and fail in normal Chrome, an extension is the suspect. Disable extensions in chrome://extensions one at a time to find which.
Common offenders: any extension claiming to “speed up downloads” or “manage downloads better.” These hook the download flow aggressively and break it as often as they help. Removing them usually resolves the issue.
Disk space
Sounds basic but it’s worth checking. Settings → System → Storage → look at the destination drive. If you’re under a few GB free space, downloads fail in inconsistent ways — some complete, some halt midway, error messages are inconsistent. Clear space first; retry downloads.
Specifically for downloads to OneDrive folders: even if the local drive has space, OneDrive’s online quota matters. If your OneDrive is full and you’re downloading to a synced folder, the local download might succeed but sync fails — the file appears, then disappears. Check OneDrive’s storage indicator in the system tray.
Group Policy in managed environments
Corporate networks often restrict downloads by file type, file size, or source domain. Symptoms specific to managed devices:
- Downloads work on personal machine but not work laptop
- Specific file types blocked regardless of source
- “Download blocked by your administrator” message
- Certain corporate sites’ downloads work but external ones fail
These are policy restrictions, not Chrome bugs. Contact IT if you need a specific download for legitimate work purposes. They can sometimes whitelist specific sites or file types case-by-case.
| Failure pattern | Most likely cause | Quick fix |
| “Failed – Forbidden” or “Virus scan failed” | Safe Browsing or antivirus block | Check chrome://downloads for Keep option; review AV quarantine |
| Halts at random percentages | Network instability or file source slow | Switch to wired; pause/resume; try off-peak hours |
| Specific file types only fail | Chrome’s executable-over-HTTP block | Find HTTPS source for the file |
| Works in Incognito, fails normally | Extension interference | Disable extensions; identify offender |
| Download button does nothing | JavaScript broken or pop-up blocker | Allow pop-ups for site; check console for errors |
| “Download blocked by administrator” | Group Policy restriction | Contact IT; can’t be bypassed locally |
Most download failures fall into one of these patterns and resolve quickly once you know which. The Incognito test plus chrome://downloads inspection covers most diagnostic ground in under 2 minutes.
When a download succeeds but the file won’t open
Slightly different issue but often grouped under “downloads not working.” File downloads completely, you click to open, and get errors — “Windows can’t open this file,” corrupt archive, blocked by Windows SmartScreen.
For SmartScreen blocks on executables: the file ran fine on the source site but Windows refuses to launch it. Right-click the file → Properties → at the bottom, if there’s an “Unblock” checkbox → check it → Apply. SmartScreen marks downloaded files with a “Zone.Identifier” stream that triggers protection; unblocking removes it.
For corrupt archives (.zip, .rar): file may have downloaded incompletely without Chrome reporting it. Re-download. If still corrupt, the source file itself is damaged — try a mirror or different source.
For files that just won’t open: Windows might not have an associated app. Right-click → “Open with” → pick the appropriate application, or install one if you don’t have it (e.g., free 7-Zip for unusual archive formats).
Resume support and download accelerators
For very large files (multi-GB ISO images, software bundles), Chrome’s default download performance can be a bottleneck. Chrome downloads as a single HTTP stream, not multi-threaded.
Tools like JDownloader or Internet Download Manager use multi-threaded downloads, which on fast connections can be 2-5x quicker, and they handle resume more robustly when the connection drops. These are useful for users who download large files frequently. For casual users, the default Chrome behaviour is fine.
Some sites also offer torrent or P2P alternatives for big files specifically because HTTP downloads aren’t reliable at that scale. For a 10GB game patch, a torrent client may genuinely be the better choice — both for speed and for resume reliability.
A note on temporary download files
Chrome downloads files with a .crdownload extension first, then renames them when complete. If Chrome crashes mid-download or Windows shuts down unexpectedly, you can be left with stranded .crdownload files in your Downloads folder.
These accumulate over time and sometimes cause Chrome to refuse new downloads of files with the same name (it sees the partial and isn’t sure how to handle it). Periodic cleanup:
- Win+R →
%USERPROFILE%Downloads→ Enter - Sort by file extension or name
- Delete any .crdownload files (they’re partial downloads, not the actual file)
- Restart Chrome; retry downloads
This is housekeeping rather than fix-an-actual-problem, but worth knowing about if your Downloads folder is getting cluttered with mystery files.
When the website itself is the issue
Sometimes downloads fail because the source site is the problem, not Chrome. Specifically:
- Download links that work for some users but not others (suggests a session or geographic block)
- Files served via expired CDN links that 404 silently
- Download buttons that require sign-in but the site doesn’t make this obvious
- Free download mirrors that have been compromised — Chrome’s Safe Browsing correctly blocks these
Quick way to verify: copy the download URL → paste in a different browser (Firefox, Edge) → does the download work there? If it fails in multiple browsers, the source is the problem. If it works in others but not Chrome: a Chrome-specific block (Safe Browsing, extension) is the cause.
For sites that consistently fail downloads only in Chrome: report to the site owner. They might have a configuration issue with their HTTPS, their headers, or how they’re serving files.
When all else fails — Chrome profile reset
If downloads have stopped working across multiple sites, file types, and after testing in Incognito, the profile state is the suspect. Reset Chrome via chrome://settings/reset → “Restore settings to their original defaults.” This doesn’t lose bookmarks or saved passwords but resets extensions, content settings, and various preferences.
If reset doesn’t help: test with a brand new profile (Chrome profile menu → Add → continue without account). If downloads work in the new profile but fail in the original, your main profile is corrupted. Sign in to Chrome Sync on the new profile to restore bookmarks and passwords; switch to using it.
If even a new profile fails to download: it’s not Chrome — it’s the system level. SmartScreen, antivirus, firewall, or Group Policy restrictions are blocking downloads regardless of which Chrome user is making the request.
For most cases though, the basics — Incognito test, Safe Browsing check, antivirus quarantine review — cover what’s actually going wrong. The diagnostic flow doesn’t need to be complicated; it just needs to follow the symptoms in the right order.
One last thing worth knowing: Chrome’s download manager UI shows a brief “this file might be dangerous” warning that disappears after a few seconds. If you click away too quickly, the file might appear to fail silently when really Chrome was waiting for you to acknowledge. chrome://downloads shows the current state of every download including any that need your input — always worth checking there before assuming a download outright failed. If this sounds familiar, Chrome Cookies Not Working is worth a look.
