Rollback Procedures for True Protection Updates

In rare cases, an update may cause compatibility issues or unexpected behavior. True Protection by Jag includes a rollback mechanism that allows you to revert to a previous version of the signature database or engine.

When to Roll Back

False Positive Spike: If a signature update causes legitimate files to be detected as threats, roll back the signatures until a corrected update is released.
Performance Issues: If an engine update causes noticeable performance degradation on specific hardware.
Compatibility Problems: If an update conflicts with a specific application or system configuration.

Rolling Back Signatures

Step 1: Navigate to Settings > Updates > Update History.
Step 2: Locate the update you want to roll back. Each entry shows the version number, date, and type.
Step 3: Click the Rollback button next to the update.
Step 4: Confirm the rollback. True Protection will revert to the previous signature set.
Step 5: If you want to pause updates temporarily, enable Hold Updates for up to 48 hours.

Rolling Back the Engine

Engine rollbacks require a restart of the True Protection service. Navigate to Settings > Updates > Engine History, select the previous engine version, and click Rollback and Restart. After the rollback, report the issue to support at [email protected] so the team can investigate and release a fix.