There's an issue with the app installer/updater and how it uses temporary directories on C: to save the installers and run them. Is there a way to change what directory is used?
with more detail:
-The updater/installer downloads all of the app files to a temp directory and then attempts to execute them. Not everyone has permission to execute out of temporary directory's so for those like me, the installer/updater simply fails.
I've noticed the only way that it works properly is when I run it as admin (which I don't wish to do as I'm not exactly suppose to..). I'm wondering if there's a way to change what directory the installer/updater saves the installers. and i was also wondering if the next version could have an option to change the directory if there is none available already.
Visit the Community page
Join our forums
Subscribe to our email newsletter
Subscribe with RSS
Follow us on Facebook
Follow us on LinkedIn
Follow us on Twitter
Follow us on Mastodon
Follow us on BlueSky
We'll be adding the ability to specify a specific directory (like one on the drive) eventually. Not being able to execute from TEMP is not a standard security precaution (it will break all kinds of installers) and it's one I've never seen before. So you must be on a very locked down PC.
Sometimes, the impossible can become possible, if you're awesome!
yeah, it's pretty locked down with a heavy group policy, (or at least was/is suppose to be :P) but no, installers don't run from TEMP or anything of the sort, they execute from where they are, and store any "hold" data there.
In all my years of programming, software engineering, and IT.. totally just lost my train of thought..
o.o
+~DESTECTS INC.~+
Actually, a huge percentage (majority, I believe) of installers are done via NSIS including popular apps like Firefox. They all keep DLLs like NSIS plugins and other binary code within TEMP and run them from there from a unique ns?????.tmp folder. As do installers that download and run things (many 'online' installers) and installers that download portions of their bits to install (Chrome, Java, etc).
Additionally, we're not talking about running from there. The error referenced in the other thread that this discussion branched off of occurs when you don't even have the ability to write to TEMP, which breaks nearly all installers and all kinds of apps.
Sometimes, the impossible can become possible, if you're awesome!
Stupidly I didn't realize till now that the platform and everything is open source >.>
I'ma go ahead and fix it for me
+~DESTECTS INC.~+