Submit a ticketCall us

AnnouncementsChange Is Inevitable

Get valuable help when it comes to tracking and monitoring changes. SolarWinds® Server Configuration Monitor (SCM) is designed to help you: detect, track, and receive alerts when changes occur, correlate system performance against configuration changes, compare server and application configuration against custom baselines, and verify application and system changes.

Learn more.

Home > Success Center > Patch Manager > Patch Manager - Knowledgebase Articles > Unable to install a Chrome package on a managed system

Unable to install a Chrome package on a managed system

Updated February 21, 2017

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. 

Environment

Patch Manager 2.1.3

Cause

Google® Chrome® packages check an Applicability Rule 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. 

Workaround

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

 

 

 

 

Last modified

Tags

Classifications

Public