--- title: "Manage updaters in a managed environment" slug: "manage-updaters-in-a-managed-environment-3" tags: ["Product Usage", "ACC 8.3.x"] updated: 2026-09-09T18:02:39Z published: 2026-09-09T18:02:39Z canonical: "docs.trellix.com/manage-updaters-in-a-managed-environment-3" --- > ## Documentation Index > Fetch the complete documentation index at: https://docs.trellix.com/llms.txt > Use this file to discover all available pages before exploring further. # Manage updaters in a managed environment If a program is configured as an updater, it can install new software and update existing software. You can add, edit, or remove updaters. 1. Manage updaters in rule groups. 1. On the ePO - On-prem console, select **Menu** → **Configuration** → **Solidcore Rules**. 2. Locate the rule group and under **Actions**, click **View**. 3. On the **Updater Processes** tab, you can **Add**, **Edit**, or **Remove** an updater. 2. Manage updaters in policies. 1. On the ePO - On-prem console, select **Menu** → **Policy** → **Policy Catalog**. 2. On the **Policy Catalog** page, select the product and category from the list. 3. Click the selected policy. 3. Complete the addition of an updater to a rule group or policy. 1. On the **Updater Processes** tab, click **Add**. 2. Specify whether to add the updater based on the file name, SHA-1, or SHA-256. If you add the updater by name, the updater is not authorized automatically. The file must be added to the allow list. 3. Enter the location of the file (when adding by name), or the SHA-1 or SHA-256 value of the executable file. 4. Specify an identification updater label for the program. 5. When adding an updater by name, specify conditions that the file must meet to run as an updater. - Select condition **None** to allow the file to run as an updater without any conditions. - Select condition **Library** to allow the file to run as updater only when it has loaded the specified library. For example, when configuring `iexplore.exe` as an updater to allow Windows Updates using Internet Explorer, specify `wuweb.dll` as the library. This makes sure that the `iexplore.exe` program has updater rights only until the web control library (`wuweb.dll`) is loaded. - Select condition **Parent** to allow the file to run as an updater only if it is started by the specified parent. For example, when configuring `updater.exe` as an updater to allow changes to Mozilla Firefox, specify `firefox.exe` as the parent. Although `updater.exe` is a generic name that can be part of any installed application, using the parent makes sure that only the correct program is allowed to run as an updater. 6. When adding an updater by name, indicate whether to disable inheritance for the updater. For example, if Process A (that is set as an updater) starts Process B, disabling inheritance for Process A makes sure that Process B does not become an updater. 7. When adding an updater by name, indicate whether to suppress events generated for the actions performed by the updater. Typically, when an updater changes a protected file, a File Modified event is generated for the file. If you select this option, no events are generated for changes made by the updater. 8. Click **OK**.