• Login
    • Search
    • Categories
    • Recent
    • Tags
    • Users
    • Groups
    • Rules
    • Help

    Do more on the web, with a fast and secure browser!

    Download Opera browser with:

    • built-in ad blocker
    • battery saver
    • free VPN
    Download Opera

    identifying argument passed to opera_autoupdate.exe

    General
    2
    2
    92
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • clbylt
      clbylt last edited by

      I'm trying to identify the value of the argument $(Arg0) in the following command:

      C:\Users\opera1\AppData\Local\Programs\Opera\autoupdate\opera_autoupdate.exe" --scheduledtask --bypasslauncher $(Arg0)

      Command is happening on a Windows 11 machine when starting Opera. Command is being halted by antivirus.

      Just curious about that argument without disabling AV.

      Thank you for any guidance.

      Reply Quote 0
        1 Reply Last reply
      • Moved from Opera for Windows by  leocg leocg 
      • burnout426
        burnout426 Volunteer last edited by

        You can open up the Windows Event Viewer and under "Applications and Services\Microsoft\Windows\TaskScheduler", you can right-click on "Operational" and choose "Enable log". That will enabling logging of tasks. Then, when Opera's tasks run, you should see log entries in there under "Operational" (you might have to refresh or retstart the Event Viewer). You should also see the entries on the "History" tab in the properties for the Opera task in the Windows Task Scheduler.

        In the log (on the General and Details tabs), you can look to see what it says. If it says just the path to opera_autoupdate.exe, then Arg0 is empty. Otherwise, it should show what Arg0 was replaced with by Opera.

        However, in my case, I don't see Arg0 being used (whether the task starts via Windows or when Opera starts and runs the tasks).

        When you're done testing, best to right-click "Operational" and clear the log and then right-click it again and choose "disable log" so you don't have a log file building up in size.

        Reply Quote 0
          1 Reply Last reply
        • First post
          Last post

        Computer browsers

        • Opera for Windows
        • Opera for Mac
        • Opera for Linux
        • Opera beta version
        • Opera USB

        Mobile browsers

        • Opera for Android
        • Opera Mini
        • Opera Touch
        • Opera for basic phones

        • Add-ons
        • Opera account
        • Wallpapers
        • Opera Ads

        • Help & support
        • Opera blogs
        • Opera forums
        • Dev.Opera

        • Security
        • Privacy
        • Cookies Policy
        • EULA
        • Terms of Service

        • About Opera
        • Press info
        • Jobs
        • Investors
        • Become a partner
        • Contact us

        Follow Opera

        • Opera - Facebook
        • Opera - Twitter
        • Opera - YouTube
        • Opera - LinkedIn
        • Opera - Instagram

        © Opera Software 1995-