Microsoft-Windows-Diagnosis-Scheduled

20 events across 1 channel

Event	Title	Channel	Sample
1	The scheduled diagnostic task has detected a change in state for a check …	Operational	N
2	Scheduled diagnostics have started.	Operational	Y
3	Scheduled diagnostics have been completed.	Operational	Y
4	Scheduled diagnostics have been disabled.	Operational	N
5	The scheduled diagnostic task has started initializing a diagnostic package.	Operational	Y
6	The scheduled diagnostic task has completed initialization of a diagnostic …	Operational	Y
7	The scheduled diagnostic task has started troubleshooting a diagnostic package.	Operational	Y
8	The scheduled diagnostic task has completed troubleshooting a diagnostic …	Operational	Y
9	The scheduled diagnostic task has detected a root cause.	Operational	Y
10	The scheduled diagnostic task has started resolving a detected root cause.	Operational	Y
11	The scheduled diagnostic task has completed resolving a detected root cause.	Operational	Y
12	The scheduled diagnostic task has started verifying the fix applied for a …	Operational	Y
13	The scheduled diagnostic task has determined that the root cause no longer …	Operational	Y
14	The scheduled diagnostic task has determined that the root cause continues to …	Operational	Y
15	The scheduled diagnostic task has encountered an error.	Operational	N
96	TEST: One or more rootcauses were detected and a package wide notification was …	Operational	N
97	TEST: No rootcauses were detected and a package wide reset notification was …	Operational	N
98	TEST: A rootcause was detected and a rootcause wide notification was raised.	Operational	N
99	TEST: A root cause does not exist and a root cause reset notification was …	Operational	N
100	System maintenance detected issues requiring your attention.	Operational	Y

Event ID 1: The scheduled diagnostic task has detected a change in state for a check registered in Security and Maintenance.

Provider: Microsoft-Windows-Diagnosis-Scheduled
Channel: Operational

Description

The scheduled diagnostic task has detected a change in state for a check registered in Security and Maintenance.

Message #

The scheduled diagnostic task has detected a change in state for a check registered in Security and Maintenance.

Event ID 2: Scheduled diagnostics have started.

Provider: Microsoft-Windows-Diagnosis-Scheduled
Channel: Operational
Level: Informational

Description

Scheduled diagnostics have started.

Message #

Scheduled diagnostics have started.

Example Event #

{
  "system": {
    "provider": "Microsoft-Windows-Diagnosis-Scheduled",
    "guid": "{40AB57C2-1C53-4DF9-9324-FF7CF898A02C}",
    "event_source_name": "",
    "event_id": 2,
    "version": 0,
    "level": 4,
    "task": 0,
    "opcode": 0,
    "keywords": -9223372002495037440,
    "time_created": "2026-06-13T05:39:32.0352489+00:00",
    "event_record_id": 22,
    "correlation": {},
    "execution": {
      "process_id": 5480,
      "thread_id": 4340
    },
    "channel": "Microsoft-Windows-Diagnosis-Scheduled/Operational",
    "computer": "telemetry-DC-a.cell-a.ludus.domain",
    "security": {
      "user_id": "S-1-5-21-1006758700-2167138679-1475694448-1105"
    }
  },
  "event_data": {},
  "message": "Scheduled diagnostics have started."
}

Event ID 3: Scheduled diagnostics have been completed.

Provider: Microsoft-Windows-Diagnosis-Scheduled
Channel: Operational
Level: Informational

Description

Scheduled diagnostics have been completed.

Message #

Scheduled diagnostics have been completed.

Example Event #

{
  "system": {
    "provider": "Microsoft-Windows-Diagnosis-Scheduled",
    "guid": "{40AB57C2-1C53-4DF9-9324-FF7CF898A02C}",
    "event_source_name": "",
    "event_id": 3,
    "version": 0,
    "level": 4,
    "task": 0,
    "opcode": 0,
    "keywords": -9223372002495037440,
    "time_created": "2026-06-13T05:39:36.5298759+00:00",
    "event_record_id": 28,
    "correlation": {},
    "execution": {
      "process_id": 5480,
      "thread_id": 5084
    },
    "channel": "Microsoft-Windows-Diagnosis-Scheduled/Operational",
    "computer": "telemetry-DC-a.cell-a.ludus.domain",
    "security": {
      "user_id": "S-1-5-21-1006758700-2167138679-1475694448-1105"
    }
  },
  "event_data": {},
  "message": "Scheduled diagnostics have been completed."
}

