Security Compliance

Unable to install a Chrome package on a managed system

This article describes an issue with installing a Chrome package on a managed system running Chrome installed by the user.

First published date

10/22/2018 9:18 PM

Last published date

10/22/2018 9:18 PM

Overview

When you push a Google Chrome package update to a managed system that is running a version of Chrome installed by the user, the procedure fails. 

Product section

Patch Manager

Cause

Google® Chrome® packages check an applicability rule (see Unable to install a Chrome package on a managed system for information) in the following registry key:

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\Google Chrome

This registry key is created when the package is installed with the following switch:

/S --system-level

 

Patch Manager deploys Chrome packages using this switch. When this switch is not implemented during a standard user installation, the following user-dependent registry key is created in HKEY_CURRENT_USER (HKCU):

HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Uninstall\Google Chrome

 

The Windows Update Agent (WUA) cannot access the HKCU for specific users and cannot verify against entries in a user's HKCU. When Patch Manager deploys Chrome packages for the first time, Patch Manager cannot install the package on the targeted system. 

Resolution

Create a custom package and remove the Applicability Rule on the Patch Manager Chrome package that checks the following HKCU:

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\Google Chrome