Opera 73.0.3827.0 developer update

[kened]

kened Banned @leocg last edited by

@leocg Yes. Windows Defender probably prevented the installation of these dlls at the time of installing Opera Developer; then later he tried to download the dlls again.

[leocg]

leocg Moderator Volunteer @kened last edited by

@kened And you probably will see it happen next times that autoupdate runs.

[kened]

kened Banned @leocg last edited by

@leocg I will wait for the next build.

[padua]

padua @craigsn last edited by padua

@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.

[padua]

padua @ralf-brinkmann last edited by

@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.

[padua]

padua @kened last edited by padua

@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.

[axem1ll]

axem1ll last edited by

I switched to cunning animal at the begging of the year, however didn't completely give up on Opera. In the recent months I've switched backed to Opera and have used it concurrently with a certain cyan-iconed browser that recently switched to chromium. I steel feel like Opera is the true browser because I've used it as my primary(probably the first) since I'd started using the Internet, however I just can't get past by recent shenanigans...

[craigsn]

craigsn @padua last edited by

@padua Thanks Padua. Appreciate the answer. I'll try it.

[A Former User]

A Former User @leocg last edited by

@leocg Well if it is a false positive, why does the browser still work even if that DLL is missing during the install? Can't be an integral part of the browser then can it. But hey, at least it's not running if it's not a false positive. Should def. be looked into more thoroughly though.

[kened]

kened Banned @padua last edited by

@padua Yes.

[leocg]

leocg Moderator Volunteer @Guest last edited by

@qyngali Because it's not using it. The DLL probably would be used after a successful update.

[kened]

kened Banned @andrew84 last edited by

@andrew84:

[A Former User]

A Former User @leocg last edited by

@leocg Of course, otherwise it would be completely pointless for it to be there. I didn't include that in my post because we are talking about a PUP here, which is not Opera's own code (at least I hope it isn't haha) so... what you wrote is exactly why I pointed out that the browser still works. Opera also tried to download it again in the background 2 times today.
But I spent some time searching and Defender also falsely detects FoxieBro in other programs apparently so I don't know. I'm not going to allow it anyway since the browser seemingly works fine without it.

[leocg]

leocg Moderator Volunteer @Guest last edited by

@qyngali It's Opera's auto-update that seems to be triggering the warning. For some reason, Windows Defender thinks that some of the downloaded files are infected.
So probably every time Opera checks for an update, Windows Defender will show the alert.

[A Former User]

A Former User @leocg last edited by

@leocg Yes, I thought that was what we discussed lol.

[ralf-brinkmann]

ralf-brinkmann @leocg last edited by

@leocg I have the autoupdate switched off and I always download the full installation file. No warnings here.

[padua]

padua @leocg last edited by

@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.

[leocg]

leocg Moderator Volunteer @padua last edited by

@padua Basically the difference between auto-update and a manual one is that the first is automatic and the second isn't. The content downloaded should be basically the same.

[padua]

padua @leocg last edited by

@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.

[gmiazga]

gmiazga Opera last edited by

Hey, we are currently looking into the issue with Windows Defender detecting .dll. All our Windows binaries before being published are scanned on VirusTotal. Version 73.0.3827.0 still shows no detections and binaries uploaded there are same like the ones on our autoupdate servers (few CDNs I checked at least) and FTP server.