Process Lasso FAQ

Did you know? Process Lasso has been around for over 15 years!

Frequently Asked Questions (FAQ)

Should I download the 32-bit or 64-bit edition?

Process Lasso’s installer auto-corrects if you get the wrong edition, so have no worries and download either one. If you want to ‘get it right’, then an easy way to check is this: If your PC contains a “\program files (x86)\” folder, then it is a 64-bit OS.

This same auto-correction applies to the Server vs Workstation editions.

Which License Type Do I Need?

Process-Lasso-Pro-workstation-license-sFor the majority of users, that wish to optimize their personal computer(s), one of our Workstation Licenses (1-5 PC’s) is the correct choice (Single PC or Entire Home). Commercial Workstation purchases should check this page.

server-square For a business, or anyone using their own Windows Server(s), our Server licenses is the correct choice (Server, Site or Multi-Site), depending on your set up and/or needs (see the Server License options for more details on each License type).

Do you have a refund policy?

Yes we do! We stand behind the quality of our products and will refund 100% of your money if you are unhappy with the product. You have 45 days to decide to choose a refund. No questions. No hassle.

We only want you to have bought Process Lasso if it truly adds value to, or improves, your Windows PC or Server experience.

Do I get free updates?

Licensed users are entitled to either LIFETIME updates, or one year of updates, depending on the license chosen at purchase.

What are the installation requirements for Process Lasso?

Workstation: Windows XP or above.
Server: Windows 2003 or above.
Disk space: Up to 50MB – due to different languages, which is why the installer can compress down to 2MB
Memory: Very little is consumed by either the GUI (ProcessLasso.exe) or Core Engine (ProcessGovernor.exe), so this requirement is simply whatever your OS recommends. No additional RAM necessary.

Does Process Leave any debris behind after uninstall and what is the uninstall procedure?

No.  Process Lasso does not make a bunch of system modifications or anything. Once you remove it, it’s gone. That said, if you find a case of debris that we missed (and it would have to be minor, such as a shortcut), please let us know!

CAUTION: You MUST run the uninstaller from the Add/Remove programs menu. You can NOT run it outside this context. I am adding this to the FAQ.

How do I Activate Process Lasso Pro With My License Activation Key?

Open your Process Lasso interface by clicking on its icon in your task bar (bottom-right corner of your screen), then from its top Menu click on Help and select Activate this software.

Then copy and paste your license activation key (can be found in your Order History) into that pop-up window in the space that follows Activation code: then click the Activate now button to complete.

If you do not see options to Activate there, then the product is already activated.

First, you must be connected to the Internet. If any firewall attempts to block ‘plActivate.exe’ from connecting to ‘’, be sure to let it through! This is a one time connection to validate the license. PL-in-Taskbar Click the icon in your Taskbar (bottom of your screen).

See the Help > Activate this software menu option, as shown below. Activation screenshot 1 If you do NOT see this, then the product may already be activated.

To ensure the right license is applied, use Help > Change license code. Activation screenshot 2

Can I re-use the same activation key after reformatting and installing a new copy of Windows?

Yes, you can re-use or transfer the same license activation key after reformatting your computer and reinstalling a new version/copy of Windows.
If you purchase a single license, that same license will activate Process Lasso installed on any Windows system, but it will only work on one system at a time (hence single license).

Do you offer support? What about sales questions?

Yes, we absolutely do! Although Bitsum is a small team, we pride ourselves on customer communication. Please see our Contact Page. We also have a Community Forum where you can ask our entire community about a specific issue.

The same goes for sales questions. Please email us at or visit the Contact Us page.

What versions of Windows is Process Lasso compatible with?

Process Lasso is designed to work with all Windows versions, including XP, Vista, 7, 8, 8.1 and 10, as well as all Windows Server Editions. This includes Windows 2003, 2008, 2008 R2, 2012, 2012 R2, WHS, and more…

