Integrity check warning

BRFZ · ‎08-25-2026

Hello,

I recently upgraded my Splunk instances to version 10.4.x and started seeing integrity check warnings affecting several files.

The check result is:

present_but_shouldnt_be

Has anyone else encountered this after upgrading to Splunk 10.4.x? Is this expected behavior or related to the upgrade process? If anyone knows what should be done in this case.

Thanks for your help!

PickleRick · ‎08-26-2026

It depends on the actual files (and the upgrade process - RPM/deb should remove old files, simply unpacking tgz over old directory won't).

Integrity check warning

administration

upgrade

Join the Splunk Community Slack to learn, troubleshoot, and make connections with fellow Splunk practitioners in real time!

Join Splunk User Groups to connect and learn in-person by region or remotely by topic or industry.

A Four-Part Event Series: State of Observability - Where AI Meets Performance

Persistent Queue at TcpOut — One of Splunk's Most Practical Features

Build resilience for the agentic era: Join us at Splunk Go San Jose

Join the Conversation

Integrity check warning

administration

upgrade

Join the Splunk Community Slack to learn, troubleshoot, and make connections with fellow Splunk practitioners in real time!

Join Splunk User Groups to connect and learn in-person by region or remotely by topic or industry.

A Four-Part Event Series: State of Observability - Where AI Meets Performance

Persistent Queue at TcpOut — One of Splunk's Most Practical Features

Build resilience for the agentic era: Join us at Splunk Go San Jose