Microsoft-Windows-Eventlog
41 events across 4 channels
Event ID 20: The event logging service encountered an error ErrorCode while obtaining or processing configuration for channel Path.
#Event ID 21: The event logging service encountered a configuration-related error (res=ErrorCode) for channel ChannelPath.
#Description
The event logging service encountered a configuration-related error (res=ErrorCode) for channel ChannelPath. The error was encountered while processing the ConfigProperty configuration property.
Message #
Fields #
| Name | Description |
|---|---|
ErrorCode UInt32 | |
ChannelPath UnicodeString | |
ConfigProperty UnicodeString |
Event ID 22: The event logging service encountered an error while initializing publishing resources for channel Path.
#Event ID 23: The event logging service encountered an error (res=ErrorCode) while initializing logging resources for channel Path.
#Event ID 25: The event logging service encountered a corrupt log file for channel ChannelPath.
#Event ID 26: The event logging service encountered a log file for channel ChannelPath which is an unsupported version.
#Event ID 27: The event logging service encountered an error (res=ErrorCode) while opening log file for channel ChannelPath.
#Description
The event logging service encountered an error (res=ErrorCode) while opening log file for channel ChannelPath. Trying again using default log file path FailedLogFilePath.
Message #
Fields #
| Name | Description |
|---|---|
ErrorCode UInt32 | |
ChannelPath UnicodeString | |
FailedLogFilePath UnicodeString | |
NewLogFilePath UnicodeString |
Event ID 28: The event logging service encountered an error (res=ErrorCode) while parsing filter for channel ChannelPath.
#Event ID 29: The event logging service encountered a fatal error (res=ErrorCode) when applying settings to the ChannelPath channel.
#Event ID 30: The event logging service encountered an error (InitChannelPublisherEnableFailure.ErrorCode) while enabling publisher InitChannelPublisherEnableFailure.PublisherGuid to channel InitChannelPublisher...
#Description
The event logging service encountered an error (ErrorCode) while enabling publisher PublisherGuid to channel ChannelPath. This does not affect channel operation, but does affect the ability of the publisher to raise events to the channel. One common reason for this error is that the Provider is using ETW Provider Security and has not granted enable permissions to the Event Log service identity.
Message #
Fields #
| Name | Description |
|---|---|
ErrorCode UInt32 | |
ChannelPath UnicodeString | |
PublisherGuid GUID |
Example Event #
{
"system": {
"provider": "Microsoft-Windows-Eventlog",
"guid": "FC65DDD8-D6EF-4962-83D5-6E5CFE9CE148",
"event_source_name": "",
"event_id": 30,
"version": 0,
"level": 2,
"task": 100,
"opcode": 0,
"keywords": 9223372036854906880,
"time_created": "2026-03-13T19:59:15.259008+00:00",
"event_record_id": 11634,
"correlation": {},
"execution": {
"process_id": 1844,
"thread_id": 8176
},
"channel": "System",
"computer": "LAB-DC01.ludus.domain",
"security": {
"user_id": "S-1-5-19"
}
},
"user_data": {
"InitChannelPublisherEnableFailure": {
"ErrorCode": 5,
"ChannelPath": "Microsoft-Windows-WinINet-Capture/Analytic",
"PublisherGuid": "A70FF94F-570B-4979-BA5C-E59C9FEAB61B"
}
},
"message": ""
}
Event ID 31: The event logging service encountered an error (res=ErrorCode) while opening configuration for primary channel ChannelPath.
#Description
The event logging service encountered an error (res=ErrorCode) while opening configuration for primary channel ChannelPath. Trying again using default configuration. This problem usually occurs if registry has been corrupted or explicitly misconfigured.
Message #
Fields #
| Name | Description |
|---|---|
ErrorCode UInt32 | |
ChannelPath UnicodeString |
Event ID 40: The event logging service encountered an error when attempting to apply one or more policy settings.
#Event ID 100: The event logging service encountered an error while processing an incoming event published from PubID.
#Event ID 102: The event logging service encountered an error while processing an incoming event from publisher PublisherName and trying to process the metadata for it.
#Event ID 103: Events have been dropped by the transport.
#Event ID 104: The LogFileCleared.Channel log file was cleared.
#Description
The LogFileCleared.Channel log file was cleared.
Message #
Fields #
| Name | Description | Rules |
|---|---|---|
LogFileCleared.SubjectUserName | ||
LogFileCleared.SubjectDomainName | ||
LogFileCleared.Channel | ||
LogFileCleared.BackupPath | ||
SubjectUserName | ||
SubjectDomainName | ||
Channel | 12 detection rules | |
BackupPath | ||
ClientProcessId | ||
ClientProcessStartKey |
Example Event #
{
"system": {
"provider": "Microsoft-Windows-Eventlog",
"guid": "{FC65DDD8-D6EF-4962-83D5-6E5CFE9CE148}",
"event_source_name": "",
"event_id": 104,
"version": 0,
"level": 4,
"task": 104,
"opcode": 0,
"keywords": -9223372036854775808,
"time_created": "2026-05-28T00:50:57.4445174+00:00",
"event_record_id": 6146,
"correlation": {},
"execution": {
"process_id": 1616,
"thread_id": 3308
},
"channel": "System",
"computer": "telemetry-DC-a.cell-a.ludus.domain",
"security": {
"user_id": "S-1-5-21-1006758700-2167138679-1475694448-1000"
}
},
"user_data": {
"LogFileCleared": {
"SubjectUserName": "localuser",
"SubjectDomainName": "cell-a",
"Channel": "Windows PowerShell",
"BackupPath": ""
}
},
"message": "The Windows PowerShell log file was cleared."
}
Detection Patterns #
Event Log Cleared
Common Indicators #
Field/value combinations most frequently checked by detection rules targeting this event, derived from cross-vendor predicate analysis.
| Field | Kind | Value | Rules | Vendors |
|---|---|---|---|---|
Provider_Name | eq | Microsoft-Windows-Eventlog | 2 rules | sigma |
Community Notes #
This will show System, Application, and other non-Security logs being cleared. Review the event to identify which one.
Detection Rules #
View all rules referencing this event →Sigma # view in coverage
Event ID 105: Event log automatic backup.
#Description
Event log automatic backup.
Message #
Fields #
| Name | Description |
|---|---|
Channel | |
BackupPath |
Example Event #
{
"system": {
"provider": "Microsoft-Windows-Eventlog",
"guid": "{fc65ddd8-d6ef-4962-83d5-6e5cfe9ce148}",
"event_source_name": "",
"event_id": 105,
"version": 0,
"level": 4,
"task": 105,
"opcode": 0,
"keywords": 9223372036854775808,
"time_created": "2012-03-26T05:50:08.470644Z",
"event_record_id": 13049,
"correlation": {},
"execution": {
"process_id": 772,
"thread_id": 4256
},
"channel": "System",
"computer": "WKS-WIN764BITB.shieldbase.local",
"security": {
"user_id": ""
}
},
"user_data": {
"AutoBackup": {
"xmlns:auto-ns3": "http://schemas.microsoft.com/win/2004/08/events",
"Channel": "Application",
"BackupPath": "C:\\Windows\\System32\\Winevt\\Logs\\Archive-Application-2012-03-26-05-50-01-755.evtx"
}
}
}
Event ID 106: Corruption was detected in the log for the Channel channel and some data was erased.
#Event ID 107: The event logging service encountered an error ErrorCode while going through publisher configuration.
#Event ID 108: The previous system shutdown was unexpected.
#Event ID 109: The event logging service encountered an error while processing an incoming event from publisher PublisherName and trying to process the metadata for it.
#Description
The event logging service encountered an error while processing an incoming event from publisher PublisherName and trying to process the metadata for it.
Message #
Fields #
| Name | Description |
|---|---|
ErrorCode UInt32 | |
EventID UInt16 | |
PublisherName UnicodeString | |
PublisherGuid GUID | |
ProcessID UInt32 | |
EventName UnicodeString |
Event ID 110: Loading metadata for publisher PublisherName (PublisherGuid) and trying to process the metadata for it.
#Event ID 111: Finished loading metadata for publisher PublisherName (PublisherGuid), with EventMetaDataCount event metadatas processed.
#Event ID 112: Failed to load metadata for publisher PublisherName (PublisherGuid).
#Event ID 200: Channel ChannelName (ChannelType) was enabled (Enabled) programmatically.
#Event ID 201: A push subscription was created for ChannelName.
#Event ID 202: A pull subscription was created for ChannelName.
#Event ID 203: OpenEventLog legacy API was used to open ModuleName.
#Event ID 204: RegisterEventSource legacy API was used to register ModuleName.
#Description
RegisterEventSource legacy API was used to register ModuleName.
Message #
Fields #
| Name | Description |
|---|---|
ModuleNameLen UInt8 | |
ModuleName UnicodeString |
Example Event #
{
"system": {
"provider": "Microsoft-Windows-Eventlog",
"guid": "{fc65ddd8-d6ef-4962-83d5-6e5cfe9ce148}",
"event_source_name": "",
"event_id": "204",
"version": "0",
"level": "5",
"task": "109",
"opcode": "0",
"keywords": 576460752304472064,
"time_created": "2026-03-15T04:33:36.389555800+00:00",
"event_record_id": 0,
"correlation": {
"ActivityID": "{00102311-0000-0000-0000-0000bebcad59}"
},
"execution": {
"process_id": "5820",
"thread_id": "8064"
},
"channel": "Microsoft-Windows-EventLog/Analytic",
"computer": "",
"security": {
"user_id": ""
}
},
"event_data": {
"ModuleNameLen": "10",
"ModuleName": "PowerShell"
},
"message": ""
}
Event ID 205: ReportEvent legacy API was used to write an event to ModuleName.
#Description
ReportEvent legacy API was used to write an event to ModuleName.
Message #
Fields #
| Name | Description |
|---|---|
ModuleNameLen UInt8 | |
ModuleName AnsiString |
Example Event #
{
"system": {
"provider": "Microsoft-Windows-Eventlog",
"guid": "{fc65ddd8-d6ef-4962-83d5-6e5cfe9ce148}",
"event_source_name": "",
"event_id": "205",
"version": "1",
"level": "5",
"task": "109",
"opcode": "0",
"keywords": 576460752304472064,
"time_created": "2026-03-15T04:33:36.390335800+00:00",
"event_record_id": 0,
"correlation": {
"ActivityID": "{00102311-0000-0000-0000-0000bebcad59}"
},
"execution": {
"process_id": "5820",
"thread_id": "8064"
},
"channel": "Microsoft-Windows-EventLog/Analytic",
"computer": "",
"security": {
"user_id": ""
}
},
"event_data": {
"ModuleNameLen": "10",
"ModuleName": "PowerShell"
},
"message": ""
}
Event ID 517: The audit log was cleared (legacy Windows 2000/XP/2003 event; superseded by 1102).
#Description
Legacy security-log clear event from Windows 2000/XP/2003. Superseded by EventID 1102 in Vista+.
Detection Patterns #
Stealth: Clear Windows Event Logs
1 rule
Defense Impairment: Clear Windows Event Logs
1 rule
Common Indicators #
Field/value combinations most frequently checked by detection rules targeting this event, derived from cross-vendor predicate analysis.
| Field | Kind | Value | Rules | Vendors |
|---|---|---|---|---|
Provider_Name | eq | Microsoft-Windows-Eventlog | 1 rule | sigma |
Event ID 1100: The event logging service has shut down.
#Description
The event logging service has shut down.
Message #
Fields #
| Name | Description |
|---|---|
ServiceShutdown |
Example Event #
{
"system": {
"provider": "Microsoft-Windows-Eventlog",
"guid": "{FC65DDD8-D6EF-4962-83D5-6E5CFE9CE148}",
"event_source_name": "",
"event_id": 1100,
"version": 0,
"level": 4,
"task": 103,
"opcode": 0,
"keywords": 4620693217682128896,
"time_created": "2026-06-13T05:22:34.5804660+00:00",
"event_record_id": 2929211,
"correlation": {},
"execution": {
"process_id": 1468,
"thread_id": 7088
},
"channel": "Security",
"computer": "telemetry-DC-c.cell-c.ludus.domain",
"security": {
"user_id": ""
}
},
"user_data": {
"ServiceShutdown": {}
},
"message": "The event logging service has shut down."
}
Detection Rules #
View all rules referencing this event →Splunk # view in coverage
References #
- Microsoft Learn https://learn.microsoft.com/en-us/windows/security/threat-protection/auditing/event-1100
- Ultimate Windows Security https://www.ultimatewindowssecurity.com/securitylog/encyclopedia/event.aspx?eventid=1100
- NSA/CISA - Best Practices for Event Logging https://www.cisa.gov/resources-tools/resources/best-practices-event-logging-and-threat-detection
Event ID 1101: Audit events have been dropped by the transport.
#Description
Audit events have been dropped by the transport. AuditEventsDropped.Reason.
Message #
Fields #
| Name | Description |
|---|---|
Reason UInt8 |
Example Event #
{
"system": {
"provider": "Microsoft-Windows-Eventlog",
"guid": "{fc65ddd8-d6ef-4962-83d5-6e5cfe9ce148}",
"event_source_name": "",
"event_id": 1101,
"version": 0,
"level": 2,
"task": 101,
"opcode": 0,
"keywords": 4620693217682128896,
"time_created": "2026-03-06T19:18:41.161306+00:00",
"event_record_id": 13453892,
"correlation": {},
"execution": {
"process_id": 1788,
"thread_id": 2828
},
"channel": "Security",
"computer": "LAB-DC01.ludus.domain",
"security": {
"user_id": ""
}
},
"user_data": {
"AuditEventsDropped": {
"Reason": 0
}
},
"message": ""
}
References #
- Ultimate Windows Security https://www.ultimatewindowssecurity.com/securitylog/encyclopedia/event.aspx?eventid=1101
Event ID 1102: The audit log was cleared.
#Description
The audit log was cleared.
Message #
Fields #
| Name | Description |
|---|---|
LogFileCleared.SubjectUserSid | |
LogFileCleared.SubjectUserName | |
LogFileCleared.SubjectDomainName | |
LogFileCleared.SubjectLogonId | |
SubjectUserSid | |
SubjectUserName | |
SubjectDomainName | |
SubjectLogonId | |
ClientProcessId | |
ClientProcessStartKey |
Example Event #
{
"system": {
"provider": "Microsoft-Windows-Eventlog",
"guid": "{FC65DDD8-D6EF-4962-83D5-6E5CFE9CE148}",
"event_source_name": "",
"event_id": 1102,
"version": 0,
"level": 4,
"task": 104,
"opcode": 0,
"keywords": 4620693217682128896,
"time_created": "2026-05-28T00:50:56.9132673+00:00",
"event_record_id": 1401962,
"correlation": {},
"execution": {
"process_id": 1616,
"thread_id": 3308
},
"channel": "Security",
"computer": "telemetry-DC-a.cell-a.ludus.domain",
"security": {
"user_id": ""
}
},
"user_data": {
"LogFileCleared": {
"SubjectUserSid": "S-1-5-21-1006758700-2167138679-1475694448-1000",
"SubjectUserName": "localuser",
"SubjectDomainName": "cell-a",
"SubjectLogonId": "0x196099a"
}
},
"message": "The audit log was cleared.\r\nSubject:\r\n\tSecurity ID:\tS-1-5-21-1006758700-2167138679-1475694448-1000\r\n\tAccount Name:\tlocaluser\r\n\tDomain Name:\tcell-a\r\n\tLogon ID:\t0x196099A"
}
Detection Patterns #
Event Log Cleared
Event Logs
3 rules
Defense Impairment: Clear Windows Event Logs
1 rule
Common Indicators #
Field/value combinations most frequently checked by detection rules targeting this event, derived from cross-vendor predicate analysis.
| Field | Kind | Value | Rules | Vendors |
|---|---|---|---|---|
Category | eq | Microsoft-Windows-Eventlog | 2 rules | kusto |
Provider_Name | eq | Microsoft-Windows-Eventlog | 1 rule | sigma |
Detection Rules #
View all rules referencing this event →Kusto # view in coverage
YARA-L # view in coverage
References #
- Microsoft Learn https://learn.microsoft.com/en-us/windows/security/threat-protection/auditing/event-1102
- Ultimate Windows Security https://www.ultimatewindowssecurity.com/securitylog/encyclopedia/event.aspx?eventid=1102
- NSA/CISA - Best Practices for Event Logging https://www.cisa.gov/resources-tools/resources/best-practices-event-logging-and-threat-detection
Event ID 1103: The security log is now PercentFull percent full.
#Event ID 1104: The security log is now full.
#Event ID 1105: Event log automatic backup.
#Event ID 1106: Events have been dropped by the event logging service.
#Event ID 1107: The event logging service encountered an error while processing an incoming event from publisher PublisherName and trying to process the metadata for it.
#Description
The event logging service encountered an error while processing an incoming event from publisher PublisherName and trying to process the metadata for it.
Message #
Fields #
| Name | Description |
|---|---|
ErrorCode UInt32 | |
EventID UInt16 | |
PublisherName UnicodeString | |
PublisherGuid GUID | |
ProcessID UInt32 |
Example Event #
{
"system": {
"provider": "Microsoft-Windows-Eventlog",
"guid": "{fc65ddd8-d6ef-4962-83d5-6e5cfe9ce148}",
"event_source_name": "",
"event_id": 1107,
"version": 0,
"level": 2,
"task": 101,
"opcode": 0,
"keywords": 4620693217682128896,
"time_created": "2016-08-18T16:53:04.313375Z",
"event_record_id": 5538,
"correlation": {},
"execution": {
"process_id": 716,
"thread_id": 1128
},
"channel": "Security",
"computer": "IE10Win7",
"security": {
"user_id": ""
}
},
"user_data": {
"EventPublisherMetaDataFailure": {
"#attributes": {
"xmlns:auto-ns3": "http://schemas.microsoft.com/win/2004/08/events",
"xmlns": "http://manifests.microsoft.com/win/2004/08/windows/eventlog"
},
"Error": {
"#attributes": {
"Code": 15002
}
},
"EventID": 0,
"PublisherName": null,
"PublisherGuid": "54849625-5478-4994-A5BA-3E3B0328C30D",
"ProcessID": 0
}
}
}
References #
- Example event sourced from https://github.com/NextronSystems/evtx-baseline
Event ID 1108: The event logging service encountered an error while processing an incoming event published from EventProcessingFailure.PublisherID.
#Description
The event logging service encountered an error while processing an incoming event published from EventProcessingFailure.PublisherID.
Message #
Fields #
| Name | Description |
|---|---|
ErrorCode UInt32 | |
EventID UInt16 | |
PubID UnicodeString |
Example Event #
{
"system": {
"provider": "Microsoft-Windows-Eventlog",
"guid": "{fc65ddd8-d6ef-4962-83d5-6e5cfe9ce148}",
"event_source_name": "",
"event_id": 1108,
"version": 0,
"level": 2,
"task": 101,
"opcode": 0,
"keywords": 4620693217682128896,
"time_created": "2026-03-12T03:08:47.632904+00:00",
"event_record_id": 2761579,
"correlation": {},
"execution": {
"process_id": 1916,
"thread_id": 2348
},
"channel": "Security",
"computer": "LAB-WIN11",
"security": {
"user_id": ""
}
},
"user_data": {
"EventProcessingFailure": {
"ErrorCode": 15003,
"EventID": 4688,
"PublisherID": "Microsoft-Windows-Security-Auditing"
}
},
"message": ""
}
References #
Event ID 6000: The Channel log file is full.
#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 {FC65DDD8-D6EF-4962-83D5-6E5CFE9CE148}
Defined in wevtsvc.dll, which carries the event manifest.
Observed on:
- WS2022-20348.4893, sample captured from a live trace, binary version 10.0.20348.1, captured 2026-06-02
- 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.4946, captured 2026-06-02