Running Process Lasso with Highest Rights - new beta improvements

I'm approaching final for v3.80. I've accomplished all but a few items remaining on my list, then I'll enter the testing (and regression testing) stage.

Slowly over the course of the next few days, I'll introduce a few of the new features in v3.80. Today's feature is better automatic startup of Process Lasso with Highest Rights for Vista+ systems with UAC turned on.

As many of us know, Windows Defender blocks automatic startup of all applications that want to run with Highest Rights. You can't even create an ignore list. I reckon this is a good thing, from a big picture perspective.

If you are running Windows XP or below, this article doesn't apply to you. So, you can stop reading now unless you are curious.

Since many people need to run Process Lasso with Highest Rights, even though it is not normally recommended, we have further accommodated that capability. Remember, Highest Rights is the mode that allows any single instance of Process Lasso to view and manage the processes of all users (including system processes). In some cases, this is certainly desired. In most cases, its not.

Originally, I had planned to work around Windows Defender by adding Process Lasso to the Windows Task Scheduler's list of application to launch when a user logs in. However, I changed my mind and tried a different approach. I call it the 'proxied launch'.

While Windows Defender doesn't allow launching of High Rights processes, it does allow launching of low-rights processes, who can then launch a High Rights process. Of course, when done this way, the UAC elevation dialog is shown to the user. In current beta, its actually shown twice - once for the GUI and once for the core engine. I plan to lower that to once before final.

Whether or not this is the way I stay with, I don't know. As a side note, the user has the choice of using the proxied launch or not. Still, the official recommendation is to just let Process Lasso run with normal rights. The only exclusions to this rule are single-user systems where a system service needs managing, or servers where the processes of multiple users need managing by a single instance of Process Lasso running as a service.