Why does it occur in your case?Īccording to resolution of this (not-a-)bug:īeginning in M73, Chrome only allows installation of extensions signed with a CRX3 package. However, it seems like in Chrome 73 Google forced this change for new installations already and introduced a new policy option for updates only.īut wait, it says all of them were converted automatically, so. New installations of the extension will fail. If your organization is force-installing privately hosted extensions packaged in CRX2 format and you do not repackage them, they will stop updating in Chrome 75. Privately hosted extensions that were packaged using a custom script or a version of Chrome prior to Chrome. Starting with Chrome 75, this restriction will also apply to force-installed extensions.
Extensions signed and hosted in the Chrome Web Store have been automatically converted.
Starting with Chrome 70, all non-force-installed extensions must be packaged in the CRX3 format. According to Chrome Enterprise release notes:
0 kommentar(er)
