--- title: "Configure Endpoint Security for Windows to prevent concurrent scans" slug: "configure-endpoint-security-for-windows-to-prevent-concurrent-scans" updated: 2026-11-16T11:35:38Z published: 2026-11-16T11:35:38Z canonical: "docs.trellix.com/configure-endpoint-security-for-windows-to-prevent-concurrent-scans" --- > ## Documentation Index > Fetch the complete documentation index at: https://docs.trellix.com/llms.txt > Use this file to discover all available pages before exploring further. # Configure Endpoint Security for Windows to prevent concurrent scans ## Configure Endpoint Security for Windows to prevent concurrent scans To prevent system performance issues caused by overlapping scans, configure Endpoint Security for Windows (ENSW) to drop incoming scan tasks when an existing Full Scan, Quick Scan task or Custom on Demand Scan is already running. When configured, ENSW ignores new scan requests and reports the dropped task status to Trellix ePolicy Orchestrator (Trellix ePO). ### Prevent concurrent scans in a policy Follow these steps to enable scan task suppression in the policy settings: 1. Select **Menu > Policy > Policy Catalog**. 2. Select **Endpoint Security Windows** from the **Product** drop-down list. 3. Select **On-Demand Scan** from the **Category** drop-down list. 4. Select the policy name to edit, or select **Duplicate** to create a policy copy. 5. Select **Performance**. 6. Select **Avoid concurrent scan**. 7. Select **Save**. ### Concurrent scan task behavior When **Avoid concurrent scan** is enabled, ENSW enforces the following operational rules: | Condition | Client behavior | Trellix ePO reporting | | --- | --- | --- | | A Full Scan, Quick Scan, or Custom Scan is active when a new scan task arrives. | ENSW cancels or ignores the incoming scan task. The active scan continues without interruption. The UI will display a message saying that the scan ‘was skipped because the concurrent scan is disabled and another on-demand scan is already running.’ | ENSW sends a status event stating the new task was dropped because an existing task is executing. | | No scan is active when a scan task arrives. | ENSW starts the scan task immediately. | ENSW reports normal task execution status. | #### When an on-demand scan is skipped, the system records an entry in the threat event log with the following details: - Event Category: Task skipped - Event ID: 34904 - Analyzer detection method: Identifies the specific scan that was skipped - Event description: On-demand scan skipped