Event ID 4: Scheduled diagnostics have been disabled.

Provider: Microsoft-Windows-Diagnosis-Scheduled
Channel: Operational

Description

Scheduled diagnostics have been disabled.

Message #

Scheduled diagnostics have been disabled.

Event ID 5: The scheduled diagnostic task has started initializing a diagnostic package.

Provider: Microsoft-Windows-Diagnosis-Scheduled
Channel: Operational
Level: Informational

Description

The scheduled diagnostic task has started initializing a diagnostic package.

Message #

The scheduled diagnostic task has started initializing a diagnostic package.

Fields #

Name	Description
`PackagePath` UnicodeString

Example Event #

{
  "system": {
    "provider": "Microsoft-Windows-Diagnosis-Scheduled",
    "guid": "{40AB57C2-1C53-4DF9-9324-FF7CF898A02C}",
    "event_source_name": "",
    "event_id": 5,
    "version": 0,
    "level": 4,
    "task": 0,
    "opcode": 0,
    "keywords": -9223372002495037440,
    "time_created": "2026-06-13T05:39:32.0385046+00:00",
    "event_record_id": 23,
    "correlation": {},
    "execution": {
      "process_id": 5480,
      "thread_id": 5084
    },
    "channel": "Microsoft-Windows-Diagnosis-Scheduled/Operational",
    "computer": "telemetry-DC-a.cell-a.ludus.domain",
    "security": {
      "user_id": "S-1-5-21-1006758700-2167138679-1475694448-1105"
    }
  },
  "event_data": {
    "PackagePath": "C:\\Windows\\diagnostics\\scheduled\\Maintenance"
  },
  "message": "The scheduled diagnostic task has started initializing a diagnostic package."
}

Event ID 6: The scheduled diagnostic task has completed initialization of a diagnostic package.

Provider: Microsoft-Windows-Diagnosis-Scheduled
Channel: Operational
Level: Informational

Description

The scheduled diagnostic task has completed initialization of a diagnostic package.

Message #

The scheduled diagnostic task has completed initialization of a diagnostic package.

Fields #

Name	Description
`PackageID` UnicodeString

Example Event #

{
  "system": {
    "provider": "Microsoft-Windows-Diagnosis-Scheduled",
    "guid": "{40AB57C2-1C53-4DF9-9324-FF7CF898A02C}",
    "event_source_name": "",
    "event_id": 6,
    "version": 0,
    "level": 4,
    "task": 0,
    "opcode": 0,
    "keywords": -9223372002495037440,
    "time_created": "2026-06-13T05:39:32.6595304+00:00",
    "event_record_id": 24,
    "correlation": {},
    "execution": {
      "process_id": 5480,
      "thread_id": 5084
    },
    "channel": "Microsoft-Windows-Diagnosis-Scheduled/Operational",
    "computer": "telemetry-DC-a.cell-a.ludus.domain",
    "security": {
      "user_id": "S-1-5-21-1006758700-2167138679-1475694448-1105"
    }
  },
  "event_data": {
    "PackageID": "MaintenanceDiagnostic"
  },
  "message": "The scheduled diagnostic task has completed initialization of a diagnostic package."
}

Event ID 7: The scheduled diagnostic task has started troubleshooting a diagnostic package.

Provider: Microsoft-Windows-Diagnosis-Scheduled
Channel: Operational
Level: Informational

Description

The scheduled diagnostic task has started troubleshooting a diagnostic package.

Message #

The scheduled diagnostic task has started troubleshooting a diagnostic package.

Fields #

Name	Description
`PackageID` UnicodeString

Example Event #

