Microsoft-Windows-RasServer

23 events across 1 channel

Event	Title	Channel	Sample
50001	IPMGM was unable to initialize a critical section.	Operational	N
50002	IPMGM was unable to create a heap.	Operational	N
50003	IPMGM was unable to allocate memory from its heap.	Operational	N
50004	IPMGM received a start request when it was already running.	Operational	N
50005	IPMGM was unable to create a synchronization object.	Operational	N
50006	IPMGM was unable to create an event.	Operational	N
50007	IPMGM was unable to create a semaphore.	Operational	N
50008	IPMGM has started successfully.	Operational	N
50009	IPMGM could not schedule a task to be executed.	Operational	N
50010	IPMGM could not find the protocol component (param1, param2).	Operational	N
50011	Protocol component has already registered with IPMGM	Operational	N
50012	IPMGM failed to register the protocol component.	Operational	N
50013	The protocol component that is attempting to deregister is currently enabled on …	Operational	N
50014	This protocol component has already been enabled on this interface	Operational	N
50015	Specified interface was not present in MGM.	Operational	N
50016	Another routing protocol component has already been enabled on this interface.	Operational	N
50017	IGMP is not enabled on this interface	Operational	N
50018	No routing protocol has been enabled on this interface	Operational	N
50019	The handle specified by the protocol component is not valid.	Operational	N
50020	Interface cannot be deleted because IGMP is still active on this interface.	Operational	N
50021	Failed to set timer for forwarding entry.	Operational	N
50022	Failed to register with RTM.	Operational	N
50099	IPMGM has stopped.	Operational	N

Event ID 50001: IPMGM was unable to initialize a critical section.

Provider: Microsoft-Windows-RasServer
Channel: Operational

Description

IPMGM was unable to initialize a critical section. The data is the exception code.

Message #

IPMGM was unable to initialize a critical section. The data is the exception code.

Event ID 50002: IPMGM was unable to create a heap.

Provider: Microsoft-Windows-RasServer
Channel: Operational

Description

IPMGM was unable to create a heap. The data is the error code.

Message #

IPMGM was unable to create a heap. The data is the error code.

Event ID 50003: IPMGM was unable to allocate memory from its heap.

Provider: Microsoft-Windows-RasServer
Channel: Operational

Description

IPMGM was unable to allocate memory from its heap. The data is the error code.

Message #

IPMGM was unable to allocate memory from its heap. The data is the error code.

Event ID 50004: IPMGM received a start request when it was already running.

Provider: Microsoft-Windows-RasServer
Channel: Operational

Description

IPMGM received a start request when it was already running.

Message #

IPMGM received a start request when it was already running.

Event ID 50005: IPMGM was unable to create a synchronization object.

Provider: Microsoft-Windows-RasServer
Channel: Operational

Description

IPMGM was unable to create a synchronization object. The data is the error code.

Message #

IPMGM was unable to create a synchronization object. The data is the error code.

Event ID 50006: IPMGM was unable to create an event.

Provider: Microsoft-Windows-RasServer
Channel: Operational

Description

IPMGM was unable to create an event. The data is the error code.

Message #

IPMGM was unable to create an event. The data is the error code.

Event ID 50007: IPMGM was unable to create a semaphore.

Provider: Microsoft-Windows-RasServer
Channel: Operational

Description

IPMGM was unable to create a semaphore. The data is the error code.

Message #

IPMGM was unable to create a semaphore. The data is the error code.

Event ID 50008: IPMGM has started successfully.

Provider: Microsoft-Windows-RasServer
Channel: Operational

Description

IPMGM has started successfully.

Message #

IPMGM has started successfully.

Event ID 50009: IPMGM could not schedule a task to be executed.

Provider: Microsoft-Windows-RasServer
Channel: Operational

Description

IPMGM could not schedule a task to be executed. This may have been caused by a memory allocation failure. The data is the error code.

Message #

IPMGM could not schedule a task to be executed. This may have been caused by a memory allocation failure. The data is the error code.

Event ID 50010: IPMGM could not find the protocol component (param1, param2).

Provider: Microsoft-Windows-RasServer
Channel: Operational

Description

IPMGM could not find the protocol component (param1, param2).

Message #

IPMGM could not find the protocol component (%1, %2)

Fields #

Name	Description
`param1` UnicodeString
`param2` UnicodeString

Event ID 50011: Protocol component has already registered with IPMGM

Provider: Microsoft-Windows-RasServer
Channel: Operational

Description

Protocol component has already registered with IPMGM.

Message #

Protocol component has already registered with IPMGM

Event ID 50012: IPMGM failed to register the protocol component.

Provider: Microsoft-Windows-RasServer
Channel: Operational

Description

IPMGM failed to register the protocol component. The data is in the error code.

Message #

IPMGM failed to register the protocol component. The data is in the error code.

Event ID 50013: The protocol component that is attempting to deregister is currently enabled on one or more interfaces.

