As app-namePortable.exe is supposedly only a launcher, why don't we terminate it after launching.
New: NAPS2 (Feb 24, 2025), Platform 29.5.3 (Jun 27, 2024)
1,100+ portable packages, 1.1 billion downloads
No Ads!, Please donate today
New: NAPS2 (Feb 24, 2025), Platform 29.5.3 (Jun 27, 2024)
1,100+ portable packages, 1.1 billion downloads
No Ads!, Please donate today
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
Follow us on Twitter
It also cleans up after the app-namePortable.exe finishes running.
neutron1132 (at) usa (dot) com
Ok. Thanks for this.
Just because the scientists didn't prove it; doesn't mean that I am wrong !!!
You shouldn't really kill the process since, it backs up settings on the host computer, and puts the portable app's settings on the host. If you kill the the launcher, then you will leave your settings on the computer you used and worse, you will lose your settings and the local installation's settings as well.
If you have an already-portable Portable App, then you don't have to worry about leaving data on the host, but you will still lose any new changes.
So whenever a program is not responding, kill the base app not the launcher (like firefox.exe not FirefoxPortable.exe), because the launcher will still clean up the app, and restore any local settings even if the internal app is terminated.