A different update issue
#11
Posted 29 January 2017 - 02:31 PM
#12
Posted 29 January 2017 - 02:39 PM
Edit: in my case i just redownloaded the main installer again for V1.2 and it has been updated to version 1.2.3766 so in my case things should be OK now as that version is sup[posed to fix the updating problem, My testing version has worked fine also since passing Ver X3766 and is currently on Ver X3370
#13
Posted 29 January 2017 - 05:58 PM
#14
Posted 29 January 2017 - 07:32 PM
#15
Posted 29 January 2017 - 08:18 PM
#16
Posted 30 January 2017 - 06:39 AM
#17
Posted 31 January 2017 - 12:24 PM
Fleegle411, on 28 January 2017 - 05:31 PM, said:
anewerror.jpg
This is coming off a fresh install from the 1.2 installer, going up to 3770 and the folder this installation is in is excluded by my AV.
Hmm, do you remember if there was a shield icon next to the update button and whether you got asked to elevate the updater? Nothing's changed in this case from 1.1 to 1.2 AFAIK, but it seems the only plausible reasons for the error is that the updater thought it didn't need to elevate, or anti-virus is screwing something up.
Jovet, on 30 January 2017 - 06:39 AM, said:
Not especially, because that would require every non-administrator install (typical for Testing and Unstable users) to elevate for no reason. This code works, as evidenced by all the updates that do happen (including on my machine), and like I said above, I am pretty sure the elevation code hasn't changed since before 1.1: it checks whether the current user (the one running the menu) can write to the application path (it tries to create a test directory), and if that fails and you're not elevated already, it will elevate the updater.
Jovet, on 30 January 2017 - 06:39 AM, said:
I am thinking that it may be useful to try and augment every exception with the directory or file involved, at least. It's a pain though, because it means wrapping every disk operation in a try/catch/throw block.
#18
Posted 31 January 2017 - 08:15 PM
James Ross, on 31 January 2017 - 12:24 PM, said:
While I am not certain, I do not believe there was a shield next to the update option on the menu, and when I clicked it the updater got straight to work, no asking "Do you want to elevate" or anything of the sort.
#19
Posted 01 February 2017 - 12:33 PM
Fleegle411, on 31 January 2017 - 08:15 PM, said:
Is the program in Program Files or another protected directory? If not, then I would not expect the shield/elevation nor the error.