Chrome Update 100.0.4896.127 via Jamf Causing Issues

New Contributor

Hello all,

I pushed the latest chrome update via Jamf to all our macs. It force closes the app once the policy hits and then it doesn't allow you to open Chrome back up. Only a reboot resolves the issue. Any ideas on why this could be happening? Keep in mind we had no issue with the recent zero day vulnerability a couple of weeks ago.


Valued Contributor II

Pushing 104.0.5112.79 without issues. Where did you get the package or did you package it? Maybe check permissions.

Contributor III

I've seen a security prompt (chrome asking for admin privs / password) which never gets focus, stuck in the background. It may not be the same issue but saw that user had no persistence in Chrome eg. sign in but never retains login / autofill etc.

A reboot / login brought that dialogue to the foreground / user authenticated, which allowed Chrome to shut the hell up and do it's job. I've switched to pkg in our deployments;




We're having a lot of issues with Chrome being deployed via App Installers. Any updates on fixing that?