I can't update from version 102
-
burnout426 Volunteer last edited by
@burnout426 There's an update now. Download https://ftp.opera.com/pub/opera/desktop/105.0.4970.16/win/Opera_105.0.4970.16_Setup_x64.exe instead.
-
-
engineerhb last edited by
I am having exactly the same problem (windows 11 latest update). I spend many hours deleting and cleaning all tracks of opera, folders and registries, but unfortunately nothing above 102 seems to work. I tried with 104 and 105 offline installers and they fail, some error related to pak corruption, uninstalling process also fails.
For now the only version that can be installed is 102 and auto update attempts also fail, after each relaunch it remains at 102. -
SectionX27 last edited by
@burnout426 it doesn't work, it will always display the same error message with pak. file, even if you change the file location for the installation. It's been weeks and the problem still persists.
-
burnout426 Volunteer last edited by burnout426
@sectionx27 I can't reproduce it and no one at Opera is able to reproduce it yet (even on Windows 11 23H2). So, not sure what's different about the systems that have the problem and what the cause is even, yet.
-
-
burnout426 Volunteer last edited by
See if the free version of Malwarebytes finds anything. Then, remove what it finds and restart Windows to test if it helps with the pak file corruption.
-
burnout426 Volunteer last edited by
Temporarily create a new account on Windows (local one not tied to a Microsoft account), log into it and test if the pak file corruption issue with the installer happens there too or not.
-
burnout426 Volunteer last edited by
What's everyone running for anti-virus?
Anyone running a system-wide VPN? There's one that can cause issues with Opera. Can't think of the name of it at the moment.
-
burnout426 Volunteer last edited by
Test that the installer is in tact after you download it. See https://www.reddit.com/r/operabrowser/comments/18468wk/comment/kaycxni/?utm_source=reddit&utm_medium=web2x&context=3 for how.
-
-
SectionX27 last edited by SectionX27
@burnout426 No hope, I did flushed my main account, tried a local login for Windows 11, deleted old files from OperaGX, still nothing, 104 can't install and still showing the same error. Only 102 can run atm. I'm tempted to do a full system restore of my Windows 11 back to defaults but then I'll risk deleting some important files and backing up is too time consuming just to fix this browser.
-
engineerhb last edited by
@sectionx27 I hope it doesn't come to that. I am in the same situation and I really don't want to restore or reset windows just for the sake of a browser, even if it means I have to remain on 102 forever or switch to another browser.
A user, rijndael9, introduced herself as an Opera engineer and sent me a message asking for my "opera_autoupdate.log" file. Does anybody have any idea about this user? Is it safe? does the log info contain any security sensitive data?
-
leocg Moderator Volunteer last edited by
@engineerhb Yes, it's safe. Regarding the file, you can open it and see if there are any information that you consider sensitive. Probably it contains data about some directories on your system.
-
-
garzov last edited by
@burnout426 It's the fact that I can't solve it in any other way that leaves me perplexed. Obviously, as an old Mac user, I had to expect something like this on Windows!
-
SectionX27 last edited by
Okay, ya'll listen up. The problem is already fixed. Just update your 2023-11 Cumulative Update Preview for Windows 11 Version 23H2 for x64-based Systems (KB5032288) and this will solve the problem. After restart, OperaGX just update itself and is now on the latest version of the browser.
-
James-joesph last edited by
Uninstall and Reinstall:
If you encounter persistent issues, you might consider uninstalling your current Opera version and then installing the latest version from scratch. -
engineerhb last edited by engineerhb
@sectionx27 The problem is not fixed, I am on this update (KB5032288) and I am still facing the same issue. I didn't have time time to send my log file to Opera, I will do it as soon as I can. I just hope they can use the log data to patch this bug or provide a guide that help us to get out of this situation.
