Hide this message
Looking to compare latest NPM features with previous versions of NPM?
The NPM new feature summary offers a comparison of new features and improvements offered with this release.
Updated February 21, 2017
This article describes the behavior of Chrome packages when first using them in an environment which has Chrome user installs.
Patch Manager 2.1.3
Chrome packages have an Applicability Rule to check:
This registry key is created when the package is installed with the "/S --system-level" switch. Patch Manager Chrome packages are deployed with this switch. When this switch is not used (during a standard user install), a different user dependent registry key is created in HKCU.
The Windows Update Agent (WUA) hasn't access to a specific users HKCU and cannot verify against entries in a user's HKCU.
This creates a difficulty in first time deployment of Patch Manager Chrome packages when Chrome is already installed by the end user. This difficulty can be worked around by creating a custom package, removing the Applicability Rule on the Patch Manager Chrome package to check
However if you remove the rule and have Google Enterprise (.msi) installs, they will be updated also.
Once Chrome has been installed with the "/S --system-level" switches, the HKLM registry key will exist for future deployment and management.