Unclear how I'm the first post here.
Unlike Process Lasso, ProcWatch has an issue (at least here in Win11) in which despite the fact that the automatically-created scheduled task (ProcWatchAdminAutoStart) clearly has the -tray switch in its command-line, it starts open upon login. When I click OK, then it goes to the tray.
If I quit it entirely and then run it from Scheduled Tasks manually, it does go right to the tray automatically. I can't really explain such a thing, unless it needs a startup delay in the task on some (slower?) systems. I'll try that and report back if it works.
We will check this and get back to you!
The auto-start w/o admin rights uses the registry instead of Task Scheduler, and the /tray parameter was omitted there. This was getting executed prior to the "as admin" Task Scheduler entry, thus you saw the window pop up.
This has been fixed as of v0.0.3.1 BETA. If you try it, let me know how it goes!
Thank you
Thanks. Updated now (the update works very well, putting you right back in the program). Everything below is only tested with v0.0.3.1.
I'd forgotten that you had two startup choices, though I didn't intentionally have both selected since that wouldn't have made sense (I would have chosen admin only). I do see that you CAN select both though, which I don't think you intended since they should be mutually exclusive. This can lead to some confusion, such as:
1) Start with neither selected
2) Choose Start with windows (it adds it to the registry)
3) Uncheck Start with Windows (it's removed)
Where the trouble starts:
1) Start with neither selected
2) Choose Start as Admin at login (it adds the task)
Problem: You may need to click OK and then the tray icon to see this, but the second step ALSO checks Start with Windows--fortunately, this is only cosmetic as it doesn't add it to the registry (maybe this wasn't the case in the last version, leading to my problem).
3) Uncheck Start with Windows
Problem: It unchecks Start with Windows (good) but also unchecks Start as Admin (and removes the task)
Since you offer both, which pieces of the program actually require admin? I instinctively run this kind of program as admin and assumed that it needed it across the board.
Thanks for the feedback!
The confusion is because we tried to couple the auto-start settings in a weird way. As of v0.0.3.3 BETA, we've created a submenu for the three distinct auto-start settings: No, Limited User, and Admin.
As to the difference: Admin is necessary to watch processes running as admin. If ProcWatch is run as a limited user, it will not have visibility into those processes. We'll work to make this clearer!
Please let me know if you run into any further trouble or have any suggestions.
That's an excellent way of doing it. All fine now. Thanks.