Recent posts

#11

General / Re: I accidentally set all of ...

Last post by Jeremy Collake - August 26, 2026, 03:45:58 PM

The "X" (excluded from ProBalance) will be seen on hard-coded exclusions. It's a signal to do nothing to that process.

Some processes, such as svchost.exe instances, will have CPU Sets that they themselves set. Process Lasso is reflecting that.

There's nothing left that Process Lasso is doing, so I think you'll eventually discover the issues you're having are elsewhere. However, to confirm that, you can uninstall Process Lasso for an extended period, say a few days.

Hope this helps!

#12

General / Re: I accidentally set all of ...

Last post by agma77 - August 26, 2026, 12:42:09 PM

What if that doesn't work? It's still doing the same thing. scvh host says the cpu set is 0/0-15 also. a lot of the rules have n x on them but when i check their rules it shows nothing.i just did a system restore for a few days back and it didnt help.i even hard reset my computer and it didnt work. now steam cant even access my d drive. how do you reenable hyper threading?

#13

General / Re: I accidentally set all of ...

Last post by Jeremy Collake - August 26, 2026, 11:41:46 AM

Use menu item "Options > Reset Configuration", then restart your PC. No changes will have persisted.

#14

General / I accidentally set all of my s...

Last post by agma77 - August 26, 2026, 10:19:05 AM

I accidentally set all of my stuff to the same affinity. How do i revet these changes? everything is set to 0-15. I was just trying to disable hyper threading and then revert it. I also activated pro balance on them.. I was trying to fix things and I think I am making things worse. I also set one to none because I was trying to figure out how to fix the issue.

#15

ProcWatch / Re: ProcWatch keeps showing al...

Last post by Martin23 - August 20, 2026, 03:56:48 AM

Thanks for the clarification—glad to know the duplicate/stale alert issue has been fixed.
I'll update ProcWatch and keep an eye on the Recent Events list for any recurrence.

#16

Process Lasso / Re: bitsum highest performance...

Last post by boggo - August 16, 2026, 08:11:12 PM

I ran into this. None of the documented fixes worked, but what did work - just uninstalling and reinstalling process lasso.

#17

Process Lasso / Re: New load-based power profi...

Last post by Jeremy Collake - August 14, 2026, 10:42:55 AM

We are considering restoring this. The Governor doesn't otherwise need to track per-core loads (only the GUI), so that was the reason the option wasn't carried over to Process Lasso. However, we can certainly add per-core load checks to the Governor and only use them when a dependent feature is turned on. I'll get back with you on this .

The smoothing window option averages the samples over the last X ticks of the Governor (default 1 second) and uses that average to decide when to act. This is needed if you don't want it to act during a 1-second load spike, for instance. It's similar to the minimum time in power plan option in that it prevents frequent switching, but different in that it is using the average to decide when to act in the first place.

#18

Process Lasso / Re: New load-based power profi...

Last post by lilysmith10 - August 14, 2026, 06:46:40 AM

The per-core load option was particularly useful for single-threaded workloads, so I'd also like to know whether its removal was technical or simply a design change, and how the smoothing sample window interacts with the minimum power-plan time in practice.

#19

ProcWatch / Re: ProcWatch keeps showing al...

Last post by Jeremy Collake - August 13, 2026, 07:27:10 AM

We've now fixed a bug that could cause duplicate entries in the Recent Events list. That may be what you saw. If you see it again after updating, please let us know.

Highlights for currently triggered rules were also added.

Thanks for the feedback!

#20

Process Lasso / Re: Rules Editor requests

Last post by LownSlow - August 12, 2026, 01:05:43 PM

Thanks so much, Jeremy!  Much appreciated!