Glossary

Real-time protection: continuous checks

Learn how continuous antivirus protection differs from manual scans, what enabled protection depends on, and how to interpret a disabled or blocked status.

Definition

Real-time protection performs security checks during device activity, such as file access or program execution, instead of depending only on scans started separately.

Also called: on-access protection, real-time scanning, continuous antivirus protection

Protection during ordinary activity

Real-time protection performs checks as the device is used. Depending on the product and enabled components, those checks can respond to file access, application activity, or other supported events. The user does not have to start a separate scan for every new download or program launch.

The term describes timing and operation. It does not identify one exclusive detection method. Microsoft’s always-on protection documentation includes file and process monitoring alongside behavioral and heuristic features in Defender Antivirus.

An illustrative difference is a downloaded installer: real-time protection may inspect relevant activity when the file arrives or is accessed, whereas a manual scan checks its selected scope when you request it. The exact events intercepted depend on the product. Neither description guarantees that every threat will be recognized.

Continuous checks and separate scans

Protection or scanWhat starts the checkWhy the distinction matters
Real-time protectionSupported device eventsHelps respond to activity between separate scans
On-demand scanA user or another explicit requestExamines a selected scope at a particular time
Scheduled scanA configured scheduleAdds periodic inspection without requiring a manual start
Offline scanA scan in a separate operating environmentChanges the conditions of inspection

An antivirus can provide several of these. A completed on-demand scan does not enable real-time protection if that feature is unavailable or disabled. Conversely, enabled real-time protection does not establish that a requested full scan finished.

The inspection methods can also overlap. Signatures help recognize patterns, and behavior monitoring assesses activity. “Real-time” should not be interpreted as a distinct malware category or as an assurance that a response happens before every possible effect.

Check the actual product and plan

Feature availability can vary by operating system, subscription, and trial state. Malwarebytes’ Windows and Mac documentation describes its paid protection layers and platform differences. Its current free-versus-paid table separately lists scanning and protection entitlements.

The practical lesson is to read the installed application’s current status rather than infer protection from the presence of a scan button. A trial ending can change available features. A feature list for another operating system or an older release may not describe your installation.

Do not infer that every free scanner behaves alike, either. Pricing labels are not standardized descriptions of monitoring, scan scope, or scheduling. Verify those functions directly when assessing the setup.

Enabled protection has dependencies

A green status is useful, but it needs context. Updates, product health, permissions, configuration, and supported operating-system integration affect what a security product can do. A component waiting for a required permission is not fully functioning merely because the application opens.

Microsoft’s update documentation separates security intelligence, engine, and platform updates. Cloud protection has a connectivity dependency. A local check can therefore have different capabilities from an otherwise similar check with supported cloud services available.

On managed equipment, an administrator may control settings. Microsoft’s always-on guidance also discusses policy and tamper protection. A setting that you cannot change is not, by itself, proof of malware. Use IT’s support process rather than trying to bypass management controls.

If protection appears disabled

Check which product is providing protection and what its status actually says. Distinguish a disabled component from a license notification, update error, required restart, or centrally controlled setting. The site’s Defender-disabled symptom article is the next route for that particular Windows symptom.

Avoid repeatedly switching protection off to complete an unexpected installation. If a program appears to be wrongly blocked, preserve the finding and follow the false-positive investigation. Broad exclusions change which future activity is checked, so they should not be used as a substitute for resolving authenticity.

A second-opinion scanner can supplement investigation without becoming the continuous protector. Do not assume installing several products with active monitoring improves coverage; confirm their supported coexistence arrangements first.

Reading a real-time block

A block concerns a recorded event. Review the item, time, and completed action in the product’s history. Windows Protection History illustrates separating findings from remediation status.

If a download was intercepted, that differs from detecting a process after it started. Keep isolated items in quarantine and follow any remaining supported actions. When earlier execution or account exposure is unresolved, continuous protection’s current status cannot answer those historical questions. Follow-up should address the evidence of the incident as well as restoring a functioning protection setup.

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