Windows - Software - Close-Patch-Reopen TeamViewer/TeamViewer Host

What the TeamViewer patcher does

This Automox Worklet™ updates EXE-installed TeamViewer and TeamViewer Host to the latest available versions on Windows endpoints. The Worklet identifies installed TeamViewer applications by checking standard installation paths (Program Files and Program Files (x86)) and the Automox Software Catalog inventory, retrieves version information for each detected installation, and compares installed versions against the latest releases available in the Automox Software Catalog.

When an update is available, the Worklet executes a three-step process: first, it gracefully stops all running TeamViewer processes to prevent file locks during installation; second, it downloads the latest EXE installer from the Automox cache servers; and third, it performs a silent, unattended installation using standard TeamViewer installer switches before relaunching the application. This close-patch-reopen approach minimizes user disruption by keeping active remote sessions active until the final relaunch.

exe", "C:\Program Files (x86)\TeamViewer\TeamViewer.exe", "C:\Program Files\TeamViewer\TeamViewer_Service.exe".

The Worklet only processes EXE-based TeamViewer installations and does not manage MSI-based deployments. If both the TeamViewer client and TeamViewer Host are detected on the same endpoint, the Worklet updates both products independently.

Why automate TeamViewer updates

TeamViewer regularly releases security patches and feature updates to address vulnerabilities and improve remote support capabilities. Manual patching across dozens or hundreds of endpoints introduces delays that leave systems exposed to known vulnerabilities. Automating TeamViewer updates keeps your endpoint fleet current on security postures without requiring manual intervention on individual machines.

By automating the update process, you eliminate the need for IT teams to manually download, stage, and deploy TeamViewer versions across your environment. The close-patch-reopen approach maintains active remote support sessions during the update, meaning IT technicians can continue providing support without losing their connections. This reduces downtime for both endpoints and IT operations teams while verifying all TeamViewer instances stay current.

Keeping TeamViewer current also supports compliance requirements in regulated industries where software version tracking and patch management are audited. Organizations using TeamViewer for managed IT services, help desk operations, or remote access can demonstrate patching compliance to customers and auditors by maintaining current versions across all endpoints.

How TeamViewer patching works

1. Evaluation phase: The Worklet searches for EXE-installed TeamViewer and TeamViewer Host in standard Windows installation directories (C:\Program Files\TeamViewer and C:\Program Files (x86)\TeamViewer), extracts the file version information from the executable, queries the Automox Software Catalog API to retrieve the latest available version, and compares the installed version against the latest version. If any installed version is older than the latest available version, the Worklet flags the endpoint for remediation and exits with status 2.

2. Remediation phase: For each product requiring an update, the Worklet terminates running TeamViewer and TeamViewer_Service processes to release file locks, downloads the latest EXE installer from the Automox cache API to the local WorkletCache directory, executes the installer with silent mode parameters (/S /allusers) and waits up to 300 seconds for installation to complete, then relaunches the application from the same installation path it used initially. If the installation succeeds with exit code 0, 3010, or 1641 (standard Windows installer success codes including reboot-required), the Worklet continues to the next product or exits successfully with status 0.

TeamViewer patching requirements

• Windows 10, Windows 11, Windows Server 2016, or later

• PowerShell 5.1 or later (included by default in supported Windows versions)

• EXE-based TeamViewer or TeamViewer Host installation (MSI installations are not supported)

• Outbound network access to https://api.automox.com to query the Software Catalog and download installers

• Local Administrator privileges to stop processes, modify Program Files directories, and execute installer executables

• At least 300 MB free disk space in the WorkletCache directory for temporary installer storage

Expected state after TeamViewer patching

After successful remediation, TeamViewer and TeamViewer Host will be updated to the latest available versions from the Automox Software Catalog. Both applications will automatically relaunch and be ready for use. To verify the update on an endpoint, check the TeamViewer version information in the application's settings or help menu (typically found in the About dialog), and confirm it matches the version number shown in the Automox console for that endpoint after the Worklet completes.

If the endpoint has active remote support sessions at the time the Worklet runs, the close-patch-reopen process will gracefully terminate existing connections during the installation phase, then reconnect after the application relaunches. IT technicians using TeamViewer for remote support should be aware that their active sessions will be interrupted when the Worklet executes remediation. For endpoints with critical active sessions, consider scheduling patches during maintenance windows or using RunNow within the Automox console to control the exact timing of the update.

How to validate close-patch-reopen teamviewer/teamviewer host changes

1. Run this Worklet on a pilot Windows endpoint and review evaluation output for close-patch-reopen teamviewer/teamviewer host.

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 Get-ExeVersion, Test-Path, Where-Object.

4. Validate remediation effects from script operations such as Log-Info, Write-Output, Log-Err, then rerun evaluation for compliance.