14February2013
I would like to submit/say - for what it is worth -
that "portable" apps should NOT write to registry!
Writing to the registry defeats the whole purpose/design of "portable" apps!
How many PA.com "portable" apps (now) write to the registry?
Does anyone have any idea?
Far too many PA.com apps (now) write to the registry - in my opinion.
PA.com should flag/point-out/specify apps that write to the registry!
I have been using PA.com µTorrent for years.
I download/"install" the µT PAF to a temp directory on my f drive,
then copy the files to the actual portable/"install" directory on my c drive,
and also then copy the files to my other laptops.
µTorrent (3.3.0.29082) now writes to the registry that it has been "installed"
and µTorrent shows up in my Windows list of installed software!
I guess µTorrent is (now) configured to write to the regsitry
when executed/launched? THAT IS RIDICULOUS!
If it writes to the registry and leaves an entry there, that should be filed as a bug. None of our apps do that that I have seen. A simple bug report would suffice instead of a sky-is-falling post complete with screaming-in-caps-closing.
Lots of portable apps write to the registry temporarily which is then removed on exit. Likely including the browser you used to write this very post.
Sometimes, the impossible can become possible, if you're awesome!
WOW!
Maybe oversensitivity to fault finding produced
such a distorted, blow-it-all out of proportion reply?
"If it writes to the registry and leaves an entry there,
that should be filed as a bug.
None of our apps do that that I have seen."
µTorrent (now) does (like I "said").
"Lots of portable apps write to the registry temporarily
which is then removed on exit.
Likely including the browser you used to write this very post."
This pronouncement/deduction is not correct either ...
LIGHTEN UP!
Which browser are you using?
Previously known as kAlug.
Please re-read your original post and reconsider if it is in proportion to a simple bug in a single app. Essentially, instead of a simple bug report, aka ("I noticed that uTorrent Portable 3.3 left an entry in the Uninstall registry key whereas uTorrent Portable 3.2 did not") you decided to go off on a rant complete with incorrect assumptions, screaming in caps, exclamations points, etc.
"that "portable" apps should NOT write to registry!"
"Far too many PA.com apps (now) write to the registry - in my opinion."
"PA.com should flag/point-out/specify apps that write to the registry!"
"THAT IS RIDICULOUS!", etc, etc)
When called on it, you got upset complete with more screaming in caps and exclamation points. Please consider taking it down a few notches and just stick with the facts. No exclamation points OR SCREAMING IN CAPS!!! are necessary
I've confirmed that uTorrent Portable 3.2 does have a bug with leaving behind 3 registry keys. The change occurred in uTorrent itself and was missed in testing, likely because uTorrent has been getting more buggy in portable form due to internal changes. To stop those keys being left behind, the uTorrentPortable.ini file within uTorrentPortable\App\AppInfo\Launcher must be updated to:
That will fix the issue with the 3 new registry keys including the Uninstall key.
Unfortunately, uTorrent now has other issues as it unceremoniously dropped all support for relative paths. See here for a workaround:
https://portableapps.com/news/2013-02-08--utorrent-portable-3.3.0.29082-...
Sometimes, the impossible can become possible, if you're awesome!
I found a simpler solution to be to modify 1 of my "Persistent" AHK scripts
to check for µTorrent registry entries & to delete them if/when they exist ...
I also use similar scripting in other non-PERSISTENT AHK scripts ...
PS: To post the/my script/code I had to use the "PRE" tag instead of the "CODE" tag
because the "CODE" tag did not keep the indentations ...