Windows Event ID 4701: A scheduled task was disabled
Written when a scheduled task is disabled. It can catch disabling of defensive or monitoring tasks (defense evasion), or temporarily hiding a malicious task.
Overview
The subcategory is Audit Other Object Access Events. It is generated when an existing task is switched to disabled. Paired with enabling 4700, it tracks changes in a task’s run state.
How it is triggered
- When a task is switched to disabled (GUI /
schtasks /change /disable/ API).
Security review points
- If a legitimate monitoring, backup, or security-related task is disabled, it can mean defenses are being weakened. Check the target task and subject.
- There is also a pattern where an attacker disables a malicious task after it runs to avoid detection (re-enabling it later with 4700).
Notes for log review
- It also occurs during legitimate operation and maintenance. Alerting narrowed to disabling of important defensive tasks is effective.
- Tie it to the creation-time content (4698) to evaluate what was disabled.
MITRE ATT&CK mapping
| Technique | Tactic | What this event shows |
|---|---|---|
| T1685 Disable or Modify Tools | Defense Impairment | Disabling legitimate monitoring or security tasks |
| T1053.005 Scheduled Task | Execution, Persistence, Privilege Escalation | Disabling a malicious task after it runs to keep a low profile |
Mapping as of ATT&CK v19.2. To search by technique, see the ATT&CK reverse lookup.
Detection rules
SigmaHQ has 2 and Microsoft Sentinel has 1 public detection rules that use this event ID as a condition.
| Rule | Type | Severity |
|---|---|---|
| Important Scheduled Task Deleted/Disabled | Sigma | High |
| Gain Code Execution on ADFS Server via SMB + Remote Service or Scheduled Task | Sentinel analytics rule | Medium |
| Defrag Deactivation - Security | Sigma (threat-specific) | Medium |
Rules are collected from SigmaHQ r2026-07-01 and from Azure-Sentinel as of 2026-10-09, limited to those whose conditions include this event ID. Sentinel rules are limited to those that query the SecurityEvent or WindowsEvent table. “Threat-specific” rules target a particular threat group or malware, and “needs setup” rules require values for your environment. Severity is the value each rule’s author assigned.
Key fields
| Field | Meaning |
|---|---|
Task Name | The disabled task name |
Subject\Account Name | The account that performed the operation |