Can't update Vivaldi since 1.3.551.17



  • When I tried to update to both .21 and .27, installation failed with "The installer couldn't create a temporary directory". I have restarted Windows already. Windows 10 1611 x64, Vivaldi 32-bit.


  • Moderator

    @tigas:

    When I tried to update to both .21 and .27, installation failed with "The installer couldn't create a temporary directory". I have restarted Windows already. Windows 10 1611 x64, Vivaldi 32-bit.

    Did you try with elevated privileges?



  • How do I elevate privileges when I'm using "Help/Check for updates" and the installer doesn't throw a UAC prompt to put a password?



  • @tigas:

    How do I elevate privileges when I'm using "Help/Check for updates" and the installer doesn't throw a UAC prompt to put a password?

    You can do a right click on the downloaded file and open it with administrator rights (an option in the context menu).



  • I repeat:

    This is the autoupdater built-in to Vivaldi and as far as I can see, the file is downloaded to a temp folder somewhere that I don't know, and the installer is supposed to run with the correct privileges or detect that it needs more privileges and show a UAC prompt for me to input the necessary credentials.

    I will manually update to 1.3.551.28, which is supposed to be the same build as 1.3 Final, but I'm sure that as soon as Vivaldi releases a new snapshot this will happen again.

    The auto-updater is BROKEN for me. If Vivaldi detects a new build and offers to auto-update, I expect it to work.


  • Moderator

    File a bug https://vivaldi.com/bugreport.html

    You are the third person I've seen mention this same problem (I don't know if the developers will be able to replicate it), but I don't recall specifically seeing a bug filed for it.

    For now, I would recommend you back up your profile, uninstall Vivaldi, remove its file directory, and install it afresh.



  • I seem to remember a similar problem reported when the (Windows Path) field was using Cyrillic (Russian) characters e.g. in UserName.
    Could this be a problem with all non-Roman characters?



  • Well, I was going to poopoo that suggestion, but in fact, I do have a non-ASCII character in my Windows' profile folder (=username). Maybe there is a connection…

    Thank you, I'll wait to see if the next snapshot also fails and then file a bug if necessary.



  • Quick check would be to download and install as a standalone version (advanced option) in a folder which only has ASCII chars in the path.
    If that works, then it would appear that you have encountered a bug and should report it
    Go to https://vivaldi.com/bugreport and give full details
    You will receive a reply email with the bug number VB-xxxx
    and you can then reply to that with a link to this thread.

    However, the bug tracker is only available to Vivaldi and insiders, it is not publicly available. So the only way to know it has been solved is to check each Changelog as it appears.



  • I've just noticed that there's a new build of Vivaldi available. I've created a new user with only ASCII letters on the username and will try to update to 1.3.551.37 from the regular account (to see if it still gives the error) and then from the new account (to see if it solves this).

    If the account with only ASCII letters in the username allows updating, I'll file a bug. I'll update in a few hours.



  • Auto-updating from 1.3.551.28 to 1.3.551.37 from "Help/Check for updates" worked perfectly. Maybe some folder got locked into Read-Only by Windows and a reboot cleared the lock in the meantime?


Log in to reply
 

Looks like your connection to Vivaldi Forum was lost, please wait while we try to reconnect.