{
  "system": {
    "provider": "Microsoft-Windows-Diagnosis-Scheduled",
    "guid": "{40AB57C2-1C53-4DF9-9324-FF7CF898A02C}",
    "event_source_name": "",
    "event_id": 7,
    "version": 0,
    "level": 4,
    "task": 0,
    "opcode": 0,
    "keywords": -9223372002495037440,
    "time_created": "2026-06-13T05:39:32.6595322+00:00",
    "event_record_id": 25,
    "correlation": {},
    "execution": {
      "process_id": 5480,
      "thread_id": 5084
    },
    "channel": "Microsoft-Windows-Diagnosis-Scheduled/Operational",
    "computer": "telemetry-DC-a.cell-a.ludus.domain",
    "security": {
      "user_id": "S-1-5-21-1006758700-2167138679-1475694448-1105"
    }
  },
  "event_data": {
    "PackageID": "MaintenanceDiagnostic"
  },
  "message": "The scheduled diagnostic task has started troubleshooting a diagnostic package."
}

Event ID 8: The scheduled diagnostic task has completed troubleshooting a diagnostic package.

Provider: Microsoft-Windows-Diagnosis-Scheduled
Channel: Operational
Level: Informational

Description

The scheduled diagnostic task has completed troubleshooting a diagnostic package.

Message #

The scheduled diagnostic task has completed troubleshooting a diagnostic package.

Fields #

Name	Description
`PackageID` UnicodeString
`RootCauseCount` Int32

Example Event #

{
  "system": {
    "provider": "Microsoft-Windows-Diagnosis-Scheduled",
    "guid": "{40AB57C2-1C53-4DF9-9324-FF7CF898A02C}",
    "event_source_name": "",
    "event_id": 8,
    "version": 0,
    "level": 4,
    "task": 0,
    "opcode": 0,
    "keywords": -9223372002495037440,
    "time_created": "2026-06-13T05:39:36.5128341+00:00",
    "event_record_id": 26,
    "correlation": {},
    "execution": {
      "process_id": 5480,
      "thread_id": 5084
    },
    "channel": "Microsoft-Windows-Diagnosis-Scheduled/Operational",
    "computer": "telemetry-DC-a.cell-a.ludus.domain",
    "security": {
      "user_id": "S-1-5-21-1006758700-2167138679-1475694448-1105"
    }
  },
  "event_data": {
    "PackageID": "MaintenanceDiagnostic",
    "RootCauseCount": "2"
  },
  "message": "The scheduled diagnostic task has completed troubleshooting a diagnostic package."
}

Event ID 9: The scheduled diagnostic task has detected a root cause.

Provider: Microsoft-Windows-Diagnosis-Scheduled
Channel: Operational

Description

The scheduled diagnostic task has detected a root cause.

Message #

The scheduled diagnostic task has detected a root cause.

Fields #

Name	Description
`RootCauseID` UnicodeString
`RootCauseName` UnicodeString
`RootCauseDescription` UnicodeString

Example Event #

{
  "system": {
    "provider": "Microsoft-Windows-Diagnosis-Scheduled",
    "event_id": 9,
    "level": "Information",
    "task": null,
    "opcode": "Info",
    "time_created": "2026-04-20T21:20:41.5898747+00:00",
    "computer": "JD-DC01-2022.ludus.domain",
    "channel": "Microsoft-Windows-Diagnosis-Scheduled/Operational"
  },
  "event_data": {
    "RootCauseID": "RC_DiagnosticHistory/DefaultInstanceId",
    "RootCauseName": "Troubleshooting history is taking up disk space",
    "RootCauseDescription": "Troubleshooting history and logs are currently taking up %UnwantedSpace%MB of disk space."
  }
}

Event ID 10: The scheduled diagnostic task has started resolving a detected root cause.

Provider: Microsoft-Windows-Diagnosis-Scheduled
Channel: Operational

Description

The scheduled diagnostic task has started resolving a detected root cause.

Message #

The scheduled diagnostic task has started resolving a detected root cause.

Fields #

Name	Description
`RootCauseID` UnicodeString
`ResolutionID` UnicodeString

Example Event #

