Can you try to run the Windows build @touwys?

Are you able to locate this build by yourself? See #160 for guidance.

I tried to download the build, via the link, with another account.
I got the 404 error (not found) initially as well. It required you to be signed into GitHub. After I signed in, it worked.

This how to access the Windows build artifacts:

The behavior of the console is configurable:

Do I capture that initial error? Good question. In a way no. If the application cannot be started it's on the OS the handle with that error. Unless the launching mechanism takes care of way of capturing that..

When building background applications, services, we indeed capture this kind of output, by redirecting the console output to a file.

Next is to turn wrap this "runtime image" into an installer which hopefully better integrates it with Windows, or Linux.

It required you to be signed into GitHub. After I signed in, it worked.

Yes, thanks for the reminder.

This how to access the Windows build artifacts:

No video found

The behavior of the console is configurable:
178 noConsole = false

I suppose you are going to keep the default set as "false", for the time being?

Incidentally, I did notice that the app settings were retained from the previous installation — even though I have "cleanly" removed the installation before installing this distribution. This can only mean that the app is not self-contained — yet? Where does it store the settings info?

Here is the DOS-log is you still need it for any reason:

•
listFix_win — DOS_console_log.txt
•

Application settings are always stored in %USERPROFILE%\.listFix(), close to the log files, in the parent folder.

1. .listFix()\history.json
2. .listFix()\mediaLibrary.json
3. .listFix()\options.json

You can open those files with a text editor.

So these are the traces left behind by listFix() independent of the distribution.
I think that is perfectly acceptable. Very few application leave so little behind.