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

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.

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.

@jojo0587 fix for it is ready and should be available in next update. It's related to indexing of tabs not working correctly in chrome.tabs API when workspaces are used.

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.

Hey, we have identified issue with crashloop which is related to recent adblock list update. Next stable update will include fix for this but we have also rolled back adblock list update until client with fix is distributed. If you have adblock enabled then you would have been affected by this issue. To fix this now you can force adblock list update manually but pressing upate button on following pages:

• opera://settings/adBlockerLists
• opera://settings/trackerBlockerLists

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.

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.

This has already been fixed internaly by DNA-123123, unfortunatelly didn't make it into this week release but already backported and will land with next stable update.

@indiqazzz thanks. It's same issue mentioned by @burnout426 above. "Crash loop on start with color theme flag enabled"

@indiqazzz nice finding. Do you have perhaps any reports with CrashID on opera://crashes page?

@indiqazzz: could you check if you have file custom_partner_content.json in your profile directory?

Hey, we have identified issue with crashloop which is related to recent adblock list update. Next stable update will include fix for this but we have also rolled back adblock list update until client with fix is distributed. If you have adblock enabled then you would have been affected by this issue. To fix this now you can force adblock list update manually but pressing upate button on following pages:

• opera://settings/adBlockerLists
• opera://settings/trackerBlockerLists

@bigone201 102.0 is still available to be downloaded manually from ftp or www.opera.com page. Issue has no effect on new users so there is no need for us to stop distribution of this version. How Kaspersky handles it is question to them and not Opera.

@paul-durham thanks, that's what we suspect. Migration should be atomic operation so it shouldn't be possible to start Opera while it wasn't finished. We are currently trying to reproduce it with fake profile with size around 100GB. Working also on some other solution for profile migration.

@simonov-89 that's why update is fully disabled.

Stable builds are rolled out gradually, usually on first day only users who update manually get new version. So generally those that download build from opera.com and install it or those that visit opera:about page to trigger update.

Issue with migration didn't affect all users and we are still not sure what triggers such situation. We haven't been able to reproduce it internally.

@simonov-89 migration to 102.0 profile copies files and nothing is deleted. So downgrade work, so does copying all files from root profile dir to Defaults folder inside profile also works.

We have currently disabled option to update to version 102 due to profile migration mechanism not working in some cases. It's still possible to manually download and install update.

@burnout426 mentioned earlier steps to finish migration manully. This is one time process and we are still investigating what could be causing issue.