Microsoft-Windows-Network-Setup

24 events across 1 channel

Event	Title	Channel	Sample
100	The Network Setup service is starting	Diagnostic	N
101	The Network Setup service has started	Diagnostic	N
102	The Network Setup service failed to start with error Code.	Diagnostic	N
110	The Network Setup service will stop due to inactivity	Diagnostic	N
111	The Network Setup service will stop due to a user request	Diagnostic	N
112	The Network Setup service is stopping	Diagnostic	N
113	The Network Setup service has stopped	Diagnostic	N
200	A new transaction has started	Diagnostic	N
201	A transaction has been closed	Diagnostic	N
202	Network Setup has begun calculating new driver bindings	Diagnostic	N
203	Network Setup has finished calculating new driver bindings	Diagnostic	N
204	Network Setup has begun committing changes to the registry	Diagnostic	N
205	Network Setup has finished committing changes to the registry	Diagnostic	N
300	Begin API Api on transaction TransactionGuid.	Diagnostic	N
301	End API Api on transaction TransactionGuid.	Diagnostic	N
400	Begin calling into plugin PluginName.	Diagnostic	N
401	End calling into plugin	Diagnostic	N
500	Begin operation OperationType on ObjectType in transaction TransactionGuid: …	Diagnostic	N
501	Operation TransactionGuid ended with code Code.	Diagnostic	N
600	Begin API Api.	Diagnostic	N
601	End API with status code Code.	Diagnostic	N
700	Invoking API ComponentId on Notify Object for TransactionGuid.	Diagnostic	N
701	The Notify Object returned with status: Code.	Diagnostic	N
702	An error occurred while invoking the Notify Object.	Diagnostic	N

Event ID 100: The Network Setup service is starting

Provider: Microsoft-Windows-Network-Setup
Channel: Diagnostic
Task: Runservice
Opcode: Start

Description

The Network Setup service is starting.

Message #

The Network Setup service is starting

Event ID 101: The Network Setup service has started

Provider: Microsoft-Windows-Network-Setup
Channel: Diagnostic
Task: Runservice

Description

The Network Setup service has started.

Message #

The Network Setup service has started

Event ID 102: The Network Setup service failed to start with error Code.

Provider: Microsoft-Windows-Network-Setup
Channel: Diagnostic
Task: Runservice

Description

The Network Setup service failed to start with error Code.

Message #

The Network Setup service failed to start with error %1

Fields #

Name	Description
`Code` Int32

Event ID 110: The Network Setup service will stop due to inactivity

Provider: Microsoft-Windows-Network-Setup
Channel: Diagnostic
Task: Runservice

Description

The Network Setup service will stop due to inactivity.

Message #

The Network Setup service will stop due to inactivity

Event ID 111: The Network Setup service will stop due to a user request

Provider: Microsoft-Windows-Network-Setup
Channel: Diagnostic
Task: Runservice

Description

The Network Setup service will stop due to a user request.

Message #

The Network Setup service will stop due to a user request

Event ID 112: The Network Setup service is stopping

Provider: Microsoft-Windows-Network-Setup
Channel: Diagnostic
Task: Runservice

Description

The Network Setup service is stopping.

Message #

The Network Setup service is stopping

Event ID 113: The Network Setup service has stopped

Provider: Microsoft-Windows-Network-Setup
Channel: Diagnostic
Task: Runservice
Opcode: Stop

Description

The Network Setup service has stopped.

Message #

The Network Setup service has stopped

Event ID 200: A new transaction has started

Provider: Microsoft-Windows-Network-Setup
Channel: Diagnostic
Task: Transaction
Opcode: Start

Description

A new transaction has started.

Message #

A new transaction has started

Fields #

Name	Description
`TransactionGuid` GUID
`EnvironmentType` UInt32

Event ID 201: A transaction has been closed

Provider: Microsoft-Windows-Network-Setup
Channel: Diagnostic
Task: Transaction
Opcode: Stop

Description

A transaction has been closed.

Message #

A transaction has been closed

Fields #

Name	Description
`TransactionGuid` GUID

Event ID 202: Network Setup has begun calculating new driver bindings

Provider: Microsoft-Windows-Network-Setup
Channel: Diagnostic
Task: Calculatebindings
Opcode: Start

Description

Network Setup has begun calculating new driver bindings.

Message #

Network Setup has begun calculating new driver bindings

Fields #

Name	Description
`TransactionGuid` GUID

Event ID 203: Network Setup has finished calculating new driver bindings

Provider: Microsoft-Windows-Network-Setup
Channel: Diagnostic
Task: Calculatebindings
Opcode: Stop

Description

Network Setup has finished calculating new driver bindings.

Message #

Network Setup has finished calculating new driver bindings

Fields #

Name	Description
`TransactionGuid` GUID

Event ID 204: Network Setup has begun committing changes to the registry

Provider: Microsoft-Windows-Network-Setup
Channel: Diagnostic
Task: Commitchanges
Opcode: Start

Description

Network Setup has begun committing changes to the registry.

Message #

Network Setup has begun committing changes to the registry

Fields #

Name	Description
`TransactionGuid` GUID

Event ID 205: Network Setup has finished committing changes to the registry

