|
From: | John Donoghue |
Subject: | [Octave-bug-tracker] [bug #58320] [mxe-octave] Add ability to specify a local or allusers install from the installer |
Date: | Fri, 15 May 2020 10:18:47 -0400 (EDT) |
User-agent: | Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/64.0.3282.140 Safari/537.36 Edge/18.17763 |
Follow-up Comment #18, bug #58320 (project octave): Ok after lots more poking around and reading I found a couple of things. 1. Even though it installs the local installation, if there is an all user one - thats what you will see - rather than the 2 different installs. I can fix that by appending (Local) to the uninstall registry keys. 2. There is apparently a bug discussed on a few different sites that there is a bug in windows 10 control panel / add remove programs that always forces the uninstall to prompt for admin user credentials. One of the issues at that point is then the installer is running at elevated status and so the local registry is the admin users rather than the user who installed it. It seems the way to solve is to catch the fact that the elevated user isn't the user who started the uninstall and rerun the uninstall from the uninstall in a non elevated state. The issue doesnt occur when running the uninstall from outside of add/remove programs. So, I try adding that. _______________________________________________________ Reply to this item at: <https://savannah.gnu.org/bugs/?58320> _______________________________________________ Message sent via Savannah https://savannah.gnu.org/
[Prev in Thread] | Current Thread | [Next in Thread] |