Furthermore, Process Lasso has some specific features that compliment the latest Microsoft CPU and I/O scheduler enhancements.

What do the system tray icons mean?

Please see this page for a complete description of all system tray icons.

Is Process Lasso compatible with Windows 10?

Yes! It has been extensively tested on Windows 10 from early debug builds of Windows 10 till present. In fact, we test it on Windows 10 more than any other platform. Process Lasso further continues to be as effective and necessary as ever with Windows 10. We personally love Windows 10, and adding Process Lasso to it will make it perfection – at least in our eyes.

How many CPUs or Cores does Process Lasso support?

Process Lasso v8 supports up to 64 logical processors and any number of physical core packages, so long as the total logical core count does not exceed 64.

Is there a comprehensive list of features?

See this link for all Process Lasso features.

Process Lasso is too complex, do you have something simpler?

First, remember that you don’t need to mess with all the advanced features of Process Lasso. You can just install it and forget it. However, if you want an even simpler solution, we do have ParkControl and (new) ProBalance Stand-Alone (still in development, but available).

Will ProBalance degrade performance in any way?

The ProBalance algorithm is designed in such a way that it will never degrade your system performance, only improve it.

It is extremely conservative. For instance, one of it’s many criteria (by default) is a process must be of normal priority class. Most audio apps set themselves to a High priority class. Thus, this exclusion was added, as it is assumed the application that sets it’s own priority class knows best.

Worst case if ProBalance did take action on some important process, you can always exclude it, but I very rarely hear of this due to the built-in exclusions and conservative nature.

Can I limit memory use of applications?

Restricting memory consumption is problematic. If a process needs to go beyond some threshold in virtual memory consumption then your options are (a) to deny the allocation, certainly resulting in an unrecoverable exception in the application, or to (b) stall the application while you wait for some other condition to be met (like a reduction in total virtual memory use). Neither is a good option.

Of course you can ‘trim’ the virtual memory, but that isn’t going to be effective if the virtual memory is actively referenced, it will just get paged right back in as soon as it is referenced. This is normally never a good idea as Windows will page out unreferenced virtual memory anyway.

Process Lasso does offer another option, setting a Watchdog rule to restart (or just terminate) a process if it exceeds a virtual memory use threshold. That may be the best and most proper action in many cases.

Is Process Lasso useful for my Real-Time applications?

Absolutely! For instance, Process Lasso has been very popular by Audiophiles because it’s intelligent algorithms, namely our proven and famous ProBalance algorithm, will keep background processes in check to ensure that maximum CPU resources go to your Audio applications. Further, it has power plan automation, and using our Bitsum Highest Performance mode, you can ensure your CPU is always in a state ready to execute code. Other intelligent algorithms and user-created rules can ensure a smooth and consistent experience for your real-time applications!

I don't see a performance boost, is it working?

First, let us be sure your expectations are correct – no product is a panacea for all system problems, and certainly not all use cases benefit equally from Process Lasso’s automated tuning. However, ProBalance does always keep you protected from that ‘worst case’ scenario, which you may encounter at some point, and it will save you from an improper shutdown.

ProBalance also does not act just to pretend to be doing something. It acts only when necessary. So if you are barely taxing your system, you aren’t going to see much difference in responsiveness. However, during times when you have your CPU loaded up, you will see a dramatic increase in responsiveness if the problem is CPU bound and ProBalance is able to cope with it. Sometimes the issue is I/O related, like waiting for a hard drive, but when it is CPU related, ProBalance addresses it.

This is well demonstrated by real-world and synthetic demos like our CPUEater Demo. I recommend that you read and try the CPUEater Demo yourself to see the impact. There is no trick here. You can recreate the demo in any language with a simple infinite loop (and nothing else!). See this page for more information on ProBalance …

Note that the Automation Features are ‘utility features’, so if you need them, then you need them. They don’t relate to this answer.

How can I even further minimize Lasso's resource use?

