Qbittorrent Portable Windows Close Application

You shouldn't be letting Windows close it like that. When Windows does so, it generally closes the launcher prior to the app itself, which means the portable settings aren't being handled appropriately on the closing of the app.

If you're wanting Windows to close it, rather than closing it yourself, I recommend installing the app normally, rather than the portable package.

Is your point about QBP or a more general one?

Y'see if it is general (which I think it is) then you're in the wrong sub forum and want the full "how does this PA thing work anyway?"

your choice, Mr Angry

I wanted to clarify quickly how things are working here and why you see the behavior you do. The recommended and supported way to shutdown all our apps running either locally, from a synced cloud drive, or from a portable drive, is to use the PortableApps.com Platform. It can automatically close down all your running portable apps, warn you of any you must close yourself (if they are "minimized" to the system tray) and then either eject or show the Windows shutdown/restart/logoff prompt. All of that happens by just clicking the power button on the PA.c Platform.

If you're running our apps without the PA.c Platform, they should be individually closed before shutting down Windows. The reason for this is that some apps that require it have a launcher sitting alongside the running app, waiting for it to close to move files back and clean up registry entries. Some apps don't require this. Some, like qBittorrent, do. If you shut down Windows without closing the running apps beforehand, Windows will just kill the processes off. This will cause files to be left behind on the local machine in some cases, or files left in the wrong location. When you run the app again the next time, it will alert you to this issue, and attempt perform a cleanup at that point in time.

Due to the way the PortableApps.com Launcher is currently coded, it can't automatically continue on or restart itself after showing you the message about it not properly being shutdown. If it were to restart itself, the state of the Windows environment variables would be mixed up from either the platform or the previous instance. This could cause TEMP files to not be properly cleaned up and similar issues.

In order to prevent Windows from shutting down and killing off the portable processes in the wrong order, we'll need to rewrite a section of the PA.c Launcher to be able to interact with the Windows shutdown API and tell Windows that we are still running and why so it can be displayed to the user. We can't handle this at the platform level as Windows demands that every single process that wants to keep running must interact with the API. This will require a bit of work to make happen that we haven't yet had time to look into.

In order to have the launcher be able to show the message and then continue working will also require a fair amount of coding that we haven't yet had time for.

Finally, the reason some apps like qBittorrent can't be properly closed by Windows or by the PA.c Platform is because, when they are minimized to the system tray, Windows can't send them the proper WM_CLOSE or WM_QUIT messages because they have no active "window" in Windows parlance. Only apps that appear as a window on your screen or an icon/button in your taskbar have an active window to receive such messages. This is why when you click power or eject on the PA.c Platform, it will alert you that a handful of apps are still running and you should close them yourself. Windows doesn't do this and will just unceremoniously kill off the processes in cases like this. So, if they have any changes within the app that haven't been saved (say if an app doesn't save changes you make to Options until you exit the app as opposed to clicking OK in the Options window), those changes will be lost because the app basically crashed.

I hope that clarifies a bit how things work today and will hopefully change in the future.