/
Windows Universal Installer

Windows Universal Installer

From Vivi App version 3.12.0 we've consolidated our Windows installers into a single universal installer that supports both Intel/AMD (x64) and ARM64 hardware. You no longer need to know which architecture a machine is running before downloading. The installer detects it at install time and activates the matching build.

This article is aimed at IT admins deploying Vivi across a fleet. End users can run the .exe and follow the prompts as before.

What's Changed

Prior to version 3.12.0: Separate installers for x64 and ARM64 Windows machines.

Version 3.12.0 and later: One universal installer that runs on either architecture.

Internally, the universal installer carries both the x86 and ARM64 application payloads. At install time, only the payload matching the host CPU is written to disk. The Windows upgrade code is unchanged from the previous separate installers, so the universal installer upgrades existing Vivi installs in place, no need to uninstall first.

Install Path

The Vivi application install path has now changed with the Windows Universal Installer

Prior to 3.12.0 the install path was: C:\Program Files\Vivi Corporation\Vivi\Vivi.exe

In Version 3.12.0 and later the path will be one of the following depending on the system architecture:

  • x86: C:\Program Files\Vivi Corporation\Vivi\x86\Vivi.exe

  • ARM64: C:\Program Files\Vivi Corporation\Vivi\arm64\Vivi.exe

Which file to use

We provide three installer files:

  • ViviSetup.exe - bootstrapper. Use this for interactive installs and for any deployment tooling that handles EXE installers. This is the recommended default.

  • ViviSetup64.msi - 64-bit-context MSI. Use this for mass deployment via Group Policy, Intune (LOB app), or SCCM on 64-bit Windows. This is what most admins want.

  • ViviSetup.msi - 32-bit-context MSI. Only required when your management tooling specifically demands a 32-bit MSI.

All three install the same Vivi application and end up at the same install location; they differ only in the package format your tooling needs.

Installation

Get the latest universal installer from https://www.vivi.io/downloads/

Prerequisites

Vivi requires the Microsoft Visual C++ Redistributable for Visual Studio 2017–2026, matching the target architecture (x86, x64, or ARM64).

How the prerequisite is handled depends on which artifact you deploy:

  • ViviSetup.exe (bootstrapper) - bundles the redistributables and runs Microsoft's native VC++ installer at install time. On machines that don't already have the minimum version, the Microsoft VC++ installer's own dialog appears and must be accepted before the Vivi install continues.

Screenshot 2026-06-15 132159.png
Native Microsoft VC++ installer Dialog

  • ViviSetup64.msi / ViviSetup.msi - does not install the redistributable. You are responsible for ensuring the matching VC++ Redistributable is already present on the target machine before the MSI runs. Stage it as a separate package in your deployment tool so it installs first. Download official installers from https://learn.microsoft.com/en-us/cpp/windows/latest-supported-vc-redist

Optional driver components

Screenshot 2026-06-15 132101.png
Vivi Client Installer Dialog

During an interactive install, the Installation Folder screen presents up to three driver checkboxes. Their visibility and default state depend on the target hardware:

  • Install Extended Display Driver - always shown, checked by default. Enables Vivi's wireless display extension, where a presenter's screen appears as an additional monitor in Windows.

  • Install Vivi Audio Driver - shown on 64-bit Windows 10 build 19041 (version 2004 / May 2020 Update) and later, and on Windows 11. Checked by default where shown. Provides system audio capture so screen sharing includes sound.

  • Install USB Passthrough Driver - legacy component, opt-in only. Shown on x86 and x64 systems but unchecked by default. Tick the box during interactive install only if you specifically need it. Not shown on ARM64. This driver supports USB device sharing in older Vivi deployments and will be deprecated in a future release. Leave unchecked for new deployments unless you have an existing use case that depends on it.

Silent / unattended installation

We have Three MSI properties map to the driver checkboxes:

  • INSTALL_DISPLAY_DRIVER - defaults to enabled

  • INSTALL_AUDIO_DRIVER - defaults to enabled

  • INSTALL_USB_DRIVER - defaults to disabled (this is a legacy feature and will be deprecated)

To opt in to the legacy USB Passthrough Driver in a silent installation:

msiexec /i ViviSetup64.msi /qn /norestart INSTALL_USB_DRIVER=1

To skip a driver that's on by default, pass an empty value. For example, to omit the audio driver:

msiexec /i ViviSetup64.msi /qn /norestart INSTALL_AUDIO_DRIVER=""

Properties for drivers that aren't applicable to the target hardware are ignored.

Verifying the installation

  1. Add or Remove Programs will show a single Vivi entry regardless of architecture.

  2. The installation location (C:\Program Files\Vivi Corporation\Vivi\ by default) will contain either an x86 or an arm64 subfolder. Only the matching architecture is installed.

  3. Launching Vivi and confirming the app opens normally is the most reliable verification.