Opera 29 - update check takes forever
-
sparrow93 last edited by
Reported this as a bug. davehawley, do You have Opera 29 Stable on Windows XP ? Because You mentioned this issue in Opera Developer, which I find probable as it is still experimental edition. What is bothering me is that why does this checking update error happen in Stable edition?
-
A Former User last edited by
I reported it as a bug in Opera Developer 30, it worked for me in Developer 29.
Why it shouldn't work on 29 Stable is a bit of a mystery!
I don't have Stable 29 installed, only the latest Developer 30.
-
Deleted User last edited by
Hi,
I also keep getting the same message when trying to install an update from Opera and keeps popping on my screen 'Please click yes or no to update Opera' and when I click 'Yes' it then does something and then I get"An error occurred while checking for updates" 'close' and then pop up again when I reload Opera.
I am using windows 8.1 and need a resolution for this as I may need to remove Opera completely and revert back to IE or another Platform, this has been ongoing for sometime and getting rather tedious now. I have uninstalled Opera and reinstalled again and this has no effect, in fact it messes my programs up and I have to go back to settings so I can then then see clips and films as this comes up as cookies and Java issues.
any help and solutions would be appreciated and thank you in advance for any help.
Mark -
Deleted User last edited by
Oh,
this is what I am using if this helps:-
Version: 28.0.1750.48 - Restart Opera to update to version 28.0.1750.51 Update stream: Stable System: Windows 8.1 64-bit (WoW64) -
sparrow93 last edited by
Thanks for the answers, I hope that the next update will fix this as I don't know how to solve this issue .
-
donq last edited by
You can't solve this issue currently - opera_autoupdater.exe is linked to one windows kernel function, which is not present in XP (and windows can't run updater exe this way). I too hope that opera dev team will fix this issue in future
-
A Former User last edited by
That's not the cause of the problem on my system.
It's a standalone "USB" install and opera_autoupdater.exe does not exist on my system at all, and never has.
-
Deleted User last edited by
Pretty interesting,
Thanks guys, may need to get another Browser as I cant have this on a pop up any longer, its driving me mad, or madder lol
cheers -
A Former User last edited by
I can confirm that it's fixed for me in the latest update today to developer 31.0.1857.0.
:yes: -
A Former User last edited by
why do you people keep expecting miracles when using an EOL OS like XP just upgrade to windows 8.1 already is there some specific reason you absolutely need to run an EOL OS
-
lando242 last edited by
Probably because their PCs are old enough to vote in the upcoming elections.
-
A Former User last edited by
actually 8.1 will run quite happily on any win XP box that has reasonable specs ie: intel P4 2.06GHz and 1GB of ram it's just not as piggy as vista or 7 (Vista being the most piggy of the two)
-
A Former User last edited by
Whether people should still be running obsolete operating systems or not is irrelevant.
The fact is that Opera still state that they support Windows XP, and that being the case, Opera should work properly with it.
There are still a massive number of PCs in the world running XP, whether Microsoft or anyone else like it or not!
-
sparrow93 last edited by
Thanks for the heads-up :). I just hope that next stable release will solve this problem.
-
Deleted User last edited by
why do you people keep expecting miracles when using an EOL OS like XP just upgrade to windows 8.1 already is there some specific reason you absolutely need to run an EOL OS
My pc is a brand new windows 8.1 pc, I installed Opera to get away IE and Google chrome, never had any issues with Opera except now when there is a message stating "An error occurred while checking for updates"
so please change your wording Mr davehawleyhas anyone else got any ideas to rectify this issue yet?
Thanks
-
A Former User last edited by
It's fixed, and was supposedly a problem that only affected XP, as leocg has already pointed out.
Why exactly should I "change my wording" BTW?