[BUG] Controller Tray Icon not autostarting on Admin users

[YukiXXL]

The TinyWall Controller tray icon does not show up on Administrator users, only Standard ones.
I also checked the Task Scheduler and it seems it is wrongly configured. The account to run is called "INTERACTIVE" and not "Users". It also uses "Run with highest privilages". Also, the program it executes is stated without quotes (not really a problem but could be when folders with spaces are used. using quotes is safer).
Changing the configuration or deleting gets restored on restart by the service. This could be a problem as this behaviour is malware-like so better make an option under "Maintance" to repair the TinyWall rather than the service repair itself.
Thank you for your attention and work.

[pylorak]

The account to run is called "INTERACTIVE" and not "Users".

Interactive is a built-in security group for users logging on locally (or remotely via RDP). Since the tray icon should only be shown in interactive sessions, why would the Users group be more appropriate?

It also uses "Run with highest privilages"

This is on purpose. This allows admin users to whitelist programs running with admin privileges by window without manually having to elevate the TinyWall controller app.

Also, the program it executes is stated without quotes (not really a problem but could be when folders with spaces are used. using quotes is safer).

TinyWall is installed by default to Program Files, which already contains spaces, yet it still works. Can you show an example where the current method doesn't work?

Changing the configuration or deleting gets restored on restart by the service. This could be a problem as this behaviour is malware

It cannot be considered malware, because TinyWall only repairs itself when it is installed. Unlike malware, it doesn't try to reinstall or repair itself if the user uninstalls it. It respects the user's wish to be disabled/uninstalled. I don't think it is "malware behavior" when an applications that has been actively installed by the user repairs itself to stay functional when it recognizes its installed state has been corrupted.