Opera 67.0.3575.31 totally unusable on Windows 10 x64
-
operalinknx1 last edited by
Please revert back to Opera 66
See my link here for solution :https://forums.opera.com/topic/38639/bookmarks-side-panel-broken-on-opera-67-0-3575-31
-
jimmybfmv last edited by jimmybfmv
I had a very similar issue that was caused by open tabs:
Immediately after the update the new version worked fine. Then, after the next restart, Opera would freeze a few seconds after every startup ("not responding"). It would stay unresponsive and I would have to force-close every time.Here's how I fixed that:
- Exit Opera (force-close)
- Back up the file "Current Session" from your profile folder: https://help.opera.com/en/latest/crashes-and-issues/
Alternatively, just back up the whole profile folder (C:\Users[UserName]\AppData\Roaming\Opera Software\Opera Stable). - Delete the file "Current Session" from your profile folder.
- Start Opera. (It should work fine now but your open tabs will be gone.)
- Close Opera.
- Copy your backup of "Current Session" back to your profile folder (replace the new file Opera created automatically).
- Start Opera.
- Success!
If you don't need to keep/restore your open tabs just follow steps 1, 3 & 4.
-
-
radekpilich last edited by
I've noticed that my Android and Windows Operas were not syncing, so I tried to log in in the Windows application and it started freezing again forcing me to go through the downgrade procedure again. Waiting for Opera 68.
-
operalinknx1 last edited by
@radekpilich Same here, I have disabled updates entirely. But what if 68 is also broken? We have no way to know.
-
burnout426 Volunteer last edited by
@operalinknx1 said in Opera 67.0.3575.31 totally unusable on Windows 10 x64:
But what if 68 is also broken? We have no way to know.
Download the Opera stable installer, launch it, click "options", set "install path" to a folder named "Opera Stable Test" on your desktop (or somewhere), set "install for" to "standalone installation", uncheck "import data from default browser" and install.
Keep testing in that Opera now and then and keep checking for updates in it and letting it update. When things are finally fine, you can enable updating with your regular Opera again and update. You can then disable updates in your regular Opera again and always test the next update in the standalone installation before you update your normal Opera. The standalone installation won't interfere with your normal Opera (besides syncing if you enable it and it works and you delete a bookmark or something of course).
-
operalinknx1 last edited by
@burnout426 Hi there, thank you so so much for taking your time to write down the directions. This is really good advice, however there is only one problem. When I launch the browser, I just want to get my work done. Things done like daily tasks and when I am in a hurry to have to get information I need. I don't have the time to mess around with all of this which is why stability and function are so important. I appreciate your advice however, but as of now I do have other more stable browsers (firefox and chromium portable) both of which are getting the job done. I love Opera browser for its unique abilities but at this rate, it is difficult to trust as a reliable solution.
-
windbags last edited by
@jimmybfmv Have same problem, but, sadly, it still froze after about a minute after doing this
-
-
windbags last edited by windbags
How can I go back to 66?
I tried a full Win10 system restore back to February (before the last launcher was written) and, while that was OK, the launcher now didn't launch Opera!
So redid the "download" via OperaSetup and have ended up back with 67 and it freezing after about a minute... -
peterhof last edited by
Re: Opera 67.0.3575.31 totally unusable on Windows 10 x64
Seems that version 67.0.3575.79 is now stable and working as expected -
windbags last edited by
@jimmybfmv said in Opera 67.0.3575.31 totally unusable on Windows 10 x64:
@windbags Have you tried disabling synchronisation?
Struggling to find how to that! (almost 2am!)
-
windbags last edited by
@jimmybfmv said in Opera 67.0.3575.31 totally unusable on Windows 10 x64:
@windbags Have you tried disabling synchronisation?
any help about how to find such welcome!
-
windbags last edited by windbags
@windbags said in Opera 67.0.3575.31 totally unusable on Windows 10 x64:
@jimmybfmv said in Opera 67.0.3575.31 totally unusable on Windows 10 x64:
@windbags Have you tried disabling synchronisation?
any help about how to find such welcome!
Answering my own question:
O-menu-Settings-Synchronisation-Sign out
(even though it was the sign-in that was failing)They seem to have broken the sign in!!
Sad that this had to be posted via Chrome ! :-0
-
burnout426 Volunteer last edited by
@windbags said in Opera 67.0.3575.31 totally unusable on Windows 10 x64:
How can I go back to 66?
You can read through https://www.reddit.com/r/operabrowser/wiki/opera/rollback_version to see if it helps.
-
-
radekpilich last edited by leocg
@peak4 said in Opera 67.0.3575.31 totally unusable on Windows 10 x64:
@AnthG don't know if you're still monitoring this thread.
When I had this problem, I just let Opera " wait for program to respond" rather than "end program"
Be patient, it can take several hours, or even overnight.I Can Confirm This Worked For Me As Well.
[Post edited to remove shouting]
-
linkinpark187 last edited by@windbags, you have to be quick when you do it, but when you open, copy and paste this into a new tab:
opera://settings
From here, go to your search, just type "sign", and the first thing that pops up should be to sign out of your account. It's a pain, but I've found that, for the moment, synchronization is completely broken.
-
jimmybfmv last edited by
@windbags Have you tried peak4's "solution"?
@peak4 said in Opera 67.0.3575.31 totally unusable on Windows 10 x64:
When I had this problem, I just let Opera " wait for program to respond" rather than "end program"
Be patient, it can take several hours, or even overnight.I had sync disabled since the update but I just tried signing in again and it worked for me, too! "Several hours" seems a bit extreme but I did have to wait 5 minutes on a sluggish laptop and 1–2 minutes on a less sluggish desktop PC for Opera to respond again. After that I was logged in and everything had been synced.
-
peak4 last edited by
@jimmybfmv said in Opera 67.0.3575.31 totally unusable on Windows 10 x64:
@windbags Have you tried peak4's "solution"?
@peak4 said in Opera 67.0.3575.31 totally unusable on Windows 10 x64:
When I had this problem, I just let Opera " wait for program to respond" rather than "end program"
Be patient, it can take several hours, or even overnight.I had sync disabled since the update but I just tried signing in again and it worked for me, too! "Several hours" seems a bit extreme but I did have to wait 5 minutes on a sluggish laptop and 1–2 minutes on a less sluggish desktop PC for Opera to respond again. After that I was logged in and everything had been synced.
It may well depend on how many tabs you have open at the time it hung.
For various reasons, and it never normally causes issues, I was probably running with 100+ open at the same time, maybe a lot more.
I've not tried it yet, but the latest version of opera has something called Workspaces available as a plugin or something, which might let me organise things differently.
Bill
