Replace a baseline only after deciding that the current included files should become the new trusted state. Replacing it accepts the whole current snapshot, not just one selected finding.

Review the changes first

1. Open PD Modules → Guard → File Integrity with Pro active.
2. Check the existing baseline time and run Scan now if a current comparison is needed.
3. Review the added, changed and removed groups against the update or customisation you intended.
4. Preserve the relevant result in your normal change record before accepting a new state.

An expected update can change many files. It does not automatically explain an unrelated change elsewhere. Do not trust the entire current installation simply because some filenames match an update you recognise.

Accept the reviewed state

Choose Set baseline, read the confirmation and proceed only when the whole intended comparison scope is acceptable. The current files replace the earlier fingerprints. The previous saved comparison is cleared because it referred to the earlier baseline.

The action does not undo file changes, restore removed files, remove malware or keep the old baseline as a selectable archive. A later No baseline yet, zero count or save error needs investigation; do not assume an interrupted replacement retained a complete previous baseline.

Verify the replacement

Check the new baseline time and file count, including any cap warning from the action. Run a subsequent comparison when appropriate and inspect its completeness. A quiet result immediately after accepting the same files is not independent evidence that the files are safe.

Scheduled integrity alert state is separate. Replacing a baseline is not proof that a notification was delivered or that every later change will produce a fresh alert. Keep backups and investigation evidence outside this fingerprint record.

See the PD Guard WHMCS guide for related tasks, or explore PD Guard.