PuTTY

For PuTTY update targeting, account for the historic installer-type change from EXE to MSI after the 0.70-era releases. Devices with an older EXE-based PuTTY install may need a base MSI deployment or cleanup step before MSI-based update logic will detect and service them correctly.

Use the official PuTTY site when validating downloads: PuTTY downloads.

For managed PuTTY updates, account for the installer-family change from the old EXE packages to MSI packages after the 0.70-era releases. Standardize on the official MSI for current Windows deployments and treat older EXE-installed endpoints as a migration case instead of assuming MSI update applicability will cover them. Source: official PuTTY source.

For managed PuTTY deployments, standardize on the official Windows MSI package for current installs and updates. Legacy PuTTY installs from the pre-0.70 EXE installer line are a separate case: MSI-based update detection/applicability should not be expected to upgrade those older EXE installs in place. Remove or replace legacy EXE-era installs first, then manage future versions with the MSI package.

Example quiet MSI pattern: msiexec /i putty-64bit-<version>-installer.msi /qn /norestart /L*v "%WINDIR%\Temp\PuTTY-install.log". If you use a custom install directory, keep detection tied to the MSI-installed PuTTY version/ProductCode rather than an older EXE uninstall entry.

Official source for current Windows MSI packages: PuTTY latest release downloads.