Configuration – ASU

ASU (Automatos Software Uninstaller) is a tool developed by Automatos to help with standardized and silent software removal in corporate environments.

It is designed to:

• Remove installed programs using the uninstall methods recommended by the vendors themselves.
• Be used in a centralized way, through a remote repository accessed by devices that have the Automatos agent installed.

ASU is available for:

• Microsoft Windows 10 or later

It is intended for corporate environments where you want to:

• Standardize software removal.

Download the agent and, during the installation, make sure you select “YES” for the option “Software distribution modules?”

After the agent is installed, the “Automatos Software Uninstaller” (ASU) module will be added automatically.

By default, ASU is installed in:

C:\Program Files (x86)\Automatos\Software Uninstaller

The location of the remote blacklist, where the configuration files must be stored, is defined in the Windows Registry:

HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Automatos\ASU
Value: RemoteBlacklistPath

Set this value to the path of your centralized blacklist repository (for example, a shared or replicated folder that all agents can access).

Download the configuration files HERE and place them in your configured RemoteBlacklistPath.

The ASU uses three main files:
WHITELST.ini, BLACKLST.ini, Engine.ini

The BLACKLST.ini file must be configured using the exact Display Name of the software, exactly as shown in Programs and Features / Installed apps in Windows.

⚠️ Note: The software you want to uninstall must have uninstall parameters defined either in UninstallString or QuietUninstallString.

ASU checks the following registry keys for installed applications:

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Microsoft\Windows\CurrentVersion\Uninstall

If the application is listed there and its DisplayName matches an entry in BLACKLST.ini, ASU will attempt to uninstall it using the available command line.

The Engine.ini file is responsible for defining which uninstall method should be used.
It identifies the uninstaller executable and executes the correct silent parameter for it.

For example, in the snippet below, there is already an uninstall “engine” configured for:

uninstall.exe /S

This means that whenever ASU detects uninstall.exe as the uninstaller, it will try to run it with /S silently.

🔧 Note:
If the software you want to uninstall is not mapped in Engine.ini, simply add a new line with the uninstaller executable and the appropriate parameters.

Example:

MyUninstaller.exe = /silent /norestart

The WHITELST.ini file defines exception hosts that must not be affected by software removals.

[HOST001 @ programs]
NOTEPAD++ (64-BIT X64)

[HOST002 @ programs]
7-Zip 25.01 (x64)

Any device whose hostname is listed in WHITELST.ini will be ignored by ASU, even if it has software present in BLACKLST.ini.

• The software “Notepad++ (64-bit x64)” will not be uninstalled from HOST001.
• The software “7-Zip 25.01 (x64)” will not be uninstalled from HOST002.

ASU executes its routines every time a user logs on or logs off.

For each device:

If the software:

• is present on the machine,
• has uninstall parameters defined in UninstallString or QuietUninstallString, and
• the hostname is not listed in WHITELST.ini,

then ASU will silently remove the software, using the method defined in Engine.ini.

ASU checks the installed applications in the registry paths mentioned above.

It compares the installed DisplayName with the entries in BLACKLST.ini.

Because the ASU runs automatically on devices that read the RemoteBlacklistPath, any software added to the blacklist will be silently uninstalled on all computers that receive this configuration – except those explicitly listed in WHITELST.ini.
For this reason, some precautions are essential:

• Make sure the Display Name added to BLACKLST.ini is exactly the same as shown in:
  • Control Panel → Programs and Features, or
  • Settings → Apps → Installed apps.
• Avoid generic or ambiguous names that might match unwanted software.

• Before adding a software to the global blacklist, ask:
  • “Can this be removed from all machines in this environment?”
• Critical or shared tools (VPN clients, security agents, backup tools, office suites, line-of-business apps) must be evaluated carefully.

• Before rolling out to the entire environment, consider:
  • Creating a pilot group (a small OU, group of machines, or lab environment).
  • Applying the new blacklist entries only to that group initially (for example, using a separate RemoteBlacklistPath).
• Validate:
  • If the uninstall works as expected.
  • If there are no side effects (dependencies, integrations, services that break, etc.).

• Verify that the software has valid parameters in:
  • UninstallString or
  • QuietUninstallString
• Confirm that the uninstaller executable (e.g., uninstall.exe, msiexec.exe, unins000.exe, etc.) is properly mapped in Engine.ini with the correct silent parameters.

• Before activating a new blacklist entry, identify:
  • Servers.
  • VIP or critical users.
  • Special-purpose machines (monitoring, kiosks, specific departments).
• Add their hostnames to WHITELST.ini in advance if they must keep that software installed.

• Inform:
  • IT support / help desk.
  • Application owners.
  • Security / governance, if applicable.
• Document:
  • Which software will be removed.
  • From which groups or environments.
  • From which date the rule will be active.

• Maintain a simple log or change history with:
  • Date of change.
  • Software added/removed to/from BLACKLST.ini.
  • Reason for the change.
  • Who approved / requested it.

• Tools like “Client”, “Agent”, “Service”, “Updater”, etc., can exist in many vendors’ products.
• Prefer using:
  • The full name.
  • Optionally, additional checks (version, vendor) in future evolutions of the process or tooling.

---

If you need any help configuring ASU or building your blacklist, please contact our support team.