Opera Update Defaults to User Profile Only - Issues with Defender ASR Org-Wide
-
fatguy1121 last edited by
We've been trying to deploy Opera as our organization's default browser, however upon installing an update rather than staying installed to C:\Program Files\Opera it's instead defaulting to C:\Users\user.name\AppData\Local\Programs\Opera
When this happens, it makes it impossible to create a Defender ASR Rule to allow Outlook to Open Opera.exe because the user path is a wildcard. This is required to allow links in Outlook to open in Opera With Defender. Because the profile is not and was not configured to ever be installed per-user, it should respect that it was installed per-machine, why would the updater do otherwise?
-
burnout426 Volunteer last edited by burnout426
@fatguy1121 said in Opera Update Defaults to User Profile Only - Issues with Defender ASR Org-Wide:
however upon installing an update
How are you installing the updates?
Are you using the command-line options for the installer?
-
fatguy1121 last edited by fatguy1121
@burnout426 No, it just does its own auto updates. Initial installation is done with an installer with manual config Per-Machine I start with the full offline installer for version version 112.0.5197.35, then it does it's own updates thereafter.
installation_status.json clearly states _all_users":true
{"_all_users":true,"_launch_from_install_dir":true,"_skip_launcher":true,"_subfolder":"112.0.5197.35","app_id":"1691177590","channel":"Stable","copy_only":false,"files":["112.0.5197.35.manifest","MEIPreload\\manifest.json","MEIPreload\\preloaded_data.pb","d3dcompiler_47.dll","dxcompiler.dll","dxil.dll","headless_command_resources.pak", -
burnout426 Volunteer last edited by
Hmm, in the Windows Task Scheduler for each machine, what's it say for the "Action" tab command for the "Opera scheduled autoupdate" task? Does it say:
C:\Program Files\Opera\autoupdate\opera_autoupdate.exe --scheduled-task --bypasslauncher $(Arg0)or something else?
In installation_status.json, do you have
"path":"C:\\Program Files\\Opera"in there? -
fatguy1121 last edited by
@burnout426 https://pastebin.com/HHWtHxcF for the full Install Status
It looks like there are two scheduled autoupdate tasks one for the user and one for program files installation. The one in Program Files includes C:\Program Files\Opera\autoupdate\opera_autoupdate.exe --scheduled-task --bypasslauncher $(Arg0)
The one for the user profile includes C:\Users\user.name\AppData\Local\Programs\Opera\autoupdate\opera_autoupdate.exe --scheduledtask --bypasslauncher $(Arg0)
Is it possible that the users themselves somehow ran another installer? or maybe selected an update prompt in opera that triggered it to do it's own thing?
-
burnout426 Volunteer last edited by
@fatguy1121 said in Opera Update Defaults to User Profile Only - Issues with Defender ASR Org-Wide:
Is it possible that the users themselves somehow ran another installer? or maybe selected an update prompt in opera that triggered it to do it's own thing?
While the former is possible, it sounds more like the latter, but don't know. For the "C:\Users"... update task, on the general tab, does it say SYSTEM for "When running this task, use the following account" or does it say the user's name?
