Zoomtopia is here. Unlock the transformative power of generative AI, helping you connect, collaborate, and Work Happy with AI Companion.
Register nowEmpowering you to increase productivity, improve team effectiveness, and enhance skills.
Learn moreKeep your Zoom app up to date to access the latest features.
Download Center Download the Zoom appDownload hi-res images and animations to elevate your next Zoom meeting.
Browse Backgrounds Zoom Virtual BackgroundsEmpowering you to increase productivity, improve team effectiveness, and enhance skills.
Zoom AI CompanionUser groups are unique spaces where community members can collaborate, network, and exchange knowledge on similar interests and expertise.
Help & Resources is your place to discover helpful Zoom support resources, browse Zoom Community how-to documentation, and stay updated on community announcements.
The Events page is your destination for upcoming webinars, platform training sessions, targeted user events, and more. Stay updated on opportunities to enhance your skills and connect with fellow Zoom users.
The Zoom Community is nominated for the 2025 CMX Community Industry Awards in the Customer Support Community category!
Vote now2024-07-03 12:08 PM
We have been alerted that numerous devices have been flagged for vulnerable versions of Zoom (5.X), with the majority of them flagging under the key C:\Users\USERNAME\AppData\Roaming\Zoom\bin\Zoom.exe.
I have attempted to update Zoom via Intune's line of business in the System Context and manually via a Kaseya Procedure. Both systems report that the latest version is installed, which is accurate. However, the majority of these key flags seem to be from profiles that reside on the computer and cannot be accessed or deleted.
When I log into an accessible profile, the latest version is installed. I also attempted to uninstall Zoom from that profile and run the CleanZoom scrubber, but to no avail.
Any advice would be appreciated.
2024-07-07 09:20 PM
2024-07-08 06:04 AM
Hello,
Not sure how a Conditional Access policy helps out with this. Maybe the wrong link was used?