Although Process Lasso is inherently very lean, you can reduce it’s resource consumption even further by taking any of these steps:

  • Set the GUI to load manually. The core engine (processgovernor.exe), running in the background, will apply all algorithms and automation. You can then open the GUI when you need to check the status or reconfigure Process Lasso. Note that when the GUI is not running, the system tray icon is also absent.
  • Disable process icons. The nice little icons shown beside process names must be retrieved from disk and use virtual memory. Therefore, you can improve performance (and sometimes even complications) by disabling process icons via the View Menu of the GUI.
  • Disable or limit logging. Process Lasso’s core engine will do a lot of logging by default. This includes process creation and termination. On high-activity systems, you may want to disable certain log event types, or the entire log.

How do I force an application to make use of under-utilized CPU or GPU cores?

A single thread can’t be externally split into multiple threads, thus you can’t force use of unused CPU or GPU cores. You could force that single thread to be swapped between the CPU cores, but that would only decrease performance due to the switches, and have the same total CPU utilization.

The application has to be programmed to utilize multiple threads in order to make use of all cores. So you might say, “Ok, then why didn’t they do that?”. Well, some actions are linear in nature. In fact, many are. For instance, if I’m adding 2+2=4, it’s really hard to break that up into multiple threads.

The same goes for use of the GPU. The application has to be programmed to use it, you can’t force it to change it’s characteristics later.

This is why the performance of individual CPU cores still matters. If you have single-threaded CPU bound load, you can have 256 CPU cores, but only 1 will be utilized, and it’s individual performance will be the system max.

The core utilization graphs are not showing. What's up?

First, make sure they are enabled in the View menu (if Process Lasso). Second, make sure you have the right bit-size. This may require a product reinstall. Otherwise, your performance counters are in some way corrupted and there is little else that can be done. The command ‘lodctr.exe /r’ is run for you to try to repair this condition if Lasso finds it to be the case, so all that can be done is done.

I have an active PC, should I disable logging?

Yes, if you have an active PC, you may want to disable certain Process Lasso log events like process creation/termination, or disable logging entirely. For a highly active PC or server, it can be resource consuming. Also remember that you do not need to have the GUI running all the time since the stand-alone core engine (processgovernor.exe) does everything that is important.

What is Gaming Mode - Is Process Lasso useful for Gaming?

Absolutely! Process Lasso is great for games.

Process Lasso’s Gaming Mode configures ProBalance and the Power Profile in such a way as to be best equipped to run games or other high-demand applications.

Further, as of Gaming Mode 2.0 in 2015, a special power profile is used that disables certain CPU power saving features, such as core parking and CPU frequency scaling (down-clocking on idle). This ensures that your CPU is always ready to execute code!

What is the difference between Process Lasso Pro Workstation and Server editions?

There are two editions of Process Lasso. One is the Workstation Edition, the other is the Server Edition. ‘Pro’ just means licensed/unrestricted and is not itself a distinct edition of the product.

The difference between the Workstation and Server Editions are some programmatic differences (though functionally the editions are presently very similar but continuously diverging), and the license type. A Windows Server install requires the Server Edition, and a Windows workstation OS requires the Workstation Edition.

How does Process Lasso's Keep Awake work?

Process Lasso’s Keep Awake works by issuing a power subsystem API call to inform the system that activity is still occurring. It does NOT do any ‘dirty hack’ like emulate keyboard input, as such is not necessary. It will issue this call once a minute at minimum, more if required.

Process Lasso crashed! What should I do?

We apologize! You are apparently one of the unlucky few that have experienced crashes of Process Lasso. If you contact us, we’ll work with you to try to determine and fix the cause. Not just for you, but for other users. In the interim, try a fresh install of Process Lasso and reset your options to defaults (bottom of Options menu). Last, try disabling Process Icons in the View Menu. These can sometimes be problematic with certain third-party shell extensions.

