For managed Tandem updates, close Tandem before running the MSI. If Tandem is open during the upgrade, the installer can return Exit Code 1618, so add Tandem to conflicting-process detection/closure rules in Intune, ConfigMgr, PSADT, or similar deployment tooling before retrying. The current Windows installer source is the official Tandem downloads page: tandemhealth.ai/product/downloads.

For managed Tandem deployments, install the Microsoft .NET Desktop Runtime 8 prerequisite before the Tandem MSI. The packaging cue is specific to the x86 Desktop Runtime even though the Tandem package is listed as MSI x64, so deployment detection should check the required runtime architecture instead of assuming only x64 prerequisites are needed.

Use Tandem Health’s official downloads page for the application source and Microsoft’s .NET 8 page for the runtime: Tandem Health downloads and .NET 8 downloads.

For managed Tandem updates, close Tandem before running the MSI. If Tandem is open during the upgrade, the installer can return Exit Code 1618, so add Tandem to conflicting-process detection/closure rules in Intune, ConfigMgr, PSADT, or similar deployment tooling before retrying. The current Windows installer source is the official Tandem downloads page: tandemhealth.ai/product/downloads.

For managed Tandem deployments, install the Microsoft .NET Desktop Runtime 8 prerequisite before the Tandem MSI. The packaging cue is specific to the x86 Desktop Runtime even though the Tandem package is listed as MSI x64, so deployment detection should check the required runtime architecture instead of assuming only x64 prerequisites are needed.

Use Tandem Health’s official downloads page for the application source and Microsoft’s .NET 8 page for the runtime: Tandem Health downloads and .NET 8 downloads.