P4V

For managed Helix Visual Client P4V updates, close the P4V desktop client before invoking the Windows installer. The EXE x64 package can return Exit Code 1 when the app remains open during update, so Intune, ConfigMgr, RMM, or PSADT packages should include a P4V-specific user prompt or pre-close step for p4v.exe rather than retrying the same installer in place.

Also stage the current Microsoft Visual C++ Redistributable before deploying the P4V EXE or MSI. Managed-deployment prerequisite data for P4V maps both EXE-x64 and MSI-x64 packages to the x64 Visual C++ v14 runtime; missing runtimes can make first installs or repairs look like installer failures instead of a prerequisite gap.

Use Perforce’s official P4V download page as the source for current installers, and Microsoft’s supported Visual C++ Redistributable page as the runtime source.

For Helix Visual Client P4V EXE/MSI deployments, stage Microsoft Visual C++ v14 Redistributable (x64) before installing or updating P4V. Treat the runtime as a prerequisite in deployment targeting/detection so clean images do not fail before P4V setup completes.

Official source: P4V downloads/documentation. Runtime source: Microsoft runtime downloads.