[BUG] Opera won't check for updates - invalid params and unable to prepare update checker runtime
-
leocg Moderator Volunteer last edited by
@no-name-opera Maybe something is blocking Opera's autoupdater?
-
no-name-opera last edited by
@leocg That might be true but my challenge is how to troubleshoot what is blocking. Is there any command (in Windows) or startup flag that can generate a complete log of what it's trying to do and where it's getting rejected?
-
leocg Moderator Volunteer last edited by
@no-name-opera Try disabling antivirus, firewalls and related software.
-
-
no-name-opera last edited by
I doubt this will help troubleshoot but, when I updated to 66.0.3515.44, I see this in the debug log:
[0123/100111.306:WARNING:minidump_to_upload_parameters.cc(67)] duplicate annotation name prod, discarding value OperaDesktop [0123/100111.306:WARNING:minidump_to_upload_parameters.cc(67)] duplicate annotation name ver, discarding value 66.0.3515.36 [0123/100111.307:WARNING:minidump_to_upload_parameters.cc(67)] duplicate annotation name channel, discarding value Stable [0123/100111.307:WARNING:minidump_to_upload_parameters.cc(67)] duplicate annotation name ptype, discarding value renderer [0123/100113.650:WARNING:minidump_to_upload_parameters.cc(67)] duplicate annotation name prod, discarding value OperaDesktop [0123/100113.650:WARNING:minidump_to_upload_parameters.cc(67)] duplicate annotation name ver, discarding value 66.0.3515.36 [0123/100113.654:WARNING:minidump_to_upload_parameters.cc(67)] duplicate annotation name channel, discarding value Stable [0123/100113.654:WARNING:minidump_to_upload_parameters.cc(67)] duplicate annotation name ptype, discarding value renderer -
zalex108 last edited byTry Fiddler app, once the blocked URLs / IPs appear, search them on HOSTS file, router blocking tab, change DNS...
--
"Off topic Tip"
Follow the Signature's BackUp | Reset link.
Take the opportunity to start a Backup plan, even create a Template Profile.
Windows 7 (x64)
Opera Test profile | Opera Back up | Reset"You cannot know the meaning of your life until you are connected to the power that created you". 路 Shri Mataji Nirmala Devi
-
no-name-opera last edited by
@zalex108 Well, isn't that a neat little tool. Thanks for the suggestion. However, it doesn't show any errors - HTTP 200 across the board, including http://autoupdate.geo.opera.com:443 (which, I assume, is the auto-updater pinging) and http://extension-updates.opera.com:443. What's confusing is that these use http as the scheme but go over port 443 (secure). I'm sure there's a reason but that's the only noticeable oddity. Other thoughts?
-
zalex108 last edited by
I don't know.
Try pinging them.
If they showed as non blocked should respond then is quite extrange.
"You cannot know the meaning of your life until you are connected to the power that created you". 路 Shri Mataji Nirmala Devi
-
no-name-opera last edited by
@zalex108 Here are the results:
PS C:\> Test-NetConnection autoupdate.geo.opera.com ComputerName : autoupdate.geo.opera.com RemoteAddress : 37.228.108.132 InterfaceAlias : Wi-Fi SourceAddress : 192.168.1.9 PingSucceeded : True PingReplyDetails (RTT) : 38 ms PS C:\> Test-NetConnection autoupdate.geo.opera.com -port 443 ComputerName : autoupdate.geo.opera.com RemoteAddress : 37.228.108.132 RemotePort : 443 InterfaceAlias : Wi-Fi SourceAddress : 192.168.1.9 TcpTestSucceeded : True PS C:\> Test-NetConnection http://autoupdate.geo.opera.com -port 443 WARNING: Name resolution of http://autoupdate.geo.opera.com failed ComputerName : http://autoupdate.geo.opera.com RemoteAddress : InterfaceAlias : SourceAddress : PingSucceeded : False PS C:\> Test-NetConnection http://autoupdate.geo.opera.com WARNING: Name resolution of http://autoupdate.geo.opera.com failed ComputerName : http://autoupdate.geo.opera.com RemoteAddress : InterfaceAlias : SourceAddress : PingSucceeded : False PS C:\> Test-NetConnection https://autoupdate.geo.opera.com -port 443 WARNING: Name resolution of https://autoupdate.geo.opera.com failed ComputerName : https://autoupdate.geo.opera.com RemoteAddress : InterfaceAlias : SourceAddress : PingSucceeded : False -
leocg Moderator Volunteer last edited by
@no-name-opera Is your connection set as limited by chance?
-
no-name-opera last edited by no-name-opera
@leocg I'm sorry but I don't understand the question. I'm not aware of any setting in Opera to limit the connection (and I just did a search to check). And I've tried the update with VPN both on and off. If you're referring to Windows overall, no, I don't have any limits set (as far as I know) and have more than ample connection speed. Can you be more specific please?
-
zalex108 last edited by
Do you have a custom Hosts file or DNS?
Try disabling the Hosts file and with Google DNS 8.8.8.8 or Open 1.1.1.1.
"You cannot know the meaning of your life until you are connected to the power that created you". 路 Shri Mataji Nirmala Devi
-
no-name-opera last edited by
@zalex108 I had a custom Hosts file to block much of Microsoft's crap tracking but just got rid of it and also tried Google DNS. Same problem.
-
A Former User last edited by
@no-name-opera Google 's dns was act 'n up earlier..
open dns is work 'n
208.67.222.222
208.67.220.220 -
-
A Former User last edited by A Former User
@no-name-opera Log Name: System
Source: Microsoft-Windows-DNS-Client
Date: 9/29/2019 2:00:19 PM
Event ID: 1014
Task Category: (1014)
Level: Warning
Keywords: (268435456)
User: NETWORK SERVICE
Computer:
Description:
Name resolution for the name translate.google.com timed out after none of the configured DNS servers responded.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">so i switched to a different Dns today..
-
-
no-name-opera last edited by
@leocg Thanks for the clarification - no, I don't have any limits set on Windows. Is there some specific setting you suspect? I'll be happy to check it.
-
A Former User last edited by A Former User
@no-name-opera i see your ealier pings didint work..
have ya done a Command prompt random ping (to n e where) to make sure the ping 'n part works..
-
no-name-opera last edited by
@nvmjustagirl Actually, some of the pings did work, which you can see in the post - I included the pings that didn't in case that lent any clues.