{
  "system": {
    "provider": "Microsoft-Windows-Diagnosis-Scheduled",
    "event_id": 10,
    "level": "Information",
    "task": null,
    "opcode": "Info",
    "time_created": "2026-04-20T21:20:41.8700060+00:00",
    "computer": "JD-DC01-2022.ludus.domain",
    "channel": "Microsoft-Windows-Diagnosis-Scheduled/Operational"
  },
  "event_data": {
    "ResolutionID": "RC_DiagnosticHistory/DefaultInstanceId/RS_AdminDiagnosticHistory",
    "RootCauseID": "RC_DiagnosticHistory/DefaultInstanceId"
  }
}

Event ID 11: The scheduled diagnostic task has completed resolving a detected root cause.

Provider: Microsoft-Windows-Diagnosis-Scheduled
Channel: Operational

Description

The scheduled diagnostic task has completed resolving a detected root cause.

Message #

The scheduled diagnostic task has completed resolving a detected root cause.

Fields #

Name	Description
`RootCauseID` UnicodeString
`ResolutionID` UnicodeString

Example Event #

{
  "system": {
    "provider": "Microsoft-Windows-Diagnosis-Scheduled",
    "event_id": 11,
    "level": "Information",
    "task": null,
    "opcode": "Info",
    "time_created": "2026-04-20T21:20:42.0122980+00:00",
    "computer": "JD-DC01-2022.ludus.domain",
    "channel": "Microsoft-Windows-Diagnosis-Scheduled/Operational"
  },
  "event_data": {
    "ResolutionID": "RC_DiagnosticHistory/DefaultInstanceId/RS_AdminDiagnosticHistory",
    "RootCauseID": "RC_DiagnosticHistory/DefaultInstanceId"
  }
}

Event ID 12: The scheduled diagnostic task has started verifying the fix applied for a detected root cause.

Provider: Microsoft-Windows-Diagnosis-Scheduled
Channel: Operational

Description

The scheduled diagnostic task has started verifying the fix applied for a detected root cause.

Message #

The scheduled diagnostic task has started verifying the fix applied for a detected root cause.

Fields #

Name	Description
`RootCauseID` UnicodeString

Example Event #

{
  "system": {
    "provider": "Microsoft-Windows-Diagnosis-Scheduled",
    "event_id": 12,
    "level": "Information",
    "task": null,
    "opcode": "Info",
    "time_created": "2026-04-20T21:20:42.0122993+00:00",
    "computer": "JD-DC01-2022.ludus.domain",
    "channel": "Microsoft-Windows-Diagnosis-Scheduled/Operational"
  },
  "event_data": {
    "RootCauseID": "RC_DiagnosticHistory/DefaultInstanceId"
  }
}

Event ID 13: The scheduled diagnostic task has determined that the root cause no longer exists.

Provider: Microsoft-Windows-Diagnosis-Scheduled
Channel: Operational

Description

The scheduled diagnostic task has determined that the root cause no longer exists.

Message #

The scheduled diagnostic task has determined that the root cause no longer exists.

Fields #

Name	Description
`RootCauseID` UnicodeString

Example Event #

{
  "system": {
    "provider": "Microsoft-Windows-Diagnosis-Scheduled",
    "event_id": 13,
    "level": "Information",
    "task": null,
    "opcode": "Info",
    "time_created": "2026-04-20T21:20:42.0908167+00:00",
    "computer": "JD-DC01-2022.ludus.domain",
    "channel": "Microsoft-Windows-Diagnosis-Scheduled/Operational"
  },
  "event_data": {
    "RootCauseID": "RC_DiagnosticHistory/DefaultInstanceId"
  }
}

Event ID 14: The scheduled diagnostic task has determined that the root cause continues to exist.

Provider: Microsoft-Windows-Diagnosis-Scheduled
Channel: Operational

Description

The scheduled diagnostic task has determined that the root cause continues to exist.

Message #

The scheduled diagnostic task has determined that the root cause continues to exist.

Fields #

Name	Description
`RootCauseID` UnicodeString

Example Event #

{
  "system": {
    "provider": "Microsoft-Windows-Diagnosis-Scheduled",
    "event_id": 14,
    "level": "Information",
    "task": null,
    "opcode": "Info",
    "time_created": "2026-04-20T21:20:41.8699918+00:00",
    "computer": "JD-DC01-2022.ludus.domain",
    "channel": "Microsoft-Windows-Diagnosis-Scheduled/Operational"
  },
  "event_data": {
    "RootCauseID": "RC_DiagnosticHistory/DefaultInstanceId"
  }
}

Event ID 15: The scheduled diagnostic task has encountered an error.

Provider: Microsoft-Windows-Diagnosis-Scheduled
Channel: Operational

Description

The scheduled diagnostic task has encountered an error.

Message #

The scheduled diagnostic task has encountered an error.

Fields #

Name	Description
`PackageID` UnicodeString
`ErrorCode` UInt32

Event ID 96: TEST: One or more rootcauses were detected and a package wide notification was raised.

Provider: Microsoft-Windows-Diagnosis-Scheduled
Channel: Operational

Description

TEST: One or more rootcauses were detected and a package wide notification was raised.

Message #

TEST: One or more rootcauses were detected and a package wide notification was raised.

Fields #

Name	Description
`hc_stateid` UInt32
`Data1` UnicodeString
`Data2` UnicodeString

Event ID 97: TEST: No rootcauses were detected and a package wide reset notification was raised.

Provider: Microsoft-Windows-Diagnosis-Scheduled
Channel: Operational

Description

TEST: No rootcauses were detected and a package wide reset notification was raised.

Message #

TEST: No rootcauses were detected and a package wide reset notification was raised.

Fields #

Name	Description
`hc_stateid` UInt32

Event ID 98: TEST: A rootcause was detected and a rootcause wide notification was raised.

Provider: Microsoft-Windows-Diagnosis-Scheduled
Channel: Operational

Description

TEST: A rootcause was detected and a rootcause wide notification was raised.

Message #

TEST: A rootcause was detected and a rootcause wide notification was raised.

Fields #

Name	Description
`hc_stateid` UInt32
`Data1` UnicodeString
`Data2` UnicodeString

Event ID 99: TEST: A root cause does not exist and a root cause reset notification was raised.

Provider: Microsoft-Windows-Diagnosis-Scheduled
Channel: Operational

Description

TEST: A root cause does not exist and a root cause reset notification was raised.

Message #

TEST: A root cause does not exist and a root cause reset notification was raised.

Fields #

Name	Description
`hc_stateid` UInt32

Event ID 100: System maintenance detected issues requiring your attention.

Provider: Microsoft-Windows-Diagnosis-Scheduled
Channel: Operational
Level: Critical

Description

System maintenance detected issues requiring your attention. A notification was sent to Security and Maintenance.

Message #

System maintenance detected issues requiring your attention. A notification was sent to Security and Maintenance.

Fields #

Name	Description
`hc_stateid` UInt32

Example Event #

{
  "system": {
    "provider": "Microsoft-Windows-Diagnosis-Scheduled",
    "guid": "{40AB57C2-1C53-4DF9-9324-FF7CF898A02C}",
    "event_source_name": "",
    "event_id": 100,
    "version": 0,
    "level": 1,
    "task": 0,
    "opcode": 0,
    "keywords": -9223372019674906624,
    "time_created": "2026-06-13T05:39:36.5128381+00:00",
    "event_record_id": 27,
    "correlation": {},
    "execution": {
      "process_id": 5480,
      "thread_id": 5084
    },
    "channel": "Microsoft-Windows-Diagnosis-Scheduled/Operational",
    "computer": "telemetry-DC-a.cell-a.ludus.domain",
    "security": {
      "user_id": "S-1-5-21-1006758700-2167138679-1475694448-1105"
    }
  },
  "event_data": {
    "hc_stateid": "0"
  },
  "message": "System maintenance detected issues requiring your attention. A notification was sent to Security and Maintenance."
}

Provenance

Where this provider's schema came from, and which Windows build it was observed on. Windows can change a provider's event schema between builds, so use this to judge whether it matches the build you collect from.

