Uninstall All Apps Under Specific Version

What the version-specific application remover does

This Automox Worklet™ identifies and removes all instances of a specified application that fall below a defined version threshold on your endpoints. The Worklet scans multiple registry hives including 64-bit, 32-bit, and per-user installations, enabling comprehensive detection across diverse installation scenarios.

The Worklet supports both MSI-based and EXE-based installers with configurable uninstall switches. During evaluation, it performs a version comparison against your specified threshold and flags non-compliant installations for removal.

This approach is particularly useful when an application permits multiple versions to coexist on a single endpoint, which is common with software frameworks and development tools.

Why remove outdated application versions

Outdated software versions often contain known security vulnerabilities and compatibility gaps that increase your organization's risk profile. By establishing and enforcing version thresholds, you eliminate legacy versions that may lack critical patches for exploits.

Older application versions also cause operational friction. They may lack features required by other business tools, exhibit stability issues, or deliver suboptimal performance. Removing outdated versions keeps your endpoints run stable, well-supported software.

When IT support staff engage with users experiencing issues, they can confidently assume recent versions are installed. This eliminates a troubleshooting variable and simplifies support interactions. Your team spends less time investigating version-related problems and more time addressing genuine issues.

How version-based application remediation works

1. Evaluation phase: The Worklet queries the Windows registry across 64-bit and 32-bit hives plus per-user profiles. It compares the DisplayVersion of each matching application against your specified minimum version using semantic version comparison. Any installation with a version less than the threshold is flagged for remediation.

2. Remediation phase: The Worklet executes the uninstall command for each flagged installation. For MSI-based installers, it invokes msiexec.exe with the product key and silent options. For EXE-based installers, it uses either stored uninstall switches from the registry or custom switches you provide, executing each removal with logging to the Windows temp directory.

Application version enforcement requirements

• Windows 7 or later

• PowerShell 2.0 or later

• $appName: the exact or partial application name as it appears in Programs and Features (example: 'Python', 'Adobe Acrobat Reader')

• $appVersion: the minimum version threshold using standard semantic versioning (example: '3.9.5', '23.003.20244')

• $uninstallSwitchEXE: (optional) silent uninstall switches for EXE-based installers if registry detection fails (example: '/uninstall /quiet')

• Local administrator privileges on the endpoint

Expected version compliance after removal

After the Worklet completes remediation, only installations meeting or exceeding your specified version threshold remain on the endpoint. All older versions of the targeted application are completely uninstalled, including user-level installations. The Worklet generates logs in the Windows temp directory documenting which versions were removed and the success or failure of each uninstall operation.

You can verify compliance by checking Programs and Features on the endpoint or by reviewing the Automox console activity log for the Worklet execution. Subsequent Worklet runs will find no non-compliant versions and report full compliance.