scriptsafe icon indicating copy to clipboard operation
scriptsafe copied to clipboard

Google turns off ScriptSafe extension after updating Chrome browser to version 138.0.7204.101

Open jbionic2016 opened this issue 7 months ago • 5 comments

Hi there,

That's what it looks like:

Image

I wonder how to turn your extension back?

Best regards

jbionic2016 avatar Jul 11 '25 09:07 jbionic2016

You find answeres in other places of the web, but at the moment:

  • enable loading of v2 extensions here: chrome://flags/#allow-legacy-mv2-extensions
  • restart chrome
  • download release for chrome, unzip
  • load extension manually in the extension tab (chrome://extensions/). You may need to enable developer mode (unsure about that step)
Image

though in the long run we will have to switch to another browser

daniil-g avatar Jul 14 '25 06:07 daniil-g

hi all. if you want use disabled extension, create *.txt-file and paste: ;---------------------- begin file -------------------- Windows Registry Editor Version 5.00 [HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Google\Chrome] "ExtensionManifestV2Availability"=dword:00000002 ;---------------------- end file ---------------------- rename .txt to .reg and execute (apply to registry), - chrome need be closed before apply.

idnxt avatar Jul 14 '25 07:07 idnxt

to chrome v139 - copy-paste the links and apply en/dis (restart chrome after each one):

chrome://flags/#temporary-unexpire-flags-m137 — Enabled chrome://flags/#temporary-unexpire-flags-m138 — Enabled chrome://flags/#extension-manifest-v2-deprecation-disabled — Disabled chrome://flags/#extension-manifest-v2-deprecation-unsupported — Disabled chrome://flags/#allow-legacy-mv2-extensions — Enabled

idnxt avatar Aug 13 '25 05:08 idnxt

to chrome v139 - copy-paste the links and apply en/dis (restart chrome after each one):

chrome://flags/#temporary-unexpire-flags-m137 — Enabled chrome://flags/#temporary-unexpire-flags-m138 — Enabled chrome://flags/#extension-manifest-v2-deprecation-disabled — Disabled chrome://flags/#extension-manifest-v2-deprecation-unsupported — Disabled chrome://flags/#allow-legacy-mv2-extensions — Enabled

This no longer works with the last Chrome update, but you can use this method:

  1. Find the shortcut for Chrome and choose "Properties"
  2. At the end of the end of the path listed in "Target" add a space (should go AFTER the quote)
  3. Add the following after the space: --disable-features=ExtensionManifestV2Unsupported,ExtensionManifestV2Disabled 

Use this altered shortcut to launch Chrome. Works for me, but knowing Google, this may be subject to change.

rpitera avatar Sep 10 '25 15:09 rpitera

Hi there, I've decided to follow Chrome's privacy/security recommendations and uninstalled all 6 extensions instead of rolling Chrome's manifest version back to V2. For some of my extensions I've managed to find a suitable substitution supporting v3 (ScriptSafe was changed to NoScript), for others - no.. I suppose, authors could have implemented necessary changes to support manifest v3 by now, for sure. Instead of inventing new sophisticated ways to stick to the older traditions and technologies.

jbionic2016 avatar Sep 10 '25 21:09 jbionic2016