`-w, --nowindow` flags don't work on "Windows Terminal"

[theSoberSobber]

• When using -w or --nowindow the expected behaviour is that a console is not to be spawned when launched from the gui, but it still does, it just minimizes the console
• The minimizing is nice but doesn't work for my needs as I need it to start on startup with --loop, so I don't want the console window to stick around
• Daemons on windows don't require a console window to be open at all times
• I am testing it from GUI by creating a shortcut and in it's target adding the flags --loop and -w

If you need a Video of the bug, I'll be more than happy to record one!
Thanks!
@thibaultmeyer

[thibaultmeyer]

Hello,

I'm not reproducing the problem. I created a shortcut and then edited the target to add "--loop --nowindow". Double-click on the shortcut and the application starts in the background. The console only appears for a fraction of a second. Nothing on my application menu bar

Note : Detaching from the console have some limitation on Windows. By example, you can't get "--nowindow" working if application is running from a terminal/console.

[theSoberSobber]

Hey man, sorry I closed the issue wrongly, see the attached to see what is the problem, thanks.
Catbox URL to Video

[theSoberSobber]

are there any logs that I can send too?

[thibaultmeyer]

I've managed to reproduce the problem, but unfortunately I don't have an immediate solution to correct it in the code. It seems that the Windows API to hide a console doesn't work properly with PowerShell.

As a workaround, you can enable legacy mode for this shortcut (see picture below)

[theSoberSobber]

Damn :((
The problem is that I actually do not care about using shortcut, I just wanted to add a binwallpaper.exe --loop in the startup registry key so that it runs with my computer all the time, but that spawns a window :((