![]() This way you won't have to always keep that extension unpacked somewhere. So, after unpacking extension in an old format (as described in another answer) you could pack it back with your current Chrome version and then install it as usual. ![]() However, it seems like in Chrome 73 Google forced this change for new installations already and introduced a policy option for updates only. And, new installations of the extension will fail. If your organization is force-installing privately hosted extensions packaged in CRX2 format and you don’t repackage them, they’ll 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, all force-installed extensions will need to be packaged in the CRX3 format. All extensions must be packaged with CRX3 format in Chrome 75 Chrome:'CRXHEADERINVALID' weixin64732313: 6.This problem was reported on and closed as an intended behavior.Īccording to Chrome Enterprise release notes: ![]() Open the extensions page in Chrome or navigate to “chrome://extensions” from the address bar.Ĭheck the “Developer mode” to enable the developer mode.Ĭlick “Load unpacked” and select folder of extracted zip file Solution 2 ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |