Problem with ExtensionSettings policy

315 views
Skip to first unread message

Pavel Aronovich

unread,
Apr 3, 2026, 5:14:49 AMApr 3
to Chromium Extensions
In Chrome version 138, the extension from the CRX file (on the enterprise LAN) is successfully installed by the ExtensionSettings policy.  Since version 144 (this is not accurate), the extension simply does not install. What could be the problem? We roll back the browser to version 138 and everything works.

Pavel Aronovich

unread,
Apr 3, 2026, 6:59:55 AMApr 3
to Chromium Extensions, Pavel Aronovich
Chrome log:

Extension error: Package cannot be installed: "ERROR_REMOVING_OLD_IMAGE_FILE"
or
Extension error: Package cannot be installed: "ERROR_SAVING_CATALOG"

But why the error suddenly appears is not clear!

пятница, 3 апреля 2026 г. в 12:14:49 UTC+3, Pavel Aronovich:

Patrick Kettner

unread,
Apr 8, 2026, 6:47:24 AMApr 8
to Pavel Aronovich, Chromium Extensions
Hi Pavel,
That error means chrome couldn't unlock the extensions package on the disk to remove it (in order to install the new item). The second is if there was a problem with saving the new manifest (which would happen if the old one has a lock on the file). It sounds like it may be a permissions issues? I haven't heard of other reports of this - how common of a problem has this been for you?

--
You received this message because you are subscribed to the Google Groups "Chromium Extensions" group.
To unsubscribe from this group and stop receiving emails from it, send an email to chromium-extens...@chromium.org.
To view this discussion visit https://groups.google.com/a/chromium.org/d/msgid/chromium-extensions/1cca8db7-d9b7-4533-91c8-6eb31dca615en%40chromium.org.

Pavel Aronovich

unread,
Apr 8, 2026, 6:51:47 AMApr 8
to Chromium Extensions, Patrick Kettner, Chromium Extensions, Pavel Aronovich
All rights are available, this is the user's personal directory. We cannot understand why this is happening. If you install version 138 first and then upgrade to 144, then everything works. If there are 144 at once, then this error occurs.

среда, 8 апреля 2026 г. в 13:47:24 UTC+3, Patrick Kettner:

Patrick Kettner

unread,
Apr 8, 2026, 6:55:12 AMApr 8
to Pavel Aronovich, Chromium Extensions
It is happening on a fresh install of the extension? Is this item hosted on the chrome web store?

Pavel Aronovich

unread,
Apr 8, 2026, 6:58:31 AMApr 8
to Chromium Extensions, Patrick Kettner, Chromium Extensions, Pavel Aronovich
Yes, the extension is hosted in the store. But in this case, it is installed from a CRX file hosted on the company's web server. The scheme has been working for many years.
We tried to clean the profile completely and rearrange the chrome.

среда, 8 апреля 2026 г. в 13:55:12 UTC+3, Patrick Kettner:

Patrick Kettner

unread,
Apr 8, 2026, 7:15:29 AMApr 8
to Pavel Aronovich, Chromium Extensions
Have you tried to repackage the extension? Would you be able to share it privately? Have you filed an issue for the problem on crbug.com?

Pavel Aronovich

unread,
Apr 8, 2026, 7:21:27 AMApr 8
to Chromium Extensions, Patrick Kettner, Chromium Extensions, Pavel Aronovich
We didn't try to repackage it, the CRX was downloaded from the store in August 2025.

среда, 8 апреля 2026 г. в 14:15:29 UTC+3, Patrick Kettner:

Pavel Aronovich

unread,
Apr 13, 2026, 5:36:27 AM (10 days ago) Apr 13
to Chromium Extensions, Pavel Aronovich, Patrick Kettner, Chromium Extensions
There is the same error with the repackaged extension. Upgrading the 144th version to 146 also does not help. Everything works correctly if you set 138 and then update.

среда, 8 апреля 2026 г. в 14:21:27 UTC+3, Pavel Aronovich:
Reply all
Reply to author
Forward
Message has been deleted
0 new messages