There are two ways to whitelist SuperOps in ESET:

Step 1: Go to the ESET PROTECT dashboard.

Step 2: Select Policies.

Step 3: Add a new policy or edit the existing policy.

Step 4 : Navigate to Settings ➝ Protections

Step 5 : Select any option between Balanced, Cautious, or Off under POTENTIALLY UNSAFE APPLICATIONS. Do not select Aggressive. Refer to this document to understand the difference between these options here: https://help.eset.com/eea/9/en-US/idh_config_scanner.html

Step 6: You can select any one of the below options, to save the policy.

🔘 : All settings in this panel won't be set by this policy. They will be editable (unlocked) on the client.

⚫ : All settings in this panel will be set by this policy. They will be locked (not editable) on the client.

⚡ : All settings in this panel will be forced by this policy. They will be locked (not editable) on

the client and won't be overwritten by other policies respecting the policy hierarchy.

Step 7 : Click on CONTINUE and hit ASSIGN.

Step 8: Select the targets to apply the policy.

Step 9: Also, select the check boxes of target name and click OK.

Step 10: Check whether the selected targets are displayed and click CONTINUE.

Step 11: Click FINISH.

Step 1: Go to the ESET PROTECT dashboard.

Step 2 : Select Policies.

Step 3: Create a new policy or edit an existing policy.

Step 4: Select Settings.

Step 5: Navigate to DETECTION ENGINE ➝ EXCLUSIONS. Click on the Edit option in Performance exclusions.

Step 6 : Click on Add to add a new folder path.

Step 7: Add your SuperOps folder path, including its bin folder and hit Save. A sample folder path is given in the below image. (C:\Program Files\superopsrmm\bin\*)

Step 8: Click Save.

You can select any one of the below options, to save the policy.

🔘 : All settings in this panel won't be set by this policy. They will be editable (unlocked) on the client.

⚫ : All settings in this panel will be set by this policy. They will be locked (not editable) on the client.

⚡ : All settings in this panel will be forced by this policy. They will be locked (not editable) on the client and won't be overwritten by other policies respecting the policy hierarchy.

And click CONTINUE.

Step 9: Click on Assign

Step 10: Select the targets to apply the policy.

Step 11: Also, select the check boxes of the target names and click OK.

Step 12 : Check whether the selected targets are displayed and click CONTINUE.

Step 13 : Select FINISH.

Step 1: Select More Options.

Step 2: Select Quarantine.

Step 3: Select the SuperOps detection (WinGo/SuperOps.Ai)

Step 4 : Click on Restore and select Restore and Exclude.

Step 5 : Confirm RESTORE AND EXCLUDE.

Step 6 : It might take 1-2 minutes for SuperOps to be restored.

Yes, SuperOps will be restored to it's original state and will start working as usual. Please make sure to start the SuperOps service after it is restored.