Skip to main content
Solved

Google Chrome Update Error 1603

  • December 5, 2024
  • 3 replies
  • 232 views

Forum|alt.badge.img

Overnight we received at least 100 failed update notifications for Google Chrome on our endpoints. The error is pretty vague and we confirmed that on each endpoint that received the error Chrome was not updated to the expected version 131.0.6778.109. What’s even more bizarre, each endpoint that reported this error no longer shows that Chrome is installed, either directly from the Control Panel or within the Automox Console. So now those endpoints won’t get updated at all since Automox isn’t seeing Chrome installed.

 

“Failed to apply patches ("Google Chrome"): Update of google_chrome failed with exit code 1603”

 

I’m looking for any help in figuring out how to remediate this. I’m going to start by trying to redeploy Chrome with other tools, and pausing the original “Keep browsers up-to-date” policy that was enabled during our onboarding into the product.

Best answer by MarkH-Automox

Hi Nick S,

We are taking a look at this internally.
In the meantime it’s possible to use a template from our Worklet catalog to install the latest version of chrome as long as you have access to it: https://console.automox.com/manage/worklet-catalog/76e612f1-b3ae-5550-86ef-28a31185d0f6

I can post any updates back here as I hear them.

Regards,

Mark

View original
How helpful was this post to you?

3 replies

Forum|alt.badge.img
  • Automox Employee
  • 130 replies
  • Answer
  • December 5, 2024

Hi Nick S,

We are taking a look at this internally.
In the meantime it’s possible to use a template from our Worklet catalog to install the latest version of chrome as long as you have access to it: https://console.automox.com/manage/worklet-catalog/76e612f1-b3ae-5550-86ef-28a31185d0f6

I can post any updates back here as I hear them.

Regards,

Mark


Forum|alt.badge.img
  • Author
  • Rookie
  • 4 replies
  • December 5, 2024

Hi Mark,

 

Unfortunately the worklet includes a command that isn’t available on our endpoints “Get-Win32App”. I replaced that with the below.

 

Get-WmiObject -Class Win32_Product | Where-Object {$_.Name -eq "Google Chrome"}

 

This works on a test VM where Chrome was previously broken by the problem update, I’ll expand to test on endpoints next.


Forum|alt.badge.img
  • Automox Employee
  • 130 replies
  • December 5, 2024

Hi Nick, It appears there were some issues with the installation workflow that Automox and other clients use: https://support.google.com/chrome/a/thread/311347547

New installers have been released by Google which rectify the underlying issue and we have put chrome back into full-support after withdrawing the problematic installers this morning for a time.

 

Any other questions or issues you see please let us know.


Reply


Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings