Apart from Configure.exe which works, the other executables start for a second and close

Describe the bug
Configure.exe works as expected and upon pressing 'Save and run' it closes. Main.exe and theme-editor.exe open for a split second and close.
According to troubleshooting page:
I've watched log.log but the only thing that appears every time is "[INFO] Loading theme AMD from res\themes\AMD\theme.yaml".
Running from powershell doesn't log anything in the terminal and doesn't change anything in log.log.
I took a look at Windows events and nothing shows up, except for a privileged session when starting main.exe as admin.
Tried with LibreHardwareMonitor/python libraries/automatic with the same outcome.
Tried both installer and portable releases.
No antivirus running.

Is there a way to run the exe's in a verbose/debug mode?

To Reproduce
Steps to reproduce the behavior:

1. Double click configure.exe.
2. Pick corresponding display.
3. Press Save and run.
4. Nothing appears to happen.

Expected behavior
Executable should launch main.exe and display info on the connected display.
Theme-editor.exe should launch on executing it.

Still, a theme editor (same?) is launched successfully from within configure.exe/Edit theme button!

Logs

log.log:
7/31/2026 10:03:24 PM [INFO] Loading theme AMD from res\themes\AMD\theme.yaml

Screenshots / photos of the Turing screen
N/A

Environment:

• Smart screen model [8.8" new HW version]
• V3.10.0 official release
• Windows 10
• Python version: I assume the executable uses its builtin python (3.13?)
• AMD 8 core CPU, Nvidia GPU

Additional context
No problems with the display, USB connection or any other HW related since in Ubuntu everything works as expected, except for the 30% CPU usage.

Start with Configure.exe, Main.exe, theme-editor.exe, and the troubleshooting page, then inspect log.log while reproducing the launch from PowerShell. Compare the behavior of direct execution with the successful Configure.exe/Edit theme path and identify what diagnostic output is available. Done means the launch failure is explained and the relevant executable behavior or debugging guidance is corrected.