Forum Discussion
Edge Dev Version 137.0.3255.0 (64-bit) corrupted extensions
-After upgrade to latest version Edge Dev is reporting many extensions as being corrupt.
-Repairing individually also does not resolve the issue, the entry disappears in Extension settings.
-Extension icon on taskbar show as blue jigsaw piece instead of default Extension icon.
-Fresh install of latest dev version also behaves similarly.
-When trying to install extension from MSoft store get Error message below:
16 Replies
Same issue here on Edge 137 when using remote desktop servers with user profile disks. The user profile disks must be seen as a symlink triggering the bug. Downgraded to Edge 136 for now as a workaround.
Yesterday i had problems on Edge 137 devloading extensions, i had strange errors like "no icon in manifest"
The problem is that i was loading the extension from a virtual on LAN hard drive. When i loaded it from local machine (desktop) it worked perfect!
I leave this here for the record, hope someone find it useful
Looks like this might have been fixed in build 138.0.3309.1 that I got today. (2025.05.15)
This time, clicking on repair actually did reinstall all 3 of my corrupted extensions and they are now working correctly again. Hopefully they stay fixed permanently and it's not a two day fix!
Edit. 2 out of the 3 extensions are now marked as corrupt 2 hours later - obviously still not fixed :-(I'm running edge Beta 138.0.3351.21 now and it hasn't corrupted yet. Hopefully it is fixed now.
Im currently using the --user-data-dir switch in the Edge Dev shortcut rather than symlink for the User Data folder. So far it is working. I suppose this is the official method. I do have the program files folder on a symlink to another drive though. Also works without it using the switch.
You could try copying the contents of your User Data folder to another location and using the --user-data-dir switch to point to that location, see if your extensions work correctly. Then try again without the switch using the default location.
If still no luck, copy the contents from the new location back to the default User Data location. But first backup the original User Data folder by simple rename.
Same problem only with adguard
Update: 08/05/25
Have just tested the latest Chrome Beta Version 137.0.7151.15 (Official Build) beta (64-bit) with symbolic link.
It has the same issue! Absoblogginlutely
Clicking Repair also removes extension from the list.
No profile sign-in/sync. Clean install to C: (OS), then symlink to external drive.Also have the same problem with the latest Canary build Version 138.0.3304.0 (Official build) canary (64-bit). Seems there is no fix in the pipeline just yet.
Just to confirm I am using a symlink to another drive for the User Data folder which I have been doing for years only once experiencing a similar issue back in 2024.
EdgeDev App fails to load when EdgeDev data is on junction symbolic - Microsoft Community
No profile sign-in/sync.Same issue for me on the latest version 137.0.3296.4 too.
What is odd is that my personal profile is fine with the extensions and even had 2 copies of Keeper, one from the Microsoft store and one installed directly from Keeper (different versions interestingly).
Attempting to repair an extension still continues to just remove the extension instead and adding new extension provides the same error
I am however able to install keeper to a different work profile so it's related to my default, synched work profile account.
Upgraded to Version 137.0.3296.4 (Official build) dev (64-bit), same problem.
Just updated to Version 137.0.3282.1 (Official build) dev (64-bit)
-Same problems as before.
Is there anyone even doing any testing before pushing updates in dev channel?Same issue in that about a third of my extensions are marked as corrupt - on my local machine.
Clicking on repair just removes them from the list of extensions.
Same edge version.
Another machine running the same edge version signed in with the same edge profile does not have the issue (at the moment).
I do not have a symlink for the Dev local folder though.
I created a new work profile and that fixed it for 5 days, but this morning after rebooting the computer I'm back to a corrupt extension in the new profile. It worked great Wednesday thru Friday. Currently running 137.0.3296.4 (Official build) dev (64-bit)
