You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If you apply the settings from the link posted by @tophf before interacting with the notification prompt, and restart Chrome, it won't affect your scripts. In short:
Go to chrome://flags/
Search for mv2
Set to Enabled: "Allow legacy extension manifest versions"
Set to Disabled: the 3 remaining ones, all named "Extension Manifest V2 Deprecation ... Stage"
Reacted by Anton, Roberto Abdelkader Martínez Pérez, bekki, Rolle Laukkarinen, Sonic, Kevin Bloch, Andreas Keefer, Yurii Pakhota, Raed Bahri, LakeAcross and 16 more
Reacted by Baki Nazik
Reacted by Kevin Bloch and Zepmanbc
Reacted by Anton, bekki, Kevin Bloch, Youar9e and blackrock33
Yeah, the issue was I clicked a bookmark immediately when starting chrome and it closed the pop-up, which nuked I don't even know what extensions along with their associated settings
Can confirm quoted comment worked! Screenshot in case anyone needs it.
If you apply the settings from the link posted by @tophf before interacting with the notification prompt, and restart Chrome, it won't affect your scripts. In short:
Go to chrome://flags/
Search for mv2
Set to Enabled: "Allow legacy extension manifest versions"
Set to Disabled: the 3 remaining ones, all named "Extension Manifest V2 Deprecation ... Stage"
Reacted by Andrei, Roberto Abdelkader Martínez Pérez, heartnn, dan, Glenn 'devalias' Grant and lukasz-brzozko
I noticed the problem with sync two weeks ago in new installations which happens in MV2 as well, but then I forgot about it and @gera2ld didn't reply. We'll fix it.
Hi @tophf, it seems that version 2.43.0 is the first official MV3 compliant Violentmonkey?
Is it all cleared, or are there any stuff that don't work anymore, with MV3?
The release note doesn't mention MV3 and I saw no official resolution comments here, either.
I would like to celebrate! Can I? 😅
P.S. My Violentmonkey extension automatically updated to version 2.43.0 on its own, without deleting my scripts, as for other usual updates.
@hotrongnghia310, no one here silenced any dissent, also no one in open source owes anyone anything, take it or leave it. Personally I'm a user of Violentmonkey like anyone else and I converted it to MV3 myself when Chrome 150 finally removed all other workarounds.
@jesus2099, everything should work and actually document-start became more reliable without the need for "synchronous page injection" option, but there seems to be a bug with reminding the user to enable "Allow User Scripts" option and so since they don't nothing works without any indication.
Reacted by jesus2099, iluminaria, Pascal Polleunus and de-tre
Activity
tophf commentedon Mar 3, 2025
You can enable ManifestV2 manually:
https://stackoverflow.com/questions/79283218
SyndiShanX commentedon Mar 4, 2025
Either that or Load the Extension Locally
SyndiShanX commentedon Mar 4, 2025
It sucks that it nuked all of my scripts though
fuminchao commentedon Mar 4, 2025
me too. Chrome sucks
dandrei commentedon Mar 4, 2025
If you apply the settings from the link posted by @tophf before interacting with the notification prompt, and restart Chrome, it won't affect your scripts. In short:
chrome://flags/mv2SyndiShanX commentedon Mar 4, 2025
Yeah, the issue was I clicked a bookmark immediately when starting chrome and it closed the pop-up, which nuked I don't even know what extensions along with their associated settings
jpuckett-di commentedon Mar 4, 2025
so does this mean that Violentmonkey won't support the new version, and we are reliant until Chrome finally removes the legacy v2 manifest option?
sa124a commentedon Mar 7, 2025
In version 131.0.6778.205, this option"Allow legacy extension manifest versions" was removed
pihao commentedon Mar 7, 2025
Version 134.0.6998.36, Windows
bekkibau commentedon Mar 9, 2025
Can confirm quoted comment worked! Screenshot in case anyone needs it.
clusterepsilon commentedon Mar 16, 2025
This is a temporary solution that will cut off a lot of users.
The flags will be removed soon.
It needs to be ported to version 3.
wk722 commentedon Mar 17, 2025
@tophf It's not working with new chrome version 134.0.6998.45
tophf commentedon Mar 17, 2025
It's working.
wk722 commentedon Mar 17, 2025
@tophf Can not install the extension.
186 remaining items
Stolka commentedon Jul 16, 2026
Thanks for the reply, I think I was able to narrow down the issue, upgrading from MV2 to MV3 seems to work, but a fresh installation from CWS doesn't.
tophf commentedon Jul 16, 2026
I noticed the problem with sync two weeks ago in new installations which happens in MV2 as well, but then I forgot about it and @gera2ld didn't reply. We'll fix it.
dnet890 commentedon Jul 16, 2026
MV3 is here and so far so good for me on Brave and Edge
https://chromewebstore.google.com/detail/violentmonkey/jinjaccalgkegednnccohejagnlnfdag
https://microsoftedge.microsoft.com/addons/detail/eeagobfjdenkkddmbclomhiblgggliao
jesus2099 commentedon Jul 16, 2026
Hi @tophf, it seems that version 2.43.0 is the first official MV3 compliant Violentmonkey?
Is it all cleared, or are there any stuff that don't work anymore, with MV3?
The release note doesn't mention MV3 and I saw no official resolution comments here, either.
I would like to celebrate! Can I? 😅
P.S. My Violentmonkey extension automatically updated to version 2.43.0 on its own, without deleting my scripts, as for other usual updates.
tophf commentedon Jul 16, 2026
@hotrongnghia310, no one here silenced any dissent, also no one in open source owes anyone anything, take it or leave it. Personally I'm a user of Violentmonkey like anyone else and I converted it to MV3 myself when Chrome 150 finally removed all other workarounds.
tophf commentedon Jul 16, 2026
@jesus2099, everything should work and actually document-start became more reliable without the need for "synchronous page injection" option, but there seems to be a bug with reminding the user to enable "Allow User Scripts" option and so since they don't nothing works without any indication.
jesus2099 commentedon Jul 16, 2026
Love you, thanks so much!! ❤️
jcnnik commentedon Jul 16, 2026
The entire browser keep crashing as long as Allow User Scripts isn't enabled.
jesus2099 commentedon Jul 16, 2026
Not my Vivaldi 8.1.4087.53 / Chrome 150.0.7871.175.
jcnnik commentedon Jul 16, 2026
Titanium 150.0.7871.124
jesus2099 commentedon Jul 16, 2026
Maybe open a new ticket, @jcnnik.
tophf commentedon Jul 16, 2026
@jcnnik, it means a bug in the browser, not in Violentmonkey.
ppo commentedon Jul 17, 2026
Being unavailable and now back made me realize how much I love and use my userscripts… and VM of course.
❤️ Thank you so much for all your work – especially on this, which must have been a bit stressful.