Glossary

Quarantine: what happens to a detected file?

Understand how antivirus quarantine differs from deletion and blocking, what an isolated item tells you, and how to handle a suspected false positive.

Definition

Quarantine is a security product action that isolates a detected item from normal use while retaining it under the product’s control for review or later handling.

Also called: antivirus quarantine, quarantined item

Why security software uses quarantine

Quarantine separates a detected item from ordinary use without immediately making the decision irreversible. That gives the product and the user a way to handle something suspicious while retaining a recovery option if the detection is later found to be mistaken.

The implementation varies between products. The useful distinction is the outcome: the item is controlled by the security application rather than available for normal use in its original location. Manage it through that application’s interface, not by opening or moving files in a quarantine storage folder.

For example, suppose a scanner isolates an installer you downloaded yesterday. That action concerns the detected installer. You still need to check whether you ran it, whether the report mentions other items, and whether additional action is required. The word “quarantined” alone does not answer those questions.

Quarantine, deletion, and blocking are different

Action or statusWhat it generally tells youWhat to verify
QuarantineThe product isolated a detected item and retained it under its control.Whether the action succeeded and whether anything else needs attention.
Delete or removeThe product removed the identified item rather than keeping a normal restore option.What was removed and whether recovery is possible from another trusted source.
BlockThe product prevented a particular action, access, or execution.Whether it also removed or quarantined an item; product terminology varies.
RestoreAn isolated item is returned for ordinary use.Whether there is reliable evidence that releasing it is appropriate.
Allow or excludeA detection or protection rule is overridden for the specified item or scope.Exactly what will stop being checked or blocked.

Read the complete event rather than interpreting one word in isolation. Microsoft’s Protection History documentation distinguishes a quarantined threat from one blocked and removed, and from remediation that did not finish.

What to check after an item is quarantined

Open the security product directly and review the event. Look for the item path, detection name, time, action, and final status. Check whether the report requests a restart or another action, and whether the same item is being detected again.

Keep the context of the file in mind. An installer in your downloads, a browser component, and a file used by an important application may require different follow-up. A filename that looks familiar is useful context, but it is not proof of safety.

On Windows, Microsoft’s documented route is Windows Security → Virus & threat protection → Protection history. Its quarantine-management guidance describes how to locate isolated items. Use that view to inspect the event; do not restore a file simply to test whether it causes a problem.

Does quarantine mean the device is clean?

It means an action was taken on the identified item, assuming the report confirms success. It does not establish that every part of an incident has been resolved.

A blocked installer that never ran presents a different question from malicious code that ran before detection. An account could also need recovery even after harmful code is removed. NIST’s incident-handling guidance treats removing malware and recovering the affected environment as separate parts of a response.

Follow the product’s recommended actions and investigate continuing symptoms. If detections recur or the application reports incomplete remediation, use official support or a qualified technician. On a work or school device, involve its administrator. Our Windows scanning guide explains the next scanning route without treating a clean result as a guarantee.

Handling a suspected false positive

A false positive is a detection that incorrectly identifies a benign item as a threat. Familiarity with the program, a clean result from one other scanner, or an immediate need to use the file is not enough to establish that conclusion. The linked article explains how to gather evidence and seek a correction.

Review the exact item and the vendor’s reason for detecting it. If it is important to your work, contact the application publisher and the security vendor through their official channels. Keep the event details available so they can assess the same file and version. Do not upload confidential documents or business files to a public analysis service without permission.

Leaving, deleting, or restoring the item

Leaving an item quarantined gives you time to resolve uncertainty. How long it remains available depends on the product and its configured retention behavior; there is no universal retention period.

If you decide to delete an isolated item, understand the recovery consequence first. Malwarebytes’ quarantine documentation states that deleting it from quarantine removes the item and prevents restoration through that list. An item you might need to recover deserves a considered decision, not a routine “empty everything” action.

If an item has been verified as benign, follow the product’s supported restoration instructions. Restore and allow are different decisions: putting back a file need not mean excluding its folder, related applications, or future downloads from protection.

The aim is to choose an action whose consequences you understand. Quarantine is useful precisely because isolation, investigation, and permanent deletion do not have to happen in the same step.

Sources & documentation

Sources checked on 6 Oct 2026. Documentation research does not establish independent testing.

MalwareCleanupTools

Guides based on official documentation. About our content · Corrections policy