[Manifest v2] Stopped working completely after the registry fix - any fix?

[Bharath Kumar]

Hi, 

A couple of weeks before the AutoControlApp stopped working - I came here looking for solution - Realized it was mentioned right there on the Chrome Extension page - https://www.autocontrol.app/force-enable-Manifest-V2-support 

So, I applied this fix and it started working. I'm not sure what happened it stopped working since yesterday (probably installed uBlock a couple of days before may be that???) 

I checked to see if it got switched to manifest v3, but it wasn't. Regardless I did double clicked on the registry file again and refresh the policy.

The browser still shows this  -> "Your browser is managed by your organisation" but I am not able to get it work. Any fix for this?

I noticed people talking about other and suggesting other temporary alternatives. So, I will try to do my bit for others facing same problem. I usually use Chrome as well as Edge -> it supports all of chrome extensions and luckily AutoControl.app has some settings to enable across device sync or something, so I am surviving on that. I will be switching my entire workflow on Edge, not sure if its possible or practical :( 

Thanks! 

[Alex]

read this discussion https://groups.google.com/g/autocontrol_app/c/ly9Q9vgTwdI/m/vXNlcPcQBwAJ

среда, 13 августа 2025 г. в 02:17:04 UTC+3, Bharath Kumar:

[Alex]

1. https://www.autocontrol.app/force-enable-Manifest-V2-support

   • Download Force Manifest V2 availability.reg to your computer.
   • Double-click on the file and confirm the message box.

   This action could be reverted by Remove Manifest V2 availability.reg + steps 2, 3.

2. Go to chrome://policy and click on the Reload policies button.

3. Go to chrome://flags/

   • Switch Allow legacy extension manifest versions to Enabled
   • Maybe Temporarily unexpire * flags also required.
   • Restart the browser.

4. Run browser with shortcut parameter (add to Target field in details) -disable-features=ExtensionManifestV2Unsupported,ExtensionManifestV2Disabled It seems not required in Chrome 138, but 140 (dev/canary) does not allow enabling mv2 extensions without this command.

среда, 13 августа 2025 г. в 15:33:34 UTC+3, Alex:

[Bharath Kumar]

I couldn't figure out how to do this --> "commandline --disable-features=ExtensionManifestV2Unsupported,ExtensionManifestV2Disabled"  
I did these 

```text

flags

Disabled

Extension Manifest V2 Deprecation Warning Stage
Extension Manifest V2 Deprecation Disabled Stage

Extension Manifest V2 Deprecation Unsupported Stage

Enabled

Temporarily unexpire M137 flags.

Allow legacy extension manifest versions

```
Now, its working! 

Thanks a lot! 

[Alex]

Add ` --disable-features=ExtensionManifestV2Unsupported,ExtensionManifestV2Disabled` to Chrome's shortcut parameters. I checked in Windows.
Flags - on chrome://flags/ page

среда, 13 августа 2025 г. в 21:25:04 UTC+3, Bharath Kumar:

[Bharath Kumar]

Its working now, I will try that option once the current fix stopped working. Thank you !!! 

[Erwin Noveno]

how can i rollback to version 138?

[Bharath Kumar]

I guess you need to have an offline installer for that version. But you can apply this fix. Its working on ' Version 139.0.7258.128  '.