I second this. This 'feature' is unwelcome and an option to disable would be welcome. Thank you.

Same issue.

Toggling ad-block makes no diff.

@l33t4opera :"...try to use the previous version of the Opera:.."

Unable to switch to an older version - 2920 directory is empty.
Is there a nightly build site / older versions archive for the Opera Dev browser?

Win 10 1709 Opera Dev 54.0.2929.0

Although it is listed as a known issue, if I may, I suggest that 'extensions deleted after update' should be a show stopper for any release including developers' version.

Opera developers and QA team may please consider this.

Thank you.

@leocg Obviously, of course!

Well, at least, it should be so in a thoroughly QA'd update process.

The issue here is that there is a difference, in this situation - the automatic update throws a warning and the downloaded update (according to other posters) does not.

My request "Can we request some one on the dev / QA team to see what the difference is between an autoupdated update and downloaded update" was for them to look into this specific case and not a request for general info on autoupdate vs downloaded update.

Thanks again to everyone in the Opera browser team for a good browser - just that this issue needs to be escalated for a QA team / dev team response.

@leocg Can we request some one on the dev / QA team to see what the difference is between an autoupdated update and downloaded update - if there is a dll in the autoupdate that is not in the downloaded update and doesn't need to be there - then it shouldn't.

Autoupdate is a useful feature and time efficient and most users may prefer to use it.

Thank you.

@kened Good point. When there are so many posts on the forum about this issue - even if it indeed is a false positive a quick and reassuring response from a moderator / admin / dev team member would be appropriate.

Thanks to the Opera team.

• it is a browser that I have been using for many years (from when there was some detail on the Opera web site / blog about the small town where the Opera software development work was happening - in those days)

But, when there is an issue like this, a formal / official response in a day or two would be welcome.

@ralf-brinkmann It was from the 'update and recovery' option of the Opera Dev version.

As I have mentioned in another post, there was no issue with the regular release version.

@craigsn I used a 'thorough' uninstaller, which uninstalls and looks for leftover folders / files and allow deletion of them as well- the one I used is Revo Uninstaller, the free edition.

Just to check, switched to the regular release version of Opera - which did not throw up the Foxiebro issue.

@artexjay Same experience with the recent Opera dev edition update - it was trying to install the Foxiebro.

When Windows Defender automatically deletes it, then the notification does not appear, but the dll for Foxiebro is in the install package.

This is terrible for a legitimate browser! And a potential reputation killer.

The release edition of Opera does not seem to have this issue only the dev edition.

Intentional or unintentional the Opera team must acknowledge this and issue a fix - possibly including an apology for the slip up.

Thank you.

@mgeffro Thanks for this clarification and glad to note that the Opera team already considers this a show stopper even for an 'alpha' release / developers' build.

Thank you for the fix in 56.0.3026.0.

Keep up the good work and thanks for a good browser.

Although it is listed as a known issue, if I may, I suggest that 'extensions deleted after update' should be a show stopper for any release including developers' version.

Opera developers and QA team may please consider this.

Thank you.

@leocg I notice that this is listed as a known issue.
"DNA-71259 Extensions deleted after update."

Thanks.

Extensions are not listed on the toolbar.
Extensions are not listed in extensions page either.