Splunk UF not ingesting previous Winevent Security logs

Available Languages

Updated:September 29, 2026
Document ID:SPLK046156

Bias-Free Language

The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.

Applicability

Splunk Enterprise

Description

User wants to ingest old data from Windows channels, this is an example of the inputs.conf:

[WinEventLog://Security]
disabled = 0
index = windows
current_only = 0
whitelist = EventCode= %^(1102|4720|4726)$%

Investigation

To follow up on the Splunk UF for Windows, reset the checkpoint file that tracks the Event logs' position by removing the corresponding XML files in $SPLUNK_HOME\var\lib\splunk\modinputs\wineventlogs.
 


Resolution

Steps 1: Stop Splunkd

Step 2 : navigate on the Splunk UF to $SPLUNK_HOME\var\lib\splunk\modinputs\wineventlogs

Step 3: Find an XML file for each channel such as Security, Applications, System, etc.

Step 4: Take backup of those files and then remove them.

Step 5 : Restart splunkd 

$SPLUNK_HOME/bin/splunk restart


Once restarted, Splunkd should re-index all of the monitored Windows events. It will also cause duplication of events if they were indexed previously.
 


Splunk Community:
How do I trigger the re-indexing of events from a locally collected Windows Event Log channel?
 

Revision History

Revision Publish Date Comments
1.0
29-Sep-2026
Initial Release

Was this Document Helpful?

FeedbackFeedback

Contact Cisco

This Document Applies to These Products