NOTICE: Registration may require manual admin activation. After registering visit https://bitsum.com/contact/ to request account activation.
Started by parkd1, May 01, 2010, 02:09:11 PM
Select 'Options / General Process Lasso settings / Reconfigure the way Process Lasso starts'. On the second dialog, select 'HIGHEST' rights. Now ALL processes will be shown to you.
This is indeed possible, and I am implementing it in version 4. The solution was known long ago, but I was too busy to consider it and off in my own little world I guess. Thanks to users here drilling it into my head, I have finally given it some thought and taken their recommendation. From here on out Process Lasso will utilize the Task Scheduler instead of registry keys to start itself. This will allow it to start at login with highest rights, with no UAC elevation prompt -- for those who desire such a configuration.
This will be implemented in version 4. The code is a little more elaborate than a 5 minute chore, but isn't that difficult, so it should not take soon. It is very high on my priority list, so should show up in one of the next alpha builds.
For users wanting to manually set up Process Lasso to start at user login with HIGHEST rights, follow the steps here: http://www.bitsum.com/docs/pl/faq.htm#no_UAC . It takes less than a minute to set up a new task in the Windows Task Scheduler 2.0.
Please remember, when changing Process Lasso to run with elevated rights, be sure to also change its internal configuration -- else it may ignore processes from other users (perhaps desired in some cases, so it gets your elevated processes but not those of others). This can be quickly toggled in the menu option 'Main / Manage processes of ALL users'.
Quote from: Hotrod on June 22, 2010, 01:20:47 AMAwesome!! This was something I had asked for early on in the development. This kills 2 birds with one stone so to speak. Keep it up Jeremy.
Quote from: Hotrod on June 22, 2010, 04:23:22 PMIf we patch this manually with a Task Scheduler entry now, will it leave a redundant entry there when we update to the new version and it writes it's own Scheduler entry?