Trouble at script startup during system boot

[WhizASh]

Describe the bug I have enables the task scheduling so gaming gaiden would start at boot . but when i system boots the script starts and the powershell is not closing itself up instead it just stays in taskbar and when i close the powershell gaming gaiden also exits .

To Reproduce Steps to reproduce the behavior:

1. enable the task scheduling using install.bat
2. boot the system

Expected behavior At system boot the powershell start and auto closes and gaming gaiden also stays in background

Screenshots screenshot

Log: 2024-05-27T13:40:29 : Cleared log at application boot 2024-05-27T13:40:29 : Executing database setup 2024-05-27T13:40:30 : Database setup complete 2024-05-27T13:40:30 : HWiNFO not detected. Or Gaming Gaiden is already Integrated. Skipping Auto Integration 2024-05-27T13:40:31 : Starting tracker on app boot 2024-05-27T13:40:31 : Resetting Icon and Sensors 2024-05-27T13:40:31 : Started tracker 2024-05-27T13:40:31 : Starting timer to check for Tracking updates 2024-05-27T13:40:31 : Hiding powershell window 2024-05-27T13:40:31 : Starting game detection 2024-05-27T13:40:31 : Running one time garbage collection before app context launch 2024-05-27T13:40:31 : Starting app context

[kulvind3r]

It is a system tray application, check your system tray. It will be running there.

There is no GUI window, Powershell window opens and then a tray icon gets created and the Powershell window closes.

All interaction with application is done using system tray icon menu.

All GUI (games list, graphs etc) is shown in your default web browser when you click on a action.

I can even see it your system tray running. In your screenshots. Blue game pad Icon.

On Mon, 27 May 2024, 13:57 Yash Mahajan, @.***> wrote:

Describe the bug I have enables the task scheduling so gaming gaiden would start at boot . but when i system boots the script starts and the powershell is not closing itself up instead it just stays in taskbar and when i close the powershell gaming gaiden also exits .

To Reproduce Steps to reproduce the behavior:

1. enable the task scheduling using install.bat
2. boot the system

Expected behavior At system boot the powershell start and auto closes and gaming gaiden also stays in background

Screenshots screenshot Screenshot.2024-05-27.134700.png (view on web) https://github.com/kulvind3r/GamingGaiden/assets/140056700/7943b482-cc14-451c-9a73-ed73977ab58e

Log: 2024-05-27T13:40:29 : Cleared log at application boot 2024-05-27T13:40:29 : Executing database setup 2024-05-27T13:40:30 : Database setup complete 2024-05-27T13:40:30 : HWiNFO not detected. Or Gaming Gaiden is already Integrated. Skipping Auto Integration 2024-05-27T13:40:31 : Starting tracker on app boot 2024-05-27T13:40:31 : Resetting Icon and Sensors 2024-05-27T13:40:31 : Started tracker 2024-05-27T13:40:31 : Starting timer to check for Tracking updates 2024-05-27T13:40:31 : Hiding powershell window 2024-05-27T13:40:31 : Starting game detection 2024-05-27T13:40:31 : Running one time garbage collection before app context launch 2024-05-27T13:40:31 : Starting app context

— Reply to this email directly, view it on GitHub https://github.com/kulvind3r/GamingGaiden/issues/10, or unsubscribe https://github.com/notifications/unsubscribe-auth/ACBU6TX4LSDRGQK7DEFAXCDZELVARAVCNFSM6AAAAABIKXJRUWVHI2DSMVQWIX3LMV43ASLTON2WKOZSGMYTQNJWGM3DQOA . You are receiving this because you are subscribed to this thread.Message ID: @.***>

[WhizASh]

This is screen recording right after system boot . The app works perfectly fine if I start it normally by running the shortcut just that on startup the powershell window is not closing up automatically and if manually closed the app just exits.

https://github.com/kulvind3r/GamingGaiden/assets/140056700/ee60e898-f610-417c-8a66-26608514fadc

[kulvind3r]

Why are you closing the Powershell window??

Let the script run completely it will hide the window after it completes the startup and only the tray icon will remain.

If you close the window then the application will exit.

Let the window run, and reply if it doesn't vanishes even after waiting for few minutes.

On Tue, 28 May 2024, 00:03 Yash Mahajan, @.***> wrote:

This is screen recording right after system boot

https://github.com/kulvind3r/GamingGaiden/assets/140056700/ee60e898-f610-417c-8a66-26608514fadc

— Reply to this email directly, view it on GitHub https://github.com/kulvind3r/GamingGaiden/issues/10#issuecomment-2133920289, or unsubscribe https://github.com/notifications/unsubscribe-auth/ACBU6TV5HTRQ4ZNFJNA3UMLZEN37JAVCNFSM6AAAAABIKXJRUWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCMZTHEZDAMRYHE . You are receiving this because you modified the open/close state.Message ID: @.***>

[WhizASh]

So , i let the powershell running and did not close the powershell window , it did not close even after 30 min so i manually closed it . Then i noticed windows is launching terminal app which is launching powershell inside , so i changed the default terminal app to launch directly powershell.exe rather than just powershell which opens it inside terminal app AND GUESS what it worked now the window automatically closes . The problem solved !!! Thanks for the amazing app i am loving it !!

[kulvind3r]

Not sure why this is happening specifically on your machine...

Does it happen only for the auto start or does the Powershell window doesnt close even if you launch using the shortcut in start menu / desktop?

Edit: NVM, you answered this earlier, it runs fine when started using the shortcuts.

On Tue, 28 May 2024, 12:15 Yash Mahajan, @.***> wrote:

So , i let the powershell running and did not close the powershell window , it did not close even after 30 min so i manually closed it . Then i noticed windows is launching terminal app which is launching powershell inside , so i changed the default terminal app to launch directly powershell.exe rather than just powershell which opens it inside terminal app AND GUESS what it worked now the window automatically closes . The problem solved !!! Thanks for the amazing app i am loving it !!

— Reply to this email directly, view it on GitHub https://github.com/kulvind3r/GamingGaiden/issues/10#issuecomment-2134460105, or unsubscribe https://github.com/notifications/unsubscribe-auth/ACBU6TRUEXKKCOOQ7DYXVNLZEQRXDAVCNFSM6AAAAABIKXJRUWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCMZUGQ3DAMJQGU . You are receiving this because you modified the open/close state.Message ID: @.***>

[kulvind3r]

Two requests to help close this bug...

1. can you look at the properties of the shortcut created and share the complete string in the Target box.
2. can you run "cmd" ( Win+R =>type 'cmd' => enter ) and then run the command 'where powershell' and share the output?

I checked few things and in the scheduled task that is created on my machine, the launch string contains "powershell.exe" and not "powershell". So your machine having just "powershell" is different behavior.

i am on windows 10, it is possible that when install script is run on windows 11, it is creating a scheduled task (and shortcuts) which have "powershell" and not "powershell.exe", leading to a terminal opening which then opens the Powershell window.

on some machines where powershell version higher than 5.1 are installed , 'powershell' command can point to 'pwsh.exe' instead of 'powershell.exe', which is what i think is happening here and that is what i am trying to verify using the 2nd command i requested above.

once you share the Target string i can add a forced fix to prevent this from happening.

There is a new release planned soon, which will have lots of new features and i can add this fix to that release as well.

[kulvind3r]

Update: The latest release uses shell:startup folder instead of scheduled tasks for auto start and this issue should no longer occur.