Every Download Says Virus Detected in Chrome and Edge: Safe Fix

If every download says “Virus detected” in Chrome or Edge, open the download details and check the active antivirus log before allowing a file. A named threat needs a file-safety decision. If unrelated downloads from official sites also fail, especially with “Virus scan failed”, check the security provider and browser settings instead of assuming every file is infected. Keep protection enabled while you identify which case applies.

Chrome and Edge failing while Firefox works is a useful comparison, not a verdict on the file. Record the exact error first: a failed scan, a named antivirus detection, and a browser reputation warning need different next steps.

What does the exact download message mean?

• “Failed – Virus detected” or “Couldn’t download – Virus detected”: check the antivirus event at the same time and the affected filename. If it names a threat, keep that file blocked and investigate the source and detection.
• “Virus scan failed”: the download’s security check did not complete successfully. Google groups this with antivirus-related download failures; the wording alone does not establish whether the file is malicious. Look for a matching security event, then check the provider if ordinary downloads fail too.
• “Not commonly downloaded” in Edge: this is a SmartScreen reputation warning, not the same as a named antivirus detection. A new or unfamiliar program can lack reputation. Verify the publisher and official source before deciding whether to keep it; familiarity with a filename is not enough.
• “Disk full,” “Insufficient permissions,” “Forbidden,” or a network error: follow the storage, folder, server or network error. These messages are not virus verdicts.

Open chrome://downloads or edge://downloads to read the failed item’s message. A webpage or notification claiming that several viruses were found is a different issue from an actual failed item in the browser’s Downloads list.

Decide whether one file or every file is blocked

• One file shows a named threat in Protection History. Keep that file blocked. Verify its source, publisher, signature, and detection before restoring it. Use the single-file virus-block decision guide.
• PDFs, images, and other ordinary files fail in both Chrome and Edge. Check the active antivirus, Protection History, browser policy, download folder, and security-product health. Do not assume all files are infected.
• Firefox downloads the same official-source file. This is a diagnostic clue that the browsers use different download/security paths. It does not prove the file is safe or identify the broken component by itself.
• Every browser fails, or the error is “Disk full,” “Forbidden,” or “No permission”. Follow the exact error. Storage, folder permissions, the server, network controls, or a systemwide security product may be responsible.
• Only one browser profile fails. Test a fresh profile without extensions or browser sync. An extension, profile setting, or managed browser policy may be involved.

How to fix every-download Virus detected errors safely

1. Record the exact error before changing anything. Chrome may say Failed – Virus detected or Virus scan failed; Edge may say Couldn’t download – Virus detected. Also record the file type, source site, time, and whether the download fails immediately or at the end. These details separate a scan rejection from network, disk, or permission errors.
2. Open Windows Security > Virus & threat protection > Protection history. Match events to the download time. Read the detection name, status and affected item, not just the card heading. A matching event gives you a specific file or action to investigate. An empty Defender history does not rule out blocking: if another antivirus is active, its log is the next place to check. If no provider records the failure, continue with the controlled test below rather than assuming the file is safe.
3. Check the active antivirus log. Windows Security shows which provider is active. If a third-party antivirus is installed, open its activity, quarantine, or event log. An old product that was disabled or partly uninstalled can still leave services or registration behind. Update or repair the active product through its official installer before removing it. Do not run two real-time antivirus engines together.
4. Use one controlled official-source test. Choose a small public PDF or image you expect to be legitimate from an official government, browser-vendor, or software-vendor site. Download it without opening it, and note the result in Chrome and Edge. Do not use a crack, mod, password-protected archive, unknown executable, or the original suspicious file as your test. If that download succeeds and only the original file fails, stop the systemwide repair: investigate the original file. If unrelated files from different official sites fail in both browsers, record whether each attempt creates a security event. Repeated failures without a matching event justify checking provider health, profiles and policy; they do not prove a particular component is broken.
5. Test a fresh profile without extensions or sync. Use Chrome Guest mode or a new unsynced Chrome profile, then a new unsynced Edge profile. Private windows are a weaker comparison if extensions have been allowed to run there. If the new profile works, review extensions and download-related settings in the affected profile one at a time. A new profile still inherits device policy and antivirus checks. If both browsers fail there too, focus on the shared provider or policy instead of repeatedly reinstalling Chrome.
6. Check the download location. Confirm that the folder exists, has free space, and lets you create a normal text file. In Edge, review edge://settings/downloads; in Chrome, review chrome://settings/downloads. A folder or permission failure usually has different wording, so do not treat it as a virus verdict.
7. Inspect browser policy without deleting it. Open chrome://policy and edge://policy. On a work or school computer, export the policy list and contact IT. On a personal PC, unexpected download restrictions or a forced download directory should lead back to the utility, script, or security product that created them. Do not delete the entire browser policy tree.
8. Update, restart, and test again. Install current Chrome and Edge updates, Windows updates, and antivirus security intelligence, then restart Windows. A restart can clear a stuck scan broker or finish a security-product update. If the security product reports errors or an unhealthy status after restarting, follow its official repair instructions. If it appears healthy and the error persists, continue with the profile/policy checks and the escalation steps below instead of cycling protection off and on.
9. Repair the security component that is actually failing. If Windows Security pages are blank or unavailable, use the Windows Security repair checklist. If Edge reports a managed SmartScreen policy, use the SmartScreen policy guide. For a third-party antivirus, use that vendor’s official repair or clean-uninstall path, then confirm that Windows Security shows one active provider.

