Bitsum Community Forum

General Category => Process Lasso => Topic started by: virtuallytasty on March 05, 2026, 09:57:18 PM

Title: Where is the INI toggle for rule enforcement on start_protected_game.exe?
Post by: virtuallytasty on March 05, 2026, 09:57:18 PM
Hi everyone,

I noticed in the changelog the following line:

"Core/GUI: Add INI toggle for allowance of rule enforcement on start_protected_game.exe"

However, I can't seem to find any information about it. There's no documentation, no FAQ mention, and I also don't see any option related to this in the GUI.

I checked the configuration file as well (prolasso.ini), but there doesn't appear to be any new entry related to this feature, and nothing was automatically created after running the program.
Could someone clarify:

Where exactly this INI toggle is supposed to be located?

What the exact parameter name is in the INI file?

How this option is intended to be used?

Right now it's a bit confusing since the changelog mentions the feature, but there's no guidance on how to access or enable it.

Thanks in advance!
fish it! (https://fish-it.io/)
Title: Re: Where is the INI toggle for rule enforcement on start_protected_game.exe?
Post by: Jeremy Collake on March 06, 2026, 06:27:00 AM
The option is not exposed in the UI, but is in prolasso.ini as:

AllowBlacklistedProcesses=false
The only process in the blacklist is start_protected_game.exe, which is an Easy Anti-Cheat launcher used most notably by Elden Ring.

Prior to v17.0.2.18, rules were not enforced on that process, with the exception of priorities by registry (IFEO). It was blacklisted a few years ago because we had a report that it was sensitive to CPU affinity adjustments. Specifically, it will refuse to launch the game if its CPU affinity is not set to all cores. In fact, even inherited CPU affinities cause that process to balk, something we found in a later investigation.

We recently had a user request that rules be allowed to be enforced on that process, and we were able to comply thinking that a mandated CPU affinity enforcement delay was sufficient to mitigate the sensitivity. Indeed, it is, or can be, but the necessary delay will vary between systems. So, we had to revert that change and this INI setting was added to set the default behavior to back to ignore. Further work on this area makes it possibly temporary, hence the lack of documentation.

Apologies for any confusion!