We are currently investigating this issue and looking for a fix. We will release update as soon as we resolve the problem.

We just released stable 72.0.3815.320 which includes earlier mentioned fixed for address bar issue. This will also be followed up by developer update 74.0.3870.0 later today and beta update later this week which were also affected by this issue.

Microsoft removed this detection. Their full reply:

We have removed the detection. Please follow the steps below to clear cached detection and obtain the latest malware definitions.

1. Open command prompt as administrator and change directory to c:\Program Files\Windows Defender
2. Run “MpCmdRun.exe -removedefinitions -dynamicsignatures”
3. Run "MpCmdRun.exe -SignatureUpdate"

Alternatively, the latest definition is available for download here: https://www.microsoft.com/en-us/wdsi/definitions

From our side there have been small changes in installer code on developer which probably got detected as malware together with Microsoft definitions update done on 2-3 October.

We have reverted to previous version of browser.js so problem should be gone soon for all users. Usually can take up to a few hours depending when was last update fetched.

If you keep up to date with the latest security updates on macOS you might have spotted warnings about the Opera application being damaged on your system. This is related to how our update mechanism works. If you see this warning there is nothing to worry about. Unfortunately you will have to reinstall the latest version of Opera from www.opera.com. If you won’t reinstall you will be stuck with the older version and will be getting more of those warnings as autoupdate will try to execute but fail each time.

Some more background on this issue

When we perform updates they are first downloaded into $TMPDIR. One of the intermediary directories created during this process used to end with the .app extension. We download the update package to this directory and perform further operations on it.

It turns out that there was a security issue in macOS, which meant .app directories that didn’t contain an actual application could also have been used by malware to execute code outside of Gatekeeper. Apple released a security update that closes this loophole, as versions 10.15.7 and 11.3 of macOS, which were released this week.

The fix causes our intermediary directory to be detected as a broken application, and a system warning is displayed, blocking any operations on the content of this directory and breaking our update mechanism. The fix on our side is to simply use a different name for the intermediate directory.

If you would like to read more about this issue please head to https://objective-see.com/blog/blog_0x64.html.

@carlosjeurissen at the moment we do not have plans for closing our store. Will try to get some information about plans for allowing v3 in our store.

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.

@yanta this was expected push from us. We recently added feature to opt-out for this promoted content if it disturbs you. To do so:

• Make sure flag opera://flags/#partner-bookmarks-opt-out is enabled
• Go to opera:settings
• Disable 'Receive promoted Speed Dials and Bookmarks'

Please note that it's currently enabled in developer only and should make it's way to stable with v56 (or sooner when we confirm there are no unintended regressions with it).

Another update. Apparently initial fix for id's wasn't working properly and we done another fixup to this. This second fix for missing bookmarks was triggered manually for @msb and @berrram accounts. @berrram could you try to log out of sync and log in again to confirm that bookmarks appear for you again? If you can confirm this works this fix will be triggered for all users.

@andrew84: Depending on status of new popout implementation we will adjust accrodingly before O66 hits stable to mkae sure . Unfortunatelly problem with video popout freezing is caused by another fix that came from chromium and with our current implementation we can't have both issues fixed.

@sam1973 you should be able to reach support on https://support-vpn-pro.opera.com/hc/en-us options to submit request or start a chat shouldn't require you to register

@sam1973 Hi Sam. I’m sorry to hear about the problems you’ve encountered with your VPN Pro subscription. Please contact VPN Pro Customer support via chat or at vpn-pro@support.opera.com. With your Opera account details, we will be able to check your subscription status, help you fix technical issues, or refund your money. Please note that we offer a 30 day money back guarantee. Whatever solution you choose, we will certainly be able to solve your case to your satisfaction.

@adam1709 True, but this specific issue was also released in chromium extended update targeting 104 version: https://chromereleases.googleblog.com/2022/09/extended-stable-channel-update-for.html

@adam1709 those updates are for chromium 105. Opera 90 is based on chromium 104.

We are working on other payment options. Stay tuned!

@upnorth: it's included in update 90.0.4480.84.

@jenming Could you try to close Opera and make sure no processes are running before starting it again.

To check running processes start Activity Monitor and search for Opera. After closing browser there should be no processes running (Opera, Opera Helper, etc.). Perhaps update process for browser.js is stuck for some reason and you are not getting updates.

@jenming this is old browser.js version. Current one should display August 23, 2022.

For reference.
macOS works a bit differently. Closing last window doesn't close application. This is indicated by small dot under icon of application in Dock. In such case pressing on application will open new window .

To restore previous windows in such case recently closed option can be used to reopen last closed window. It's available in History menu.

@semsemsem this should only appear when update is actually performed. You could try to check opera://update if something wrong happens there. I would also suggest reinstalling browser. Might resolve problem and could be easier then trying to investigate cause.