Recent posts

#31

Process Lasso / Re: Creating an inverse / rese...

Last post by Jeremy Collake - August 10, 2026, 11:51:33 AM

As you've discovered, there isn't currently a way to easily achieve an automatic undo of rules applied by a config profile.

We maybe can add something along those lines. I've ticketed it and will get back to you.

We'll also consider blanking the value on a rule when it's "all cores", but that would make it less apparent when such rules are set.

#32

Process Lasso / Re: Call of Duty via Xbox App ...

Last post by drivemadd - August 09, 2026, 11:23:22 PM

I've seen people run into this too. From what I understand, getting CoD to consistently prefer the V-Cache CCD can be tricky, and some rules don't seem to stick. Hopefully someone with a working setup can share the exact settings.

#33

Process Lasso / Creating an inverse / reset Co...

Last post by LownSlow - August 09, 2026, 02:26:23 PM

Summary: I'd like to create a profile that resets all of the actively running processes to their defaults without needing to manually enter the processes in the rules list.

Detail:

My understanding is that changing config profiles in Process Lasso (PL) does not necessary "undo" what the previously selected profile configured, which is why a reboot is often recommended (please correct me if I'm wrong...I'm fairly new to PL).

I'd like to create an "inverse" profile that would include the same processes as my tweaked profile, but set those processes all back to their default values (basically like they were never touched by PL).  Unless I'm missing something, this could help avoid a reboot or manually ending and restarting processes that might be affected by the tweaked profile.

Right now the only way I can think of doing that is:

1) Copy the profile I'd like to invert/revert, and choose "use current settings as this profile"
2) Use "Edit Rules" on the new profile and "blank out" each option in the rules table.

But this involves a LOT of double-clicking fields and selecting [blank] in the dropdown list.  Also, if I ever add a rule to the original profile, I have to do the entire rules table all over again.

Is there another way to do this?

If not, I have a suggestion: add an option to the "Reset Configuration" dialog box that offers to "maintain the list of rules but set them to default".  This would create inverse profiles instantaneously--both on initial creation and any time you've added a process to the ruleset for the profile you're wanting to revert.

One other thought.  When I've done this the manual way, I notice that the "Rules" column specifies "0-19" in it for each blanked out rule in the ruleset.  This makes the table messy.  It would be great if the Rules column for these processes looked like when there's no rule at all (just empty, unless PL or Windows has other defaults, like dwm.exe, System, explorer.exe, etc.)

Thanks for any help or feedback with this!

#34

Process Lasso / How do you change which Config...

Last post by LownSlow - August 09, 2026, 01:36:10 PM

How do you change which Config Profile is the default profile?

"Manage Configuration Profiles" shows "(default)" after one of my profiles, but I find no way to select a different one.

Thanks for any help.

#35

ProcWatch / Re: 0.0.2.7 starts automatical...

Last post by delaymellohi - August 07, 2026, 09:48:04 AM

It's great to see the issue was tracked down so quickly and that the startup settings were redesigned instead of just patching the original problem. Separating the options into Limited User and Admin makes much more sense, especially since the admin mode is needed to monitor elevated processes. Sounds like the update solved the original issue nicely.

#36

Process Lasso / Re: Should I uncheck CPU 0 for...

Last post by naguibk - August 06, 2026, 03:47:06 AM

for tuning tips asking respective game communities for tuning tips

#37

Process Lasso / Re: Optimizing CPU Usage with ...

Last post by naguibk - August 06, 2026, 03:42:58 AM

Optimizing CPU usage for intensive workloads (such as 3D rendering, video encoding, compiling, or heavy simulations) in Process Lasso requires moving beyond default settings to tailor core allocation, power plans, and thread management.Key Optimizations for CPU-Intensive Tasks1. Induce Performance Mode & Configure Power ProfilesBy default, Windows aggressively park cores and lower clock speeds to save energy.Enable Performance Mode: Right-click your workload executable (e.g., blender.exe, handbrake.exe) and select Induce Performance Mode.Bitsum Highest Performance: This forces the system into the Bitsum Highest Performance power plan while the specified application is running. It prevents CPU core parking, disables CPU throttling, and keeps core clock frequencies pinned at maximum speeds.2. Fine-Tune Hardware-Specific CPU AffinitiesModern CPUs feature asymmetrical core architectures. Tailoring CPU affinity ensures your heavy tasks get the best physical hardware:Intel Hybrid CPUs (12th Gen & Newer - P-Cores vs. E-Cores):Render/Export Tasks: Keep your intensive app assigned to all cores (P-Cores + E-Cores) for maximum multi-threaded throughput.Background Apps: Right-click background apps (browsers, Discord, communication tools) and set Efficiency Mode / Always / ON or pin them strictly to E-Cores so they never consume main P-Core threads.AMD Ryzen Dual-CCD CPUs (7900X, 7950X, 7950X3D, 9950X):Latency-Sensitive/Single-Core Heavy Tasks: Restrict the app to CCD0 (the cache-heavy or higher-clocked CCD).Heavy Multi-Threaded Tasks: Assign the application to all logical cores across both CCDs, but isolate background tasks to CCD1.

#38

Process Lasso / Re: CPU Sets rule ignored afte...

Last post by Jeremy Collake - August 03, 2026, 02:26:47 PM

Does the current CPU Set of the process change, or just the cores that end up used?

#39

Process Lasso / Re: Bug Report: "Export Entire...

Last post by Bonzo - August 03, 2026, 12:52:42 PM

Thanks for the advice

#40

Process Lasso / CPU Sets rule ignored after wa...

Last post by annasm - August 03, 2026, 05:57:07 AM

I'm using Process Lasso on Windows 11 and created a CPU Sets rule for one specific application so it only runs on a selected group of cores. It works correctly after a fresh boot, but after the PC wakes from Sleep, the same application sometimes starts using all available cores until I manually restart the process. Has anyone seen CPU Sets rules stop being enforced after resuming from Sleep? Is there a setting in Process Lasso to automatically reapply CPU Sets after wake, or is this a Windows scheduling limitation?