Ok, you know I’m long on your side, and also, I had thought all this was long taken care of. But…
first point. As anyone sensible to security risks will, and by Microsoft recommendation for a decade, I’m running as a non-admin user in Windows 10. I go admin as needed, just as you do in *nix/nux.
Then. I long ago discombobulated Beta installs so that they don’t go to Documents, but were installed correctly from the base 64-bit installer, in C:\Programs Files . Fine.
So, 22.214.171.124 arrives. First point is that Scrivener itself doesn’t tell me anything about an available update. Each time, I’ve had to also run Check for Updates to see it, and this is consistent on later runs of Scrivener since I’m not yet updated.
I downloaded the updater directly from the link in the still-mis-titled parked message above. Running this tries to install Scrivener in my Documents folder. No thank you, and why doesn’t it hint that maybe you want to install as Admin to send it to the right place??
So, I decide to use the in-program updater after all. This in turn crashes out, telling me it can’t write in C:\Program Files.
Now, you know I’m very able to and will fix this (run the installer as Admin).
What can save you a lot of grief for new Beta testers, and for your eventual release, is to straighten up this picture, no?
So it hangs properly, the various ways, yes… ?
A smile, and a gentle enough chide, I will hope,
p,s, Also could ask about this business of putting executables in Documents – isn’t the usual practice these days for determinedly non-admin installs to use AppData/Roaming, or the like?