Are you deploying via Mac Apps?
Yes, chrome is up to date but need to find out the root cause of this error message and resolve.
Yes, chrome is up to date but need to find out the root cause of this error message and resolve.
I ask because we were deploying Chrome via Mac Apps (including the provided config profiles) and were seeing the same thing. We then set the deployment status to off and had a user quit the application and relaunch. The error was no longer present.
I ask because we were deploying Chrome via Mac Apps (including the provided config profiles) and were seeing the same thing. We then set the deployment status to off and had a user quit the application and relaunch. The error was no longer present.
This issue has been happening since the upgrade to Sonoma, I stopped the mac apps deployment all together and still received that error message. I was manually pushing out google every week and that was just too tiresome so I tried the mac apps again, but you can choose automatic or manual, manual seems to work for me. Just need to get this error message to go away.
Been seeing this for a while too.
Also seeing this with Edge BTW.
This issue has been happening since the upgrade to Sonoma, I stopped the mac apps deployment all together and still received that error message. I was manually pushing out google every week and that was just too tiresome so I tried the mac apps again, but you can choose automatic or manual, manual seems to work for me. Just need to get this error message to go away.
We're seeing the same error on Airs that are running Monterey.
Seeing the same thing on our end. Turning off mac apps deployment immediately got rid of the error 5 on chrome and edge.
What do you mean turning off the deployment, we have isntallomator looking for the app and trying to update, but we dont instal the app by default. We have the error above.
This issue has been happening since the upgrade to Sonoma, I stopped the mac apps deployment all together and still received that error message. I was manually pushing out google every week and that was just too tiresome so I tried the mac apps again, but you can choose automatic or manual, manual seems to work for me. Just need to get this error message to go away.
I have been trying to push out the update for chrome with config profiles via mac apps as well and am seeing the same thing across multiple users. I have removed any policies that have chrome updates so there aren't any clashing policies, but so far I can't find anything as to why this is happening. I'd love to know if anyone found a fix for this.
What do you mean turning off the deployment, we have isntallomator looking for the app and trying to update, but we dont instal the app by default. We have the error above.
Turning off the deployment in Mac Apps. A lot of us are trying patching with Mac Apps to keep users up to date, but it's not playing nice.
seen the same error when then new update came out for chrome yesterday via jamf app catalogue.
Anyone found the root cause apart from to turn it off an on again
According to Jamf (I've created a tech case about this error) this behaviour is "normal" if Mac Apps is used to distribute and update Chrome as the internal update mechanism of Chrome is replaced by the update mechanism of Mac Apps/Jamf App Catalog.
According to Jamf (I've created a tech case about this error) this behaviour is "normal" if Mac Apps is used to distribute and update Chrome as the internal update mechanism of Chrome is replaced by the update mechanism of Mac Apps/Jamf App Catalog.
I saw that same thing. Not sure why it's considered normal behavior, but it seems like Chrome isn't broken, just unable to update on it's own now.
I saw that same thing. Not sure why it's considered normal behavior, but it seems like Chrome isn't broken, just unable to update on it's own now.
If you look at the App Installer Metadata under the Google Chrome Mac app it says:
"Built-in auto-updates disabled" Yes
so it's normal behavior because the MDM is controlling the update cadence and versioning, and not end-users
thats really helpful thanks all
We're seeing the same error on Airs that are running Monterey.
Following, We also have Airs running Ventura and getting the same errors. I've inherited this from previous Tech Admin. I've tried removing almost all Jamf profiles and still getting error. Any help in resolving this would be GREATLY Appreciated!!