ETW provider GUID 40ab57c2-1c53-4df9-9324-ff7cf898a02c

Defined in sdiagschd.dll, which carries the event manifest.

Observed on:

WS2022-20348.4893, schema read from the registered manifest, binary version 10.0.20348.1, captured 2026-06-02
Win11-26200.6584, schema read from the registered manifest, binary version 10.0.26100.1, captured 2026-06-02

`j` / `k`	Scroll down / up
`d` / `u`	Half-page down / up
`gg` / `G`	Top / bottom
`h` / `l`	History back / forward
`f`	Follow link (`Shift` = new tab)
`/`	Focus search
`?`	Toggle this help
`↑` / `↓`	Navigate search results
`Enter`	Open highlighted result
`Esc`	Close results / dialog

`type:`	`events` / `rules` / `providers`
`vendor:`	`sigma` / `elastic` / `splunk` / `kusto` / `chronicle` (vendor name alone also works: `sigma:`, `kql:`, `secops:`…)
`tactic:`	TA-id, slug, or name: `credential_access`, `TA0006`
`technique:`	technique or sub-technique ID: `T1003`, `T1003.001` (alias `tech:`)
`severity:`	`critical` / `high` / `medium` / `low` / `informational` (alias `sev:`)
`risk_score`	Numeric comparison on the Elastic risk score (0 to 100): `risk_score>50`, `risk_score<=20`, `risk_score=99` (alias `risk`; Elastic rules only)
`stages:`	Rules with exactly N pipeline stages
`correlation:`	`single_event` / `sequence` / `alternatives` / `alternatives_cross_log` / `all_required` / `correlated`
`with:`	Co-occurrence event-id; stacks (`with:4624 with:4769`) to require all, while a comma list in one occurrence (`with:4624,4769`) is an either-or group. Implies multi-event
`like:`	Structural neighbors of a rule slug (equivalents + subsumption stricter / broader): `like:comsvcs_lsass_memory_dump-splunk-sysmon`
`groupby:`	Entity-grouping substring match against `group_by_keys`: `groupby:user`, `groupby:host`
`uses:`	Rules whose predicate tree touches the field (any kind, any value): `uses:CommandLine`
`excludes:`	Rules with top-level `not()` clauses on the field (FP whitelists): `excludes:ParentImage`
`field:` / `value:`	Predicate search; narrows rule cards to those with a matching leaf and drives the indicator tier. Unquoted = substring, wildcards allowed (`value:mimikatz`)
`indicator:`	Shorthand for `field:F value:V`: `indicator:Image=*\powershell.exe`
`kind:`	Filter by predicate kind. Narrows rule cards to those carrying a matching predicate leaf (`vendor:elastic kind:cidr_match`) and drives the indicator tier: `contains` / `starts_with` / `ends_with` / `regex` / `cidr` / `eq` / `in` … (operator aliases `op:`/`match:`)
`has:` / `no:`	`sample`, `field`, `notes`, `refs`, `trace`, `thirdparty`, `rule`, `pattern`, `timewindow`, `threshold`, `newterms`, `sigma`/`elastic`/`splunk`/`kusto`/`chronicle`
`-op:val`	Exclude matches; works on most operators but not `type:`/`like:`/`has:`/`no:` (use `no:<flag>` to exclude a rule flag): `tactic:execution -vendor:splunk`. Standalone `-kind:`/`-field:`/`-value:` drop every rule carrying a matching predicate leaf (`type:rules -kind:is_null`)
`field:"…"` / `value:"…"`	Quoted value = anchored exact match (also allows spaces): `value:"net user"`
`a,b`	Comma = OR inside one operator (`vendor:sigma,elastic`, `severity:high,critical`); repeating a facet merges the same way. `field:`/`value:` never split (literal commas)
`vendors:` / `stage:`	Singular and plural spellings fold to the canonical operator and value: `tactics:` = `tactic:`, `type:event` = `type:events`, `correlation:sequences` = `correlation:sequence`, `has:thresholds` = `has:threshold`
`"quoted phrase"`	Exact-match a multi-word phrase (free text)