If every download still fails

After updating or repairing the active security product, restart and repeat the same official-source download with protection enabled. If it now succeeds in both browsers and no new security event appears, stop changing settings. Investigate any original file that remains blocked separately.

If both browsers still fail in fresh profiles, collect the exact error, failure time, browser versions, active antivirus name, file type/source, and whether the matching event is present in its log. Include what changed just before the problem began, such as a security-product update or uninstall. Give this short record to the security vendor or your IT administrator so they can identify the failing component. Share logs privately; remove account names, personal paths and sensitive URLs from public screenshots. Do not keep trying registry values or reinstall Windows solely because of this message.

When a malware scan is the right next step

A threat blocked during download does not by itself mean the file ran. Run a full malware scan if a suspicious installer or script already ran, the same threat reappears without another download, security exclusions appeared unexpectedly, or Windows reports incomplete remediation. Those signs can mean the blocked download is only one visible symptom. A download error that simply persists after reboot can still be a provider or policy problem.

A security tool may quarantine the file you can see while a loader, scheduled task, service, browser change, Defender exclusion, or bundled module remains. In that situation, download and install Gridinsoft Anti-Malware from its official site using the button below, update its detection database, and run a Full Scan to check for detections, hidden files, startup entries, scheduled tasks, bundled applications, browser changes, and persistence. Remove confirmed detections, restart, and scan again if the alert returns. A clean scan adds evidence; it cannot guarantee that every file is safe or that no compromise occurred.

If one legitimate file alone is detected, do not broaden the issue into a system repair. Keep it quarantined, collect the hash, source, signer, and exact detection, then follow the false-positive reporting process. For an executable, the EXE safety checklist helps verify the publisher and path before you consider restoring anything.

Do not “fix” the error by disabling the scan

Many forum and video fixes tell readers to turn off Safe Browsing, SmartScreen, real-time protection, or the Windows attachment scan. That can make the message disappear while leaving the cause unresolved and removing the check that would stop a real threat.

• Do not add exclusions for the whole Downloads folder, browser process, file type, or drive.
• Do not set a policy to allow all downloads merely because several official-source files failed.
• Do not change ScanWithAntiVirus to suppress Attachment Manager notification. Microsoft documents that this policy controls whether Windows calls registered antivirus programs; bypassing the call is not a repair.
• Do not download the original suspicious file through Firefox just because Firefox works.
• Do not clear Protection History or antivirus logs until you have recorded the matching event.

The safe end state is simple: one active and healthy antivirus provider, current security intelligence, normal browser policy, a writable download folder, and the tested official-source files downloading without protection being disabled.

FAQ

References

1. Google. “Fix file download errors.” Google Chrome Help, accessed November 8, 2026. Chrome download-error definitions.
2. Microsoft. “Troubleshoot download failures.” Microsoft Learn, updated April 6, 2026, accessed November 8, 2026. Edge download-failure checklist.
3. Microsoft. “Policy CSP – AttachmentManager.” Microsoft Learn, updated October 14, 2026, accessed November 8, 2026. Attachment Manager antivirus-notification policy.
4. Microsoft. “Microsoft Edge support for Microsoft Defender SmartScreen.” Microsoft Learn, accessed November 8, 2026. Download reputation and warning types.