Splunk Add-on for Microsoft Windows v8.8.0 is unable to ingest performance metrics data for several Windows (UF v9.0.1) machines into Splunk

Available Languages

Updated:September 29, 2026
Document ID:SPLK046620

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 Cloud Splunk Enterprise Splunk Universal Forwarder v9.0.1 Splunk Add-on for Microsoft Windows v8.8.0

Description

There are several windows Universal Forwarders which are unable to send performance data into Splunk; whereas, the other Universal Forwarders are able to send performance data successfully using Splunk Add-on for Microsoft Windows v8.8.0.


Investigation

During investigation, there were no such error logs observed in the Splunk Add-on for Microsoft Windows input logs or in Splunk internal logs (_internal index). The failure to generate logs on the Windows host could be due to disabled or corrupted Windows counters.


Resolution

If the counters are enabled; however, the metrics data is still not present, it is recommended to try rebuilding the counters by using the below steps:

Below are the steps to reload the performance counters:

  1. Launch Command Prompt as Administrator (right click Runs As Administrator).
  2. Go to directory Windows\System32
    • $ cd Windows\System32
  3. To rebuild your resource counters run the following command (to restore performance counter registry strings and information by using a file name):
    • $ lodctr /r
  4. Restart the Splunk-forwarder service and it should resolve the issue.

lodctr reference document can be viewed by clicking here.

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