After W10 update Vivaldi cannot update:
-
After W10 update Vivaldi cannot update:
"The installer couldn't create a temporary directory. Please check for free disk space and permission to install software."
Vivaldi did not cause the problem, but I imagine you will have to deal with it?
Meanwhile, how can I deal with permissions to install software?Thanks!! [Yours is my main browser -
you are Good!] -
@lexoverrex Have you tried running Vivaldi as admin ? Where is Vivaldi installed ? Which type of installation (standalone, per user, ..)
-
Is there a summary of expected behavior for this error without running as admin, which of course, we should never have to do?
What I've found:
-
If Vivaldi is installed normally, and to the normal location (Program Files), Vivaldi has no problem updating itself, since the UAC prompt triggers.
-
If Vivaldi is in standalone mode and in a location, for example, like c:\vivaldi (i.e. not in either Program Files structure, which are protected areas), there's also no problem. I don't recall if it even needs UAC in this case; probably not.
-
If, however, Vivaldi is in standalone mode and in Program Files (e.g. Program Files\VivaldiStandalone), then when Vivaldi attempts to update itself you will see the above error--unless you run as admin.
That seems to me to be a problem, since if Vivaldi can trigger UAC in example #1, it should also be able to do it in example #3. Right? Standalone mode shouldn't preclude that.
-
-
@Gwen-Dragon Yes, that seems to be the case, though it's difficult reconciling how it is that Vivaldi's updater has no problem working in the same area if it's not a standalone install. How could that possibly make any difference to it?
-
@rseiler said in After W10 update Vivaldi cannot update::
@Gwen-Dragon Yes, that seems to be the case, though it's difficult reconciling how it is that Vivaldi's updater has no problem working in the same area if it's not a standalone install. How could that possibly make any difference to it?
Perhaps because installing Vivaldi 'normally' into Program Files toggles Windows installation actions that create registry keys and subfolders involving UAC protected access to the Program Files folder. Whereas a typical standalone install, in not being intended to be installed into Program Files, doesn't create the registry keys involving protected access, so it doesn't need the admin-level keys and access - but does trigger a Windows' error message if user installation into Program Files is attempted (which is normal Windows installation blocking unless a user alters the main protection/access levels for the Program Files folder).
-
@Blackbird Yes, must be one or more of those things which distinguishes the two. Interesting.
-