Why does Google Chrome Product version not get updated when Kace patches it?

We recently setup Kace at our school and I am still getting my head around using its myriad of features. One of the things we are the most excited about is the patch automation. So I have been messing around with it for the past few days patching Google Chrome on my test VMs. I have noticed while the K1000 patches Chrome up to the current version in the catalog as expected, the product version information on the VM never gets updated to reflect the updated version. For example, I manually installed version 52.0.2743.116 via the Chrome enterprise MSI and let the patch schedule run. It completes without issue but the product version number does not change in add/remove programs. However, when looking in chrome://help in Chrome the correct version (53.0.2785.89) is indeed installed.

I can't help but think I have either overlooked something or just massively don't understand how patching in Kace works. Any help/explanations/insights would be greatly appreciated.

1 Comment   [ + ] Show comment
  • Hi, Well I wanna replicate this, I could not find that MSI for that version.... I´ll use 6.4 latest and a Win 8.1 testing machine.

    If you could share that .MSI... It is impossible to download it (to mirror your version), because I deployed Chrome with Managed Installations, using the regular .EXE installer, named "ChromeStandaloneSetup64.exe", and no issues updating via patches - Channeler 4 years ago

Answers (2)

Posted by: anonymous_9363 4 years ago
Red Belt

I believe you may have stumbled across one of the (many) reasons why Google's so-called "enterprise" MSIs are a piece of [takes a breath...] work. They're simply a wrapper for Google's own installers.

Chrome's dutifully records version information from the MSI in ARP but (I'd bet my last dollar that) the patch is probably not updating that information. It would be simple enough to determine that by using a lightweight snapshotting tool (my current favourite of which is ZSoft Uninstaller) to perform 'Before' and 'After' snaps of a manual installation of the patch. I'm confident you won't see the ARP stuff even being accessed, much less updated.

  • That makes sense. That was kind of what I was suspecting is going on. So the next question is will the K1000's patch management system work as intended for Chrome patching while not updating ARP on the target systems? - jrblalock 4 years ago
    • We have been using KACE to patch Chrome for at least a year and it works as expected. We also see the static version problem but it is not affecting patching. - JasonEgg 4 years ago
Posted by: anonymous_9363 4 years ago
Red Belt

Pass, I'm afraid. I know next to nothing about Kace boxes (I'm a refugee from the days when IT Ninja was AppDeploy).

Unfortunately, one of the poor things about ITN is that the forum software was switched to what you see now and, unlike every other forum on the planet, there's currently no way that people can see the latest posts on it, unless they're subscribed to the thread. Subscribers to this thread presently number 2: you and me!

Maybe someone more Kace-qualified than me will  pop by by chance... :-(

  • Yeah, I have not been terribly impressed with the forum layout myself. Thats for the help you could provide. Hopefully someone else will stumble across the question. - jrblalock 4 years ago
This website uses cookies. By continuing to use this site and/or clicking the "Accept" button you are providing consent Quest Software and its affiliates do NOT sell the Personal Data you provide to us either when you register on our websites or when you do business with us. For more information about our Privacy Policy and our data protection efforts, please visit GDPR-HQ