Showing results for 
Search instead for 
Did you mean: 

Zoom not auto updating on MSI installs


We have installed Zoom with the MSI installers and set them to automatically update.

Zoom recently pushed out an update that did not auto install and it required admin privileges to install the update so IT had to be called and install the update on a multitude of PCs, laptops, and other devices.

Why would this update not auto-install and require admin privileges?



The update likely required admin privileges because it involved system-level changes, such as updating core components or modifying settings that regular users don't have permission to alter. Zoom's automatic updates might not always cover updates that necessitate administrative access to ensure security and stability. In such cases, manual intervention is required to execute the update with the necessary permissions.


BFB Security has also seen this issue and had to have a customer move to IBM BigFix. Most smaller companies won't implement BigFix and other solutions and Zoom is the only meeting that has no specific method to auto-update other than downloading and pushing out a new version every time an update is released. In today''s breach rich world costing the economy billions per year, It's unacceptable not to provide an auto update feature that does not require admin rights (part of zero trust)


There are several potential reasons why the Zoom update did not auto-install and required admin privileges:

  1. Change in Installation Requirements: Sometimes, updates include changes in installation procedures, such as requiring admin privileges for security reasons or to modify system settings.

  2. Policy Changes: Zoom might have changed its update policy, requiring explicit admin privileges for certain updates to ensure compliance with security standards or to prevent unauthorized modifications.

  3. Security Enhancements: The update might contain security enhancements that necessitate admin privileges to ensure proper implementation and to protect against potential vulnerabilities.

  4. User Account Control (UAC): If User Account Control settings are configured on the devices, certain updates may prompt for admin credentials as a security measure to prevent unauthorized changes to system files.

  5. Installation Errors: There could have been errors during the auto-installation process, prompting the need for manual intervention by IT to ensure successful update installation.

  6. Group Policy Restrictions: Group policies configured on the network may restrict automatic updates or require admin privileges for software installations to maintain control over the software environment.

  7. System Configuration: The devices may have configurations that prevent automatic updates or require admin privileges for software installations to maintain stability and security.

In summary, the update likely required admin privileges due to security measures, policy changes, or system configurations aimed at ensuring proper installation and protecting the devices from potential risks.