On-demand scanners: scope and results
Understand manual malware scans, quick versus full scope, update and completion checks, and why a clean scan does not answer every recovery question.
An on-demand scanner inspects a selected device or file scope when a scan is explicitly requested, rather than providing continuous checks on device activity.
Also called: manual malware scan, manual antivirus scan, on-demand scanningA requested inspection
An on-demand scanner runs a check when you explicitly request one. It can be a separate utility or a feature inside an antivirus that also provides other protection. The term describes how the inspection is initiated, rather than a specific detection engine or guarantee of removal.
Microsoft Safety Scanner is a concrete Windows example: it runs only when manually triggered and does not replace continuous antimalware protection. Other applications combine requested scans with real-time protection.
Scheduled scans can use the same inspection functions, but a schedule supplies their trigger. This matters when reading product documentation: some vendors group manual and scheduled inspection under broader on-demand scanning terminology. Check what starts the scan and what it examines, rather than deciding from the label alone.
A manual scan is useful for an explicit question, such as checking a selected download or inspecting supported locations after a security alert. It does not monitor everything that happens after it finishes.
Scope matters more than the name
Quick, full, and custom scans are common labels, but their contents differ across products. A full scan is broader in the product’s defined scope; it is not a literal inspection of every possible object, account, or device.
| Scan description | Typical purpose | Question to check in the documentation |
|---|---|---|
| Quick scan | Inspect locations prioritized by the product | Which startup, memory, or other locations are included? |
| Full scan | Inspect a broader set of supported storage locations | Which drives and object types are actually covered? |
| Custom scan | Inspect selected files or locations | What was selected, omitted, or excluded? |
| Offline scan | Inspect from a separate operating environment | What scope and platform does that scanner support? |
Microsoft’s scan documentation describes Defender’s quick, full, and custom scans, including how configuration affects drive coverage. Malwarebytes’ scan-type documentation describes a different set of modes, with platform-specific availability.
Choose the documented scope that addresses the question. A narrowly selected file check cannot answer whether other locations contain malware. A longer scan is not automatically the best first step for every incident; follow the product’s guidance and any administrator instructions.
Prepare the scan without creating another exposure
Use the vendor’s official download or installed application. Check compatibility, the current version, and update status before relying on a result. Do not obtain a scanner through an unexpected pop-up claiming that your device is infected.
Portable scanners can have special freshness requirements. Microsoft’s Safety Scanner expires ten days after download; its documentation recommends obtaining the latest copy before each scan. That product-specific rule should not be applied to every utility, but it illustrates why an old saved executable needs checking.
Keep the device on reliable power for a lengthy scan and save work before any mode that requires a restart. If credible active compromise requires isolation, arrange necessary downloads through a trusted device or IT. A routine scan preparation step should not cause you to reconnect an actively compromised system without considering containment.
Completion, exclusions, and unreadable objects
A scan that stops early supplies a different observation from one that completes its defined scope. Check the final status and reported errors. “No threats found so far” during a scan is not its final result.
Objects can fall outside an engine’s supported inspection or configured limits. ESET’s ThreatSense documentation illustrates limits for object size and nested archives. Encrypted content, exclusions, inaccessible locations, and scan settings all need product-specific interpretation. Do not reduce inspection limits merely to make a scan finish faster without understanding the consequence.
Record what the tool says it checked, skipped, or could not inspect. A large count of scanned objects is useful operational information, but it is not a completeness certificate.
Findings and recovery are separate questions
If the tool finds something, read the exact item and completed response. Windows Protection History distinguishes recorded threats and actions. Keep items in quarantine while resolving uncertain classifications.
A completed scan with no findings means the tool reported no detections within that inspection. It cannot prove there was no earlier execution or that a stolen password, session, or file is now safe. Continuing symptoms also deserve diagnosis, because software faults can resemble infection and some compromises need further investigation.
Use the Windows scan route for the site’s next step. A second opinion or offline scan should address a specific unresolved question. Repeating scans indefinitely is less useful than recording their scope, results, and what remains unanswered.
Sources & documentation
Sources checked on 6 Oct 2026. Documentation research does not establish independent testing.