Vimium stopped working after latest Chrome update

[adriatp]

Chrome version: Chromium 144.0.7559.96 (Arch Linux)
Vimium version: 2.3.1 (latest)

Description: After updating Chromium, Vimium shortcuts no longer work. Restarting the browser and disabling other extensions did not help. Now, the following message appears on all pages, while before it only appeared on Chromium settings pages:

Vimium is not allowed to run on this page.
Your browser does not run web extensions like Vimium on certain pages, usually for security reasons.

[ndit-dev]

Same problem but on Edge 144.0.3719.92 (Win 11)

But I'm pretty sure it's some combination of an update and a policy (edge://policy) or security setting. I only have this problem on enterprise owned machines that has enforced security policies through Intune. Problem started a few days ago and came on all machines at the same time. Haven't been able to narrow it down yet. But when testing on standalone machines it works.
Have not changed any policies or security settings for months

[adriatp]

Same problem but on Edge 144.0.3719.92 (Win 11)

But I'm pretty sure it's some combination of an update and a policy (edge://policy) or security setting. I only have this problem on enterprise owned machines that has enforced security policies through Intune. Problem started a few days ago and came on all machines at the same time. Haven't been able to narrow it down yet. But when testing on standalone machines it works. Have not changed any policies or security settings for months

Thanks to your comment, I managed to get it working, since I reviewed the extension’s settings. The thing is, I was using ungoogled Chromium, and I’m not exactly sure why, but after enabling the “Allow in Incognito Mode” option, it now works. I’m not in incognito mode, but enabling that option makes the application work as usual again.

From my side, the ticket can be closed here since the problem is already solved, but I’m not sure this is how it’s supposed to work.

[dithmer]

Same problem but on Edge 144.0.3719.92 (Win 11)

But I'm pretty sure it's some combination of an update and a policy (edge://policy) or security setting. I only have this problem on enterprise owned machines that has enforced security policies through Intune. Problem started a few days ago and came on all machines at the same time. Haven't been able to narrow it down yet. But when testing on standalone machines it works. Have not changed any policies or security settings for months

Just here to reinforce that statement. It still is a big problem with (enterprise managed) edge and we are not even able to find the setting which need to be set to make it work again. It also does not fix the problem for edge, with @adriatp 's fix, even though I hoped so.