How can I reduce CPU cycles consumed by Process Lasso?

There should not be any general problem with CPU consumption by Process Lasso because it’s native x64 code is highly efficient. When the User Interface (ProcessLasso.exe) is minimized, it goes into a pseudo-sleep mode, further reducing CPU use. The Core Engine (ProcessGovernor.exe) always consumes minimal resources, working silently in the background to enforce process rules and algorithms.

If you have a condition where the GUI is consuming an extraordinary amount of CPU cycles (like an entire core), then it may be caused by an interoperability issue with your security software. You may want to try disabling or uninstalling particularly ‘beta’ versions of security software. You can also do these things:

  1. Reduce GUI Refresh Rate. See menu ‘Options / General / Refresh rate / GUI’.
  2. Reduce Logging. See menu ‘Options / Log Options’.
  3. Disable process icons. See menu ‘View / Show process icons’.
  4. Close ProcessLasso.exe, but leave the core engine (processgovernor.exe) running. Then only start the GUI when you wish to view activity or make configuration changes. The core engine (processgovernor.exe) to take care of the real work.

Remember, since Process Lasso was designed to have an independent core engine, you can close the GUI completely. No system tray icon will exist, but Process Lasso’s actions will still be taken by ProcessGovernor, and those actions will be logged if you wish to review them.

The system tray in is disappearing, or GUI crashing. How to fix?

Try disabling process icons via the menu item ‘View / Show process icons’ This is indicative of a silent crash of Process Lasso’s GUI. Remember, the core engine, processgovernor.exe continued to operate, so the product functions, like ProBalance, remained active.

Is ParkControl Pro included in Process Lasso? Can I use both together?

No, it is not included, and yes, they are designed to run together.

Basically, ParkControl Pro has features not present in Process Lasso, such as a dynamically changing system tray icon that reflects core parking status. Going forward, there will be more differences.

They are designed to work along-side each other, so when ParkControl Pro is installed, Process Lasso’s ‘Core parking’ tool will actually just open ParkControl Pro’s window. This can lead to the perception that it is ‘within’ Process Lasso, but the only thing within Process Lasso is a more limited rendition of ParkControl (no Pro).

Should I micro-manage CPU core assignments (CPU affinities)?

In some cases, yes, but it depends on your reason, and you need to be smart about it.

If your goal is increased performance, remember that the Windows OS CPU Scheduler tries to manage which threads are on what cores itself, and it’s not dumb. So, when you micro-manage CPU affinities, you are second-guessing it. This can only be appropriate when you are certain of what the loads are going to be and know what you’re doing.

If your goal is to limit CPU use, then you can do so by giving a problematic process access to only a limited subset of available cores. However, you must be sure that this process isn’t ‘blocking’, meaning slowing it doesn’t slow something else, or even everything else. Similarly, you obviously must be willing to tolerate the proportional decrease in that application’s performance.

We do NOT recommend limiting the CPU affinities of ALL processes with a broad rule like .; we also don’t recommend limiting the CPU affinity of system or security software.

In general, be conservative, cautious, selective, and smart!

What is the best setup for real-time uses like audio?

There is no special setup, just install and go. I will note that we now have CPUBalance as well – which is ProBalance isolated from the other features. For many audio users, especially those who already have optimized PCs and don’t need all that Lasso offers, this may be the preferred solution. Read at .

Do I need Process Lasso on a new computer?

Modern CPUs are not actually getting very much faster, they are growing parallel (adding cores). This is because we hit the limits of physics. Now, since a thread can only execute on one core (it can be seapped around, but it can only execute on a single core at a time and can’t be broken up, and most software still has single-threaded or multi-threaded CPU bound occurrences, it is more improtant than ever to have Process Lasso’s ProBalance algorithm, and it’s automation on top of that for custom CPU affinities.

So, ironically, you need it even more.

Still no answer? You should contact us. But there is also the legacy FAQ if you want to keep searching.