Windows - Software - Uninstall Artweaver

What the Artweaver uninstaller does

This Automox Worklet™ detects and removes Artweaver from Windows endpoints. The Worklet performs a comprehensive scan of the Windows registry to identify both 32-bit and 64-bit installations of Artweaver, then automatically executes the application's uninstall routine.

The Worklet uses the registry uninstall strings registered by the application to remove Artweaver silently without requiring user interaction. It supports both MSI-based uninstalls and traditional executable uninstallers, accommodating different Artweaver installation methods.

The uninstall process runs with native 64-bit PowerShell on 64-bit operating systems, verifying proper detection and removal of both architecture variants. Exit codes validate success, recognizing standard Windows uninstall completion codes (0, 1641, 3010).

Why remove Artweaver from your endpoints

Software lifecycle management requires systematic control over applications running on your endpoints. Uninstalling unused or deprecated software reduces endpoint attack surface, frees system resources, and maintains cleaner endpoint configurations across your organization.

Automated uninstallation through Automox eliminates the need for manual removal on individual endpoints. This approach maintains consistent application removal across your entire fleet, reduces support tickets from users attempting manual uninstallation, and maintains accurate software inventory records.

When you standardize application deployment and removal through Worklets, you gain auditable records of software changes, faster completion times, and the ability to target specific endpoint groups for removal.

How Artweaver removal works

1. Evaluation phase: The Worklet queries the Windows registry at HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall and HKLM:\SOFTWARE\Wow6432Node\Microsoft\Windows\CurrentVersion\Uninstall to detect any installed versions of Artweaver. It checks both 64-bit and 32-bit registry locations on 64-bit systems, and 32-bit registry only on 32-bit systems. If Artweaver is found in any registry location, the endpoint is flagged for remediation.

2. Remediation phase: The Worklet retrieves the UninstallString property for each Artweaver installation found and executes it with appropriate parameters. For MSI-based installations, it runs msiexec.exe /x with the product GUID; for executable installers, it runs the uninstall executable with /VERYSILENT and /NORESTART flags. The Worklet waits for the uninstall process to complete and validates the exit code against known successful codes (0, 1641, 3010). Failed uninstalls are reported separately from successful removals.

Artweaver removal requirements

• Windows 7 or later (Server and Workstation editions supported)

• Local Administrator privileges required to modify registry and execute uninstallers

• Artweaver must be installed through standard Windows installation method (registered in Add/Remove Programs)

• PowerShell 2.0 or later (included in all supported Windows versions)

• No open Artweaver processes during uninstallation (the Worklet runs silently, but background processes may prevent removal)

Expected state after Artweaver removal

After successful remediation, Artweaver is completely removed from the endpoint. The application no longer appears in Add/Remove Programs, registry entries are deleted by the uninstaller, and the Worklet exits with code 0 to indicate successful completion. On subsequent evaluation runs, the Worklet detects no Artweaver installation and exits without requiring further remediation.

If uninstallation fails (for example, due to locked files or insufficient permissions), the Worklet reports the specific error in the Activity Log and does not remove the application from remediation tracking. In this case, investigate open Artweaver processes or permissions issues before retrying the Worklet.

How to validate uninstall artweaver changes

1. Run this Worklet on a pilot Windows endpoint and review evaluation output for uninstall artweaver.

2. Confirm Automox activity logs show successful completion and exit code 0.

3. Verify endpoint state using checks aligned to evaluation script logic, such as Write-Output, Get-ChildItem, Get-ItemProperty.

4. Validate remediation effects from script operations such as Get-ChildItem, Get-ItemProperty, Where-Object, then rerun evaluation for compliance.