Provider: Microsoft-Windows-Network-Setup
Channel: Diagnostic
Task: Commitchanges
Opcode: Stop

Description

Network Setup has finished committing changes to the registry.

Message #

Network Setup has finished committing changes to the registry

Fields #

Name	Description
`TransactionGuid` GUID

Event ID 300: Begin API Api on transaction TransactionGuid.

Provider: Microsoft-Windows-Network-Setup
Channel: Diagnostic
Task: ExternalAPI
Opcode: Start

Description

Begin API Api on transaction TransactionGuid.

Message #

Begin API %2 on transaction %1

Fields #

Name	Description
`TransactionGuid` GUID
`Api` UInt32

Event ID 301: End API Api on transaction TransactionGuid.

Provider: Microsoft-Windows-Network-Setup
Channel: Diagnostic
Task: ExternalAPI
Opcode: Stop

Description

End API Api on transaction TransactionGuid.

Message #

End API %2 on transaction %1

Fields #

Name	Description
`TransactionGuid` GUID
`Api` UInt32
`Code` Int32

Event ID 400: Begin calling into plugin PluginName.

Provider: Microsoft-Windows-Network-Setup
Channel: Diagnostic
Task: Plugincallback
Opcode: Start

Description

Begin calling into plugin PluginName.

Message #

Begin calling into plugin %3

Fields #

Name	Description
`TransactionGuid` GUID
`PluginId` UInt32
`PluginName` UnicodeString
`Api` UInt32

Event ID 401: End calling into plugin

Provider: Microsoft-Windows-Network-Setup
Channel: Diagnostic
Task: Plugincallback
Opcode: Stop

Description

End calling into plugin.

Message #

End calling into plugin

Fields #

Name	Description
`TransactionGuid` GUID
`Output` UInt32
`Code` Int32

Event ID 500: Begin operation OperationType on ObjectType in transaction TransactionGuid: ObjectId on PropertyBufferSize:PropertyBuffer.

Provider: Microsoft-Windows-Network-Setup
Channel: Diagnostic
Task: Operation
Opcode: Start

Description

Begin operation OperationType on ObjectType in transaction TransactionGuid: ObjectId on PropertyBufferSize:PropertyBuffer.

Message #

Begin operation %2 on %3 in transaction %1: %4 on %5:%6

Fields #

Name	Description
`TransactionGuid` GUID
`OperationType` UInt32	Known values `%%1904` New registry value created `%%1905` Existing registry value modified `%%1906` Registry value deleted `%%14674` Value Added `%%14675` Value Deleted `%%14680` Value Added With Expiration Time `%%14681` Value Deleted With Expiration Time `%%14688` Value Auto Deleted With Expiration Time
`ObjectType` UInt32
`ObjectId` GUID
`PropertyBufferSize` UInt16
`PropertyBuffer` Binary

Event ID 501: Operation TransactionGuid ended with code Code.

Provider: Microsoft-Windows-Network-Setup
Channel: Diagnostic
Task: Operation
Opcode: Stop

Description

Operation TransactionGuid ended with code Code.

Message #

Operation %1 ended with code %2

Fields #

Name	Description
`TransactionGuid` GUID
`Code` Int32

Event ID 600: Begin API Api.

Provider: Microsoft-Windows-Network-Setup
Channel: Diagnostic
Task: INetCfgAPI
Opcode: Start

Description

Begin API Api.

Message #

Begin API %1

Fields #

Name	Description
`Api` UInt32

Event ID 601: End API with status code Code.

Provider: Microsoft-Windows-Network-Setup
Channel: Diagnostic
Task: INetCfgAPI
Opcode: Stop

Description

End API with status code Code.

Message #

End API with status code %1

Fields #

Name	Description
`Code` Int32

Event ID 700: Invoking API ComponentId on Notify Object for TransactionGuid.

Provider: Microsoft-Windows-Network-Setup
Channel: Diagnostic
Task: INetCfgNotifyObject
Opcode: Start

Description

Invoking API ComponentId on Notify Object for TransactionGuid.

Message #

Invoking API %2 on Notify Object for %1

Fields #

Name	Description
`TransactionGuid` GUID
`ComponentId` UnicodeString
`Api` UInt32
`Parameter1` UInt32
`Parameter2` UnicodeString

Event ID 701: The Notify Object returned with status: Code.

Provider: Microsoft-Windows-Network-Setup
Channel: Diagnostic
Task: INetCfgNotifyObject
Opcode: Stop

Description

The Notify Object returned with status: Code.

Message #

The Notify Object returned with status: %1

Fields #

Name	Description
`Code` Int32

Event ID 702: An error occurred while invoking the Notify Object.

Provider: Microsoft-Windows-Network-Setup
Channel: Diagnostic
Task: INetCfgNotifyObject
Opcode: Stop

Description

An error occurred while invoking the Notify Object. The call was aborted with status: Code.

Message #

An error occurred while invoking the Notify Object.  The call was aborted with status: %1.

Fields #

Name	Description
`Code` Int32

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 a111f1c2-5923-47c0-9a68-d0bafb577901

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

Observed on:

WS2022-20348.4893, schema read from the registered manifest, binary version 10.0.20348.4767, captured 2026-06-02
Win11-26200.6584, schema read from the registered manifest, binary version 10.0.26100.4484, 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)