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

Hey, there is problem with one of oour certificates. We are currently in process of releasing client update as this can't be handled on server side currently.

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.

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.

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.

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

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

Hey, got a good news for you all. If you enable flag opera://flags/#dynamic-demuxer-selection issue should be resolved. It's still disabled by default in 54.0.2952.71 and will be enabled be default when 55 goes stable but you should be safe to turn it on now.

@johnd78 We were cleaning up old code and decided to drop old implementation in favor of easier maintenance. Hopefully there shouldn't be further changes to this.

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.

@chas4: Hey, we already have this fixed internally. Problem is with latests security update from Apple and way Opera autoupdate process names temporary directory in $TMPDIR. Current beta 76.0.4017.88 already contains this fix and next updates should work correctly.

@andrew84 due to problems with builds (compilation/crashes) we weren't able to release it earlier this week. Should be back with new build on Monday.

@chas4: weird version is expected change. It was added for easier identifying if it's x64 or arm64 build

@operafanuk hey, we are testing all release but on 64-bit Windows 7. We are also running tests on Windows 7 32-bit. We haven't noticed any errors on either sytem.
Could you check if any logs are generated in one of following folders after you try to run installer:

• %temp%.opera\Opera Installer
• %temp%\Opera Installer

Please also send us your exact system version:

• winver (run from Start Menu)

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.

A workaround has been pushed from server which should have addressed this issue. This will be later followed up by client hotfix.

@andrew84 72.0.3815.211 includes fix for another internal issue, but not yet resolves address bar problem.

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

@nintendork07: Thanks for those steps. Reported this internally as DNA-89451