Recent Posts

Pages: 1 2 [3] 4 5 ... 10
Process Lasso / A question about Processor Group Extender
« Last post by Jibroni on October 17, 2021, 07:35:07 PM »
 :-\ So from my understanding of Processor Group Extender is it forces an application to use the full CPU. So is this meant to be used only for CPU's that have 64 logical cores, or can I also used it on a 16 thread CPU? And can I use it on a video game? Will it, for instance force a single threaded game to use more of it? It sounds scary, so I figured I'd ask around first before trying it. What does "group unaware application" mean exactly?

Process Lasso / Re: Latest Beta ..
« Last post by noahphense on October 05, 2021, 01:14:35 PM »
Hey Jeremy,

Current Version: PL Pro x64

The boolean toggle (between versions) you mentioned sounds perfect for the root-cause of both of the items I mentioned in the OP.  So cheers to that.

Regarding the ekrn.exe, I grep'd for it, it's the only one in the system.  As of today, it's back to normal operation.

With that said, the deep wildcard (\*) recursive'ness is god-like.  I've been using it heavily, since the beginning.  I wont bore you with how many I actually have, but here are a two examples.  It would be quite time consuming to manage without them.

My programming language:
c:\pb\*   (which covers everything below that)


The lts573 is just the version number.  There is nothing in that directory except two more dirs, 32 and 64 bit versions.

This is a big one:

All of those below, have their own deep sub-dirs as I'm certain you are already aware.  It's been working great thus far.  With the exception of some one-offs, where a launcher is calling another executable.  Which is understandable.


Cheers for the help and the info.

Process Lasso / Re: Latest Beta ..
« Last post by Jeremy Collake on October 05, 2021, 07:00:50 AM »
The svchost actions are just due to your use of the beta. They won't be acted on again.

In the last few betas builds prior to release, the ProBalance service exclusion was intentionally turned off. However, that change was reverted by the final 10.3 build. Your exclude services setting will also changed back to true when you update to the final.

There should be no change related to recursive path handling and wildcards, with the ProBalance exclusions or other rules. Can you check the log, find the ProBalance event for ekrn.exe, and confirm it is actually in 'c:\program files\eset' and not 'c:\program files (x86)\eset' or elsewhere, causing the path mismatch?

Ekrn.exe was likely acted on because of the now reverted service exclusion change, so is the same phenomenon as your svchost.exe actions.
Process Lasso / Latest Beta ..
« Last post by noahphense on October 04, 2021, 08:32:20 PM »
Something I am noticing.  As of the last beta.

In the ProBalance Exclusions, I've been using things like this for a long time.

c:\program files\eset\*

There is nothing in the directory, but there is a folder and the rest of the app in that folder.  IE.
C:\Program Files\ESET\ESET Security

It seems that recursive'ness, has stopped being functional.  As well, I am now getting quite a few svchost punches.  Not sure if that was an intentional change.

I've attached an image.


General / Re: Win 11 - Explorer.exe memory leak
« Last post by Jeremy Collake on October 04, 2021, 07:57:05 PM »
There isn't a great solution to a memory leak. Simple memory trims aren't going to be effective.

The only viable solution is to use a Watchdog rule to restart Explorer.exe when its memory usage grows over a certain size.

However, since Explorer is a special system process that may have multiple instances, it isn't clear how well such a rule would work.

As a side note, I've personally been quite frustrated with Windows 11 bugs. They are really slowing me down, impacting day-to-day work. I hope a miracle happens and suddenly things come together!

General / Win 11 - Explorer.exe memory leak
« Last post by Globespy on October 04, 2021, 06:55:33 PM »
I read an article on 'PCGamer' (there are other tech sites reporting this) and checked it out for myself.
Indeed, the more file explorer windows you open, the larger the memory load becomes (which is expected).
However, when you close all those windows the amount of memory being used remains the same, but even worse is that it just keeps getting larger every time you open an explorer window until you either force a restart of explorer.exe or reboot your PC.
Was hoping a program like 'Process Lasso' would have something to help here, but I haven't been able to find a solution?

Appreciate any tips on PL functionality that may be able to help.
Process Lasso / Re: Stopped and restarted Process Lasso
« Last post by Tarnak on September 28, 2021, 11:47:30 AM »
Keep them coming...

Process Lasso / Re: Stopped and restarted Process Lasso
« Last post by Tarnak on September 28, 2021, 08:16:45 AM »
I have been using Process Lasso since version 3, on XP desktop together with WSA [formerly Prevx].

Then went to Windows 10 Pro in 2016, i.e. Microsoft Surface Book laptop which died July 2021.

Now, I am with a much cheaper HP laptop running Windows 10 Home. Don't want to get a more expensive laptop, for the time being.

I will persevere with running both PL and WSA. Thanks, for your time.
Process Lasso / Re: Power Plan often not doing what it should
« Last post by Jeremy Collake on September 28, 2021, 06:48:00 AM »
Great! So we see vrmonitor.exe is changing the power profile on its own accord.

This (SteamVR) is therefore the culprit. When it exits, it is likely switching the power profile back to that which it started in, leaving you stuck in BHP.

You can read more about SteamVR changing the power profile here.

Ideally, there would be a SteamVR option to turn off its change of the power profile. However, I don't know if such exists. We'll be working on ways to improve this interaction in the future, but in the interim you may have to keep manually changing the power profile back after using SteamVR.

Other mitigatory rules are also possible, such as setting an application power profile on a system process like 'explorer.exe'. However, I can not currently attest to that.

And, no, you don't need ParkControl. It just has that handy feature to show what process changed the power profile. But now you've looked that up in the Windows Event Log, so it is unnecessary.

Process Lasso / Re: Stopped and restarted Process Lasso
« Last post by Jeremy Collake on September 28, 2021, 06:41:02 AM »
No, that doesn't have anything to do with it. That event just records the power profile change.

Whatever the cause, I don't think it is the fault of Process Lasso. What sort of hardware are you running on this PC? You should definitely get rid of that Webroot software, it will be taxing everything, and it doesn't look like a system with much extra capacity.

Pages: 1 2 [3] 4 5 ... 10