Please not the last part of the applicability rule RegType32="true"
This component ensure we search the Wow6432Node.
Usually, Wo6432Node will not be explicitly written out, instead thise is used to ensure proper redirection of registry searches for a 32 bit application ona 64 bit operating system, and also ensure it is handled appropriately on a 32 bit operating system as well.
In this folder, there is a file 'Zoom User Based Install CI.cab' which can be imported as a Configuration Item, and you can deploy a Configuration Baseline containing this and determine who has Zoom as a user.
Can you please check if the Zoom installation you have installed is a system wide version?
We commonly seen Zoom installs that are the user-based install that is in the user profile. If it is the per-user install then it cannot be updated by a Software Update, as this runs in system context.
The improvement to third party catalogs in the console is certainly nice. It allows a lot more flexibility in what you select to sync. If you are not using the Publisher tool, then I would definitely recommend upgrading to get the enhanced in-console third party update publishing experience.
I'd say there are a large number of features, bug fixes, and improvements across the board to justify upgraded from 1902 all the way to 2002! Do you have anything holding you back from changing versions?
We generally do not host the content. Our tool downloads the files directly from the manufacturer. We download the binaries to a temporary directory and then package up the updates and or applications.
We provide the EXE because there is no direct download for the MSI.
While it might be possible to extract the MSI from the EXE, that adds some extra layers of complexity when it comes to automation, and is something we generally try to avoid. It is best to download the binary directly from the vendor without having to make modifications.
There are a lot of scenarios where even in an enterprise environment the user might install software such as CCleaner or Malwarebytes, such as you saw.
Removing such software due to licensing is definitely a good approach, and likely the preferred path, but I can see a scenario where removing software can take time to get the approvals and work through corporate processes. In the meantime, the software could be patched to mitigate potential vulnerabilities.