As qBittorrentPortable.ini shows, qBittorent Portable is all over the registry and app data folders, not to mention a whole custom code in custom.nsh.
That's a lot of writes which are not needed since qBittorent has an official portable mode which can also be achieved with a command line parameter and/or an environmental variable (see both here). It's also mentioned here.
So there are 3 ways to activate portable mode, why not using any of them?
In addition, it includes in vain a folder called $PLUGINDIR.
This might also apply to qBittorrent Enhanced Portable, and might solve issues like this and that.
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
there are many levels of portability.
john makes real portable apps.
if he would use it it would be not full portable.
that's what i figured out.
the settings problem is not only here.
i have a port app from developer, same problem.
i help out but get ignored and bullied here.
hopefully i'm not making very bad at the moment.
we need here slowly a not mobing hint.
edit:
one can get here mental problems, don't let get bullied.
fight against bulling!
i help where i can! help each other! be nice!
qBittorrent Portable Enhanced has used the -profile command line switch from the beginning. qBittorrent Portable does as of a recent release. That doesn't make qBittorrent fully portable though.
You're welcome to use the standard ZIP version from the publisher with the PA.c Platform if you want to directly associate it with files, you just lose out on automatic updates and stuff.
Sometimes, the impossible can become possible, if you're awesome!