I have PortableApps platform installed. It is configured to check for updates on launch, which I do manually.
Most apps seem to behave well, except qBittorrent. Today I was told that v 4.3.3 was available (my existing version is 4.3.1). When I instructed it to update, it went through the motions and said 'update was complete'. When I examined the version running, it still said 4.3.1.
Normally qBittorent starts automatically with Windows. Could this be the problem - that the PortableApps update sequence does not first shut down the existing app before updating it? If so, why does it (incorrectly) claim that the update was successful?
(I am not sure if this is a bug, or a 'feature'.)
Visit the Community page
Join our forums
Subscribe to our email newsletter
Subscribe with RSS
Follow us on BlueSky
Follow us on Facebook
Follow us on LinkedIn
Follow us on Mastodon
You'll need to reinstall it over itself.
If you have qBittorrent starting automatically with Windows, it's starting in non-portable mode.
Sometimes, the impossible can become possible, if you're awesome!
Clarification: Before I installed qBittorrent with PortableApp, I had a (stand-alone) *portable* version running on Win 10. That was the version running on Windows start-up. Since installing qBittorrent on PortableApps, I have *deleted* the original (stand-alone) qBittorrent.
How could qBittorrent be starting in non-portable mode, in either scenario?
If you set a packaged app to start with Windows, it sets itself directly to start, bypassing the portable launcher and running in local mode.
Sometimes, the impossible can become possible, if you're awesome!