Microsoft-Windows-ProcessExitMonitor

4 events across 2 channels

Event	Title	Channel
3000	The process 'param1' exited with exit code param2.	Application
3001	The process 'param1' was terminated by the process 'param2' with termination …	Application
1073744824	The process 'param1' exited with exit code param2.	Operational
1073744825	The process 'param1' was terminated by the process 'param2' with termination …	Operational

Event ID 3000: The process 'param1' exited with exit code param2.

Provider: Microsoft-Windows-ProcessExitMonitor
Channel: Application

Description

The process 'param1' exited with exit code param2. The creation time for the exiting process was 0xparam3.

Message #

The process '%1' exited with exit code %2. The creation time for the exiting process was 0x%3.

Fields #

Name	Description
`param1` UnicodeString
`param2` UnicodeString
`param3` UnicodeString
`ExitingProcessId` UnicodeString

Detection Rules #

View all rules referencing this event →

Splunk # view in coverage

Windows Event Triggered Image File Execution Options Injection source: The following analytic identifies the creation or modification of Image File Execution Options (IFEO) registry keys, detected via EventCode 3000 in the Application channel. This detection leverages Windows Event Logs to monitor for process…

Event ID 3001: The process 'param1' was terminated by the process 'param2' with termination code param3.

Provider: Microsoft-Windows-ProcessExitMonitor
Channel: Application
Level: Informational

Description

The process 'param1' was terminated by the process 'param2' with termination code param3. The creation time for the exiting process was 0xparam4.

Message #

The process '%1' was terminated by the process '%2' with termination code %3. The creation time for the exiting process was 0x%4.

Fields #

Name	Description
`param1` UnicodeString
`param2` UnicodeString
`param3` UnicodeString
`param4` UnicodeString
`ExitingProcessId` UnicodeString
`InitiatingProcessId` UnicodeString

Example Event #

{
  "system": {
    "provider": "Microsoft-Windows-ProcessExitMonitor",
    "guid": "{FD771D53-8492-4057-8E35-8C02813AF49B}",
    "event_source_name": "Process Exit Monitor",
    "event_id": 3001,
    "version": 0,
    "level": 4,
    "task": 0,
    "opcode": 0,
    "keywords": 36028797018963968,
    "time_created": "2021-06-09T04:58:49.287418Z",
    "event_record_id": 32887,
    "correlation": {},
    "execution": {
      "process_id": 0,
      "thread_id": 0
    },
    "channel": "Application",
    "computer": "MSEDGEWIN10",
    "security": {
      "user_id": "S-1-5-21-3461203602-4096304019-2269080069-1000"
    }
  },
  "event_data": {
    "param1": "C:\\Windows\\System32\\lsass.exe",
    "param2": "C:\\Users\\IEUser\\Desktop\\LsassSilentProcessExit.exe",
    "param3": "0",
    "param4": "01d75d3714c3280e"
  }
}

References #

Example event sourced from https://github.com/NextronSystems/evtx-baseline

Event ID 1073744824: The process 'param1' exited with exit code param2.

Provider: Microsoft-Windows-ProcessExitMonitor
Channel: Operational

Description

The process 'param1' exited with exit code param2. The creation time for the exiting process was 0xparam3.

Message #

The process '%1' exited with exit code %2. The creation time for the exiting process was 0x%3.

Fields #

Name	Description
`param1` UnicodeString	The process '
`param2` UnicodeString	' exited with exit code
`param3` UnicodeString	. The creation time for the exiting process was 0x
`ExitingProcessId` UnicodeString

Event ID 1073744825: The process 'param1' was terminated by the process 'param2' with termination code param3.

Provider: Microsoft-Windows-ProcessExitMonitor
Channel: Operational

Description

The process 'param1' was terminated by the process 'param2' with termination code param3. The creation time for the exiting process was 0xparam4.

Message #

The process '%1' was terminated by the process '%2' with termination code %3. The creation time for the exiting process was 0x%4.

Fields #

Name	Description
`param1` UnicodeString	The process '
`param2` UnicodeString	' was terminated by the process '
`param3` UnicodeString	' with termination code
`param4` UnicodeString	. The creation time for the exiting process was 0x
`ExitingProcessId` UnicodeString
`InitiatingProcessId` UnicodeString

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 fd771d53-8492-4057-8e35-8c02813af49b

Defined in werfault.exe, which carries the event manifest.

Observed on:

WS2022-20348.4893 · schema read from the registered manifest · captured 2026-06-02
Win11-26200.6584 · schema read from the registered manifest · binary version 10.0.26100.5074 · captured 2026-06-02

Downloads

Credits

Microsoft - authored the ETW manifests and PDBs the schema comes from
jdu2600 - the event-schema TSV format this catalog adopted
nasbench - the tool that dumps registered providers and manifests

`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:`)
`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)

Microsoft-Windows-ProcessExitMonitor

Event ID 3000: The process 'param1' exited with exit code param2.

Description

Message #

Fields #

Detection Rules #

Splunk # view in coverage

Event ID 3001: The process 'param1' was terminated by the process 'param2' with termination code param3.

Description

Message #

Fields #

Example Event #

References #

Event ID 1073744824: The process 'param1' exited with exit code param2.

Description

Message #

Fields #

Event ID 1073744825: The process 'param1' was terminated by the process 'param2' with termination code param3.

Description

Message #

Fields #

Provenance

Downloads

Credits

Keyboard shortcuts

Search operators