Provider: Microsoft-Windows-RasServer
Channel: Operational

Description

The protocol component that is attempting to deregister is currently enabled on one or more interfaces.

Message #

The protocol component that is attempting to deregister is currently enabled on one or more interfaces.

Event ID 50014: This protocol component has already been enabled on this interface

Provider: Microsoft-Windows-RasServer
Channel: Operational

Description

This protocol component has already been enabled on this interface.

Message #

This protocol component has already been enabled on this interface

Event ID 50015: Specified interface was not present in MGM.

Provider: Microsoft-Windows-RasServer
Channel: Operational

Description

Specified interface was not present in MGM.

Message #

Specified interface was not present in MGM.

Event ID 50016: Another routing protocol component has already been enabled on this interface.

Provider: Microsoft-Windows-RasServer
Channel: Operational

Description

Another routing protocol component has already been enabled on this interface. Only one routing protocol component may be enabled on an interface at any time.

Message #

Another routing protocol component has already been enabled on this interface.  Only one routing protocol component may be  enabled on an interface at any time.

Event ID 50017: IGMP is not enabled on this interface

Provider: Microsoft-Windows-RasServer
Channel: Operational

Description

IGMP is not enabled on this interface.

Message #

IGMP is not enabled on this interface

Event ID 50018: No routing protocol has been enabled on this interface

Provider: Microsoft-Windows-RasServer
Channel: Operational

Description

No routing protocol has been enabled on this interface.

Message #

No routing protocol has been enabled on this interface

Event ID 50019: The handle specified by the protocol component is not valid.

Provider: Microsoft-Windows-RasServer
Channel: Operational

Description

The handle specified by the protocol component is not valid. This maybe because the protocol component is not registered with IPMGM.

Message #

The handle specified by the protocol component is not valid. This maybe because the protocol component is not registered with IPMGM

Event ID 50020: Interface cannot be deleted because IGMP is still active on this interface.

Provider: Microsoft-Windows-RasServer
Channel: Operational

Description

Interface cannot be deleted because IGMP is still active on this interface.

Message #

Interface cannot be deleted because IGMP is still active on  this interface.

Event ID 50021: Failed to set timer for forwarding entry.

Provider: Microsoft-Windows-RasServer
Channel: Operational

Description

Failed to set timer for forwarding entry. The error code is in the data.

Message #

Failed to set timer for forwarding entry.   The error code is in the data.

Event ID 50022: Failed to register with RTM.

Provider: Microsoft-Windows-RasServer
Channel: Operational

Description

Failed to register with RTM. The error code is in the data.

Message #

Failed to register with RTM. The error code is in the data.

Event ID 50099: IPMGM has stopped.

Provider: Microsoft-Windows-RasServer
Channel: Operational

Description

IPMGM has stopped.

Message #

IPMGM has stopped.

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 29d13147-1c2e-48ec-9994-e29dfe496eb3

Defined in rtm.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)

Microsoft-Windows-RasServer

Event ID 50001: IPMGM was unable to initialize a critical section.

Description

Message #

Event ID 50002: IPMGM was unable to create a heap.

Description

Message #

Event ID 50003: IPMGM was unable to allocate memory from its heap.

Description

Message #

Event ID 50004: IPMGM received a start request when it was already running.

Description

Message #

Event ID 50005: IPMGM was unable to create a synchronization object.

Description

Message #

Event ID 50006: IPMGM was unable to create an event.

Description

Message #

Event ID 50007: IPMGM was unable to create a semaphore.

Description

Message #

Event ID 50008: IPMGM has started successfully.

Description

Message #

Event ID 50009: IPMGM could not schedule a task to be executed.

Description

Message #

Event ID 50010: IPMGM could not find the protocol component (param1, param2).

Description

Message #

Fields #

Event ID 50011: Protocol component has already registered with IPMGM

Description

Message #

Event ID 50012: IPMGM failed to register the protocol component.

Description

Message #

Event ID 50013: The protocol component that is attempting to deregister is currently enabled on one or more interfaces.

Description

Message #

Event ID 50014: This protocol component has already been enabled on this interface

Description

Message #

Event ID 50015: Specified interface was not present in MGM.

Description

Message #

Event ID 50016: Another routing protocol component has already been enabled on this interface.

Description

Message #

Event ID 50017: IGMP is not enabled on this interface

Description

Message #

Event ID 50018: No routing protocol has been enabled on this interface

Description

Message #

Event ID 50019: The handle specified by the protocol component is not valid.

Description

Message #

Event ID 50020: Interface cannot be deleted because IGMP is still active on this interface.

Description

Message #

Event ID 50021: Failed to set timer for forwarding entry.

Description

Message #

Event ID 50022: Failed to register with RTM.

Description

Message #

Event ID 50099: IPMGM has stopped.

Description

Message #

Provenance

Downloads