Bitsum Community Forum

Happy new year.

Some nasty issues, starting to nerve a little and I do not know what to do anymore to get rid of it, would appreviate your kind help.

I had some issues that special settings for X4.exe have not been remembered.
Or when I selected CPU affinity "always" for the X4.exe process and want to use the last 8 threads or whatever it was not remembered, whenever I looked at it again, different cores were selected compared to those I just choosed seconds ago.

So I tried to start over and removed all (2) profiles with the manage profile function.

Now I seem to have and use only the default profile, as in Profile Manager I get in the list no profile displayed.

But even now I get getting this message after login:
Warning: the configuration file is not writeable. Please check the path via "Options / General / Reconfigure the Way Process Lasso Starts".

I am starting PL as a service and didn't changes the proposed path, pretty default.

If I want to manage profiles I always get the message box "Use of multiple configuration profiles when the governor is running as service is not yet supported. The GUI may be referencing a different configuration file than the Governor, causing rules not to be reflected or enforced. Continue anyway ?"

Also a problem when performing frequent Beta updates, then the updater complains about not being able to save some files (although I entered Administrator password, thus the updater should have required credentials.

At the moment PL feels to me as if this tool is currently in a bad shape. Operation is not as smooth as it used to be.
Is this because I am running a Beta version ?

I do this because I hope that some other issues are quicker gone by this which I reported some weeks ago in the area of Idle saver not working, when running PL as service.

At the beginning I scratched only on the surface what PL can do.
Now where I want to use some more of the special features of PL, I run into issues and even upgrades do not run cleanly.
So .. could you kindly give me advice, which version of PL gives me most control over "most if not all" processes on the system
and does not have all these issues, that settings are not being remembered correctly, permission problems, ..

System: Windows 7 Pro (with latest updates)
PL: 9.5.1.0

Hi, Thanks for the feedback.
On the Gov as a service, there are some limiting factors at this time. You should get a message if opening configuration manager that Gov as a service doesn't support multiple configs (so use default).
Now the default path should be config " C:\ProgramData\ProcessLasso\config" and log "C:\ProgramData\ProcessLasso\log"  in configuration startup settings.

I have a testbed here setup like above and affinity, priorities are working fine with always settings.

On beta's again I am not seeing any issues, I update each beta, but I will look into it some more on your specific issues.

Edit: I see you are on windows 7, that could be a difference from my report above as I test in windows 10.
We will get back to you.

I am sorry for your experiences.

All of your problems stem from running the governor-as-a-service in combination with a limited rights (standard) user.  The bottom line is that this particular configuration scenario is the least well supported. So while these problems aren't just you, they are also not common.

You are most likely comparing your experience to the time before you switched to governor as a service. The issues you've encountered are not new, and support for this setup has actually been improving (hence the new warnings instead of silent failures). Therefore, there is no older 'better' build to go back to.

Running the governor as a service comes with trade-offs. You shouldn't do it unless there is a need. It is great for multi-user servers, but not so great for home users. especially limited rights users.

You could switch to an administrative user to manage all system processes when running the governor as a normal process. However, I would first question whether those processes really need managed.

The default config path when using the governor as a service is not writable by limited rights users, which is why you see the 'not writable' error. You could change this to a path under your user folder to resolve it.

The sporadic update issues are similarly related to lmited user with governor-as-service. We are evaluating that.

In the case of IdleSaver, it is not a simple bug, but due to the Windows architecture. The adjustment required to work around the issue might cause more problems than it solves, and ParkControl could be deployed to fill the IdleSaver role. Therefore, this adjustment is still being considered.

The config profile support will return to the governor-as-a-service once some multi-user complexities are worked out. This work has to be done deliberately.

The setting persistence issues you previously reported boiled down to not having write access to the INI, and not being warned about such. Now you are warned about this, attempted profile use, and IdleSaver with the governor-as-a-service.

You should uninstall Process Lasso and re-install it to clear things up, using the default normal process governor, then stay on the stable branch. You can 'File / Export' your configuration before doing this, then import it after the re-install.

From my perspective PL is a tool, that allows the user to customize process scheduling on a system.

I think controlling process scheduling makes only sense, if you can control ALL processes and threads on a system, not only those which were started by the user.

Example: pinning i.e. a process to CPU 3-6 makes IMHO only sense if the remainder of all processes avoid to use CPU 3-6.
Therefore I think I need to have as much as possible under the control of PL.

Yes I am running Windows 7 and this will stay. I do not like/trust Win10 for several aspects.

For security reasons I am running a user without administrative rights and this should stay.
I could change the rights for the folder or use a different folder if that would solve the issues to store settings ??
Or would it be a solution to i.e. run PL under the user credentials of "Administrator" account ?
Or another PL dedicated user account with Admin rights ?
But I wouldn't like having to enter an admin password each time the process starts.

Then the only remaining issue would be to run "Idle Saver", but if I remember correctly this you wanted to fix.
How far is this, can you roughly estimate when this would be available, because I really liked this feature.

Many thanks for your quick and kind response.

I agree this configuration scenario is important, which is why it is being steadily improved.

Given your preferences, I advise to make sure that configuration and log path is changed to somewhere writable by your limited user, then just hang in there with governor as a service. We can continue to use you as a guinea pig and fix issues you report.

I am also going to start testing this scenario much more thoroughly going forward.

The IdleSaver solution could be rolled out any time. I finished core work on it several days ago, but am researching alternate solutions that don't require an agent in each interactive session.

Phantastic, thanks for testing and rolling energy saving out.

Regarding Energy consumption (E5-1650v3, MSI RTX 2070 SUPER TRIO X):
Energy Profile High Performance: Playing Shadow of the Tomb Raider: 304W 1,33A, max 423W (Full HD resolution and highest detail).
Energy Profile High Performance: IDLE: tweaked by parkcontrol to disable cpu core parking and running at 3,6  GHz:  106W 0,49A
Energy Profile Balanced: tweaked by parkcontrol to park 50% of cores and running at 2.5 GHz (instead of 3.6 GHz): 85W 0,41A
Lowest Power settings:  tweaked by parkcontrol to park max amount of cores and running at lowest clock speed 1.2 GHz: 79W 0,39A

Energy saving would save around 27W on an IDLE system (between High Performance vs Energy Saving).

I finished and integrated the new per-session agent into Process Lasso.

After some early testing, it will be introduced in the next beta version - then IdleSaver will work in your setup.

I'll post here when the beta version is available.

Process Lasso v9.6.0.1 beta includes the new session agent.

Integration work was extensive, so further refinement is certain.

Cool many thanks, just upgrading.

V9.6.0.1 BETA

Sorry but it does not seem to work, when enabling IDLE saver I get this message when IDLE saver should change the energy profile to "energy saving".
But it doesn't and this is in the log:

processgovernor.exe
Action: IdleSaver has changed the power profile
More Info: Error - Energy Saver disabled, Governor as Service incompatible

That doesn't sound like this new version - that log entry was removed.

I wonder if your governor failed to get replaced.

You might want to try running the full installer from https://dl.bitsum.com/files/beta/processlassosetup64.exe

That said, we're taking a closer look at it and still early, so there could be some issue we haven't found yet.

Hi Idlesaver still doesnt work.

I even shutdown core engine and PL before installing from full installer and even performed a full reset of options.

My PC is in balanced mode, I configure Idlesaver to turn the PC into energy saving after 10sec.

I do not move the mouse, the system is Idle. But it still doesn't work.

If you want to see with your own eyes or want to have a look yourself we can arrance for a teamviewer session if you can't reproduce this on your system
and if this would help you qualifying and eventually finding the issue. My TZ is GMT+1.

Ok, I believe you. There may be some additional factor.

Please check the following:

1. Ensure bitsumsessionagent.exe is running in your user session.
2. 'Options / Power / Configure IdleSaver settings / Disable while Performance Mode' is engaged is UNCHECKED.

If the issue persists after a few more builds, I'll send a debug build so we can trace what is happening.

Thanks for testing and we'll get it sorted out!

Many thanks I think I can work on this on saturday.

Also note:

Did you change the configuration file path so that it is accessible by your limited user? If not, changes to the configuration will not persist or be adopted by the governor.

You must move this away from ProgramData (the default with service).

For the sake of experimentation, set it to 'c:\Users\ranko\ProcessLasso' or similar.

Sorry, had PSU issues with my system that needed attention.

Runing PL as service and using a different path to store configs works for me as normal not-admin user.
So thats a feasible solution.

Any progress meanwhile in terms of
- software upgrade issues and
- idleserver when using PL as service ?

Regarding IDLE server some progress ?
I am currently running version 9.6.0.8 BETA (Engine version: 4550700), PL as service, there it still doesn't work.

Not sure why IdleSaver still isn't working for you, it is so far in our tests. I will enable debug output and instruct soon, then we will find out what is going on. If it begins to work at any point, let us know.

Importantly, yesterday's beta versions had a build problem that caused a failure to find new updates, so you should download and reinstall (over-top) the beta 9.6.0.17 to ensure you continue to get them.

This work will be continuing and I will update this thread with anything pertainent.

Which debugging to be enabled pls ?

Upon testing in a fresh Windows 7 install, I found that the new session agent was not statically linked, causing it to fail to start if MSVC runtime DLLs are missing. This problem was only be seen in Windows 7, as Windows 10 has them pre-installed.

9.6.0.21 beta fixes this, now available.

Once complete, you should see 'bitsumsessionagent.exe' running as a process in your user session, and IdleSaver should now work with your setup.

IDLE saver works now in 9.6.0.23 BETA when running PL as service.
Thats great, many thanks for this improvement !

Update installation still fails.

Great to hear!

I am working on improvements to the update process in these environments.

Quick Update: I performed now an upgrade installation from Window 7 to Windows 10 1909 !!

Somebody told me that the protection from internet security suites alone would be too weak and most likely not fill the gap, that Microsoft ceased support for Windows 7. I would have bought extended support for Win7, but this is sadly only applicable for companies.

So from now on I will work with Windows 10 and use a few tools/script collection to harden/debloat my system and hope not to screw up too much by this... I implemented O&O Win10 Shutup first and will let it settle for one or two days to see, that nothing screwed up.
The next step is to try to debload the system even further by using this power shell collection, which is commented and looks very promising:
https://github.com/W4RH4WK/Debloat-Windows-10

One new PL upgrade report for Win10 1909

No warnings like on Windows 7, but .. the PL core engine does not restart.
Right click to the Icron in the Windows Notification Area to "Start PL core engine" does not do anything.

Which beta version was this, I have not seen this on my end with gov as a service?

Warning: on your debloating be very careful what type of app/scripts you use. I would generally stay away from script type app because most don't let you chose or pick what you want. Many "scripts" you will end up losing Xbox, MS Mail, calender, MS Store and may have issues with start-menu. I would make an image of OS before going further.

If you want my opinion O&O Shutup10 and their Appbuster are at top of the list, very safe just stay away from red marked ones. WPD also good and while I never used it if you must use script type one like Debotnet, that one at least lets you chose which to disable/remove.
I still would be very careful, you're not going to get any added performance it just cleans up things you don't need.

I noted the governor-as-service failing to start after an update from Limited users in yesterday's testing (it is due to the limited user, affects Win7 and Win10).

Previously, the governor wasn't stopped for limited user updates, so it is a consequence of successfully stopping and replacing the governor w/o reboot in these environments.

These items should be fixed shortly. (note update fixes take 2 updates to propagate through to an install)

Thanks for the feedback!

Could you kindly tell me the purpose of "Prevent Sleep" ?

I have a certain feeling that this doesn't work.

I assigned to MusicBee (a music player) to prevent sleep for "Prevent PC and Display".
Then I went away from my PC and the screen turned dark.

I thought that the purpose of this setting is, that to keep both on, PC and Display.

Many thanks for clarification.

This is for PL 9.6.0.51 Beta on Windows 10 1909.
It was an upgrade installation and I used OO Win10 Shutup to turn off most of the Win10 features that I dislike (Privacy, etc).

The upgrade to PL 9.6.0.55 Beta worked, many thanks :-)

Quote from: ranko on January 26, 2020, 04:08:39 PM
Could you kindly tell me the purpose of "Prevent Sleep" ?

I have a certain feeling that this doesn't work.

I assigned to MusicBee (a music player) to prevent sleep for "Prevent PC and Display".
Then I went away from my PC and the screen turned dark.

I thought that the purpose of this setting is, that to keep both on, PC and Display.

Many thanks for clarification.

This is for PL 9.6.0.51 Beta on Windows 10 1909.
It was an upgrade installation and I used OO Win10 Shutup to turn off most of the Win10 features that I dislike (Privacy, etc).

Yes, you have that right it should keep the system awake depending on setting when that process is running.
We are testing many factors of gov as service and seems this is not working correctly, though the "keep this PC awake" from main menu does work.

I'll go ahead and fix the Prevent PC sleep in these environments, adding that capability to the new session agent. Thanks for noting that!

Thats great, many thanks.
Process Lasso Pro is such a cool product, so useful, many thanks !

Quote from: Jeremy Collake on January 27, 2020, 06:40:34 AM
I'll go ahead and fix the Prevent PC sleep in these environments, adding that capability to the new session agent. Thanks for noting that!

Hi Jeremy, how are you ? Any news on this topic ?

It should already be fixed. Is it not working for you?

Was very busy, these days and waited for a response on this thread, I need to check.

Great this works now many thanks.

I see now another issue. Is it right to assume, that I should be able to see all processes if I run PL Pro as a service ?
Even as normal user ?

I have a Macrium Reflect running and do not see the process which actually performs the backup to be able to apply a high performance profile
or to prevent display going into energy saving mode.

I sorted for CPU load and I/O, but nothing shows up in both tabs "all processes" and "active processes".

I thought that I get through the GUI the ability to control all (relevant) processes.

Quote from: ranko on February 09, 2020, 02:55:08 PM
Great this works now many thanks.

I see now another issue. Is it right to assume, that I should be able to see all processes if I run PL Pro as a service ?
Even as normal user ?

I have a Macrium Reflect running and do not see the process which actually performs the backup to be able to apply a high performance profile
or to prevent display going into energy saving mode.

I sorted for CPU load and I/O, but nothing shows up in both tabs "all processes" and "active processes".

I thought that I get through the GUI the ability to control all (relevant) processes.

Hi, If you are Admin account you will see user and system process name in the "user" column of PL. If you are a limited user account you will only see user processes.

As a service, the Governor is able to manage processes in all sessions. However, as a limited user, the GUI would require you "Run as administrator" to show processes in other user sessions.

You can still set rules for those processes in the config dialogs, or run the GUI as admin to list them for config.

Note that after an install or update the GUI may be running as administrator and thus temporarily show all processes.

I made some thoughts about this topic.
As you know I have a separate Administrator user, so I have no chance to see all processes with my normal user account without admin rights.

Would it perhaps be possible, to add an entry "Show Process Lasso Main Window (Admin)".
Once you execute it you get then the usual password dialog, if you have no Admin rights ... ?!

I think that would be ideal otherwise you force a user to have Admin rights which I would regard not as good.

Yes, I think having an menu option to elevate (to admin) on-demand is desirable. I'll put it on the agenda. Thanks for the continued feedback!

Quote from: Jeremy Collake on February 16, 2020, 09:55:51 AM
Yes, I think having an menu option to elevate (to admin) on-demand is desirable. I'll put it on the agenda. Thanks for the continued feedback!

Oh that would be really sweet ;)

Thanks for picking up the ball and making the product really round, highly appreciate it :-)

The status flags for certain optimizations in the "Rules Colum" under "Active Processes" is not being updated properly.

I have for MusicBee.exe "ihA0-3".

Then I start disabling the optimizations in this order:
- Priority Class to Always -> None ...
- CPU Affinity   to Always -> No default affinity
- I/O Priority    to Always -> None

But "ih" remains although the 3rd action should have deleted it.

If you change the CPU affinity then "ih" vanishes, but then you get the same issue with CPU affinity.

If you change then Priority Class, then CPU Affinity becomes properly updated, but then you have the issue with Priority Class.

It seems to me that the last remaining flag has the issue not becoming updated properly in the Rules column.

I first noticed it now in PL 9.7.0.2, but don't know / can't exclude that this was already the case in earlier versions / Betas.

My system: Win10 Pro, 1909.

Many thanks for fixing this.

Quote from: ranko on February 19, 2020, 03:00:33 PM
The status flags for certain optimizations in the "Rules Colum" under "Active Processes" is not being updated properly.

I have for MusicBee.exe "ihA0-3".

Then I start disabling the optimizations in this order:
- Priority Class to Always -> None ...
- CPU Affinity   to Always -> No default affinity
- I/O Priority    to Always -> None

But "ih" remains although the 3rd action should have deleted it.

If you change the CPU affinity then "ih" vanishes, but then you get the same issue with CPU affinity.

If you change then Priority Class, then CPU Affinity becomes properly updated, but then you have the issue with Priority Class.

It seems to me that the last remaining flag has the issue not becoming updated properly in the Rules column.

I first noticed it now in PL 9.7.0.2, but don't know / can't exclude that this was already the case in earlier versions / Betas.

My system: Win10 Pro, 1909.

Many thanks for fixing this.

I tried to reproduce but it works on my end.
Will test more.

This is my config file if it helps.

[Administration]
Version=4630100
ConfigPasswordMD5=
[OutOfControlProcessRestraint]
OocOn=true
ExcludeChildrenOfActiveForeground_2=false
DisableProBalanceWhenSysIdle=false
ProBalanceDropOneRandomCore=false
OocDisableCoreParkingWhileIn=false
DisableProBalanceIfSysIdleThisManyMS=30000
TotalProcessorUsageBeforeRestraint=9
PerProcessUsageBeforeRestraint=7
TimeOverQuotaBeforeRestraint=1100
PerProcessUsageForRestore=3
PlayOnRestraint=C:\WINDOWS\media\Windows Pop-up Blocked.wav
PlayOnRestore=C:\WINDOWS\media\Windows Feed Discovered.wav
MinimumTimeOfRestraint=4200
MaximumTimeOfRestraint=0
TameOnlyNormal=true
LowerToIdleInsteadOfBelowNormal=false
ExcludeServices=true
PlaySoundOnRestraint=false
PlaySoundOnRestore=false
RestrainByAffinity=false
RestraintAffinity=
ExcludeForegroundProcesses=true
DoNotLowerPriorityClass=false
RoundRobinAffinitySelection=false
LowerIOPriorityDuringRestraint=false
MatchExclusionsByPathnameToo=false
OocExclusions=
OocHardCodedExclusionOverrides=
[GUI]
ClearLogAtExit=false
ShowGraphLegend=true
ShowGraphCPU=true
ShowGraphResponsiveness=true
ShowGraphMemoryLoad=true
ShowGraphProBalanceEvents=true
ShowGraphSelectedProcessesCPUHistory=true
ProBalanceCountersOnGraph=true
ShowGraphLicenseName=true
[Advanced]
AutomaticUpdate=false
RoundRobinSkipCore0=false
[Performance]
DefaultsLevel=327942
GracefulWaitTimeInMs=5000
UpdateSpeedGUI=1000
UpdateSpeedCore=1000
ManageOnlyCurrentUser=false
ExitOnCloseWindow=false
SoundsOff=true
AggressivelyTrimProcessLassoWorkingSet=true
IsConfigWritable=true
ForcedMode=false
IgnoreProtectedProcesses=true
HideSuspendedProcesses2=false
[ForegroundBoosting]
BoostForegroundThread=false
BoostForegroundProcess=false
ForegroundBoostExclusions=
[SystemTrayIcon]
UseStaticIcon=false
ShowResponsivnessInTrayInsteadOfProcessorUsage=false
[Logging]
LogDisable=false
LogSmartTrim=true
LogCPULimiter=true
LogEmitCSV=false
LogPruning=true
LogProBalanceParkingChanges=true
LogProcessExecutions=false
LogProcessTerminations=false
LogProcessesDisallowed=true
LogDefaultPriorityAdjustments=true
LogDefaultAffinityAdjustments=true
LogProBalanceBegin=true
LogProBalanceEnd=true
LogInstanceLimitTerminations=true
LogPowerProfileChanges=true
[MemoryManagement]
SmartTrimIsEnabled=true
SmartTrimWorkingSetTrims=false
SmartTrimClearStandbyList=false
ClearStandbyFreeRAMThresholdMB=1024
ClearStandbyOnlyInPerfMode=true
SmartTrimAutoMinimumRAMLoad=65
MinimumProcessWSSInMb=196
SmartTrimIntervalMins=15
[SysTrayBalloons]
EnableSystemTrayNotification=false
BalloonTipDuration=10000
ShowBalloonsForOocPriorityRestoration=false
[ProcessAllowances]
ApplyInstanceCountLimitsToAllUsers=false
AllowedProcesses=
DisallowedProcesses=
InstanceLimitedProcesses=
InstanceManagedCPUAffinities=
ProcessThrottles=
OneTimeProcessThrottles=
CPULimitRules=
[ProcessDefaults]
DefaultPriorities=x4.exe,above normal,game.exe,above normal
DefaultIOPriorities=x4.exe,3
DefaultMemoryPriorities=
DisableThreadPriorityBoost=
DefaultAffinities=x4.exe,4-11
KeepRunningProcesses=
MatchWildcardsToPathnames=true
MatchOnCommandLine=false
[AdvancedRules]
DivideCPUPercentThresholdsBySystemCPUCount=false
ProcessorGroupExtended=
WatchdogRules2=
[GamingMode]
GamingModeEnabled=false
GamingChangePowerPlan=true
TargetPowerPlan=Bitsum Highest Performance
GamingModeEngageForSteam=true
AutomaticGamingModeProcessPaths=c:\program files (x86)\steam\steamapps\common\star conflict\win64\game.exe
[MemoryManagement]
SmartTrimExclusions=
[PowerManagement]
Display=x4.exe,game.exe
PC=
[PowerSaver]
ShowNotificationWhenActivePowerSchemeChanges=true
[ProcessDefaults]
DefaultPowerSchemes=freefilesync_x64.exe;bitsum highest performance,x4.exe;bitsum highest performance,game.exe;bitsum highest performance,sidebar.exe;ausbalanciert
[PowerSaver]
PowerSaver_IdleTime=4
EnergySaverEnabled=true
EnergySaverForceActivePowerProfile=false
EnergySaverUpPowerProfileName=
EnergySaverEvents=true
DisableEnergySaverDuringGamingMode=true
PowerSaver_TargetGUID=Energiesparmodus
PowerSaver_Exclusions=

Ok, I was able to reproduce.
BTW your config is fine.

I'll fix that in the near future, thanks for pointing it out.

The Active Processes tab wasn't given much love until the last few months, and this quirk is just something I missed.

Hi,

one process has assigned "Bitsum highest performance" energy profile and also "Induce Performance Mode" has been set,
but PL Pro stays at "Balanced".

I tried to toggle "induce performance mode" to see, whether this brings a change to performance mode -> Bitsum highest Performance.
But when disabling this option I get this error message:
"There was an error removing from the automatic Performance Mode list the path '<path_to_the_executeable>'

Next I tried to disable a power profile from the process, works and re-assigned Bitsum highest Performance.
But what happens now .. Idlesaver seems to activate Energy Saving .. hello whats this ?!

Then I try to actively enable Performance mode from the GUI under "Main -> Performance Mode enabled".
But nothing happens, the PC stays at energy saving.

Remember, for settings I am using now my user directory so permission problems should be excluded.
K:\andreas\Eigene Dokumente\process lasso\config\prolasso.ini has a timestamp of this morning, so this should work.

These settings have been performed also from the TAB "active processes" if this might be important here as well.

Win10 1909, latest Patchlevel, PL Pro 9.7.0.2.

Quote from: ranko on February 21, 2020, 02:39:44 AM
Hi,

one process has assigned "Bitsum highest performance" energy profile and also "Induce Performance Mode" has been set,
but PL Pro stays at "Balanced".

I tried to toggle "induce performance mode" to see, whether this brings a change to performance mode -> Bitsum highest Performance.
But when disabling this option I get this error message:
"There was an error removing from the automatic Performance Mode list the path '<path_to_the_executeable>'

Next I tried to disable a power profile from the process, works and re-assigned Bitsum highest Performance.
But what happens now .. Idlesaver seems to activate Energy Saving .. hello whats this ?!

Then I try to actively enable Performance mode from the GUI under "Main -> Performance Mode enabled".
But nothing happens, the PC stays at energy saving.

Remember, for settings I am using now my user directory so permission problems should be excluded.
K:\andreas\Eigene Dokumente\process lasso\config\prolasso.ini has a timestamp of this morning, so this should work.

These settings have been performed also from the TAB "active processes" if this might be important here as well.

Win10 1909, latest Patchlevel, PL Pro 9.7.0.2.

Hi
When you say "one process has assigned "Bitsum highest performance" energy profile" do you mean using option "application process power plan" or "idlesaver" option?

You should never use performance mode "and" application power plan on the same process.
Idlesaver should work ok as there is an option to turn it off when performance mode is on.

Oh, you can't disable performance mode manually from the main menu if a process is running and set to performance mode, you would need to close it, but then power plan should go to default plan.

The error message can come up if the triggered path of the process used wildcard options, in other words, PL doesn't know the true path.

I look into your other comments.

I completely wiped my configuration by removing all files and directories.
It doesn't work anymore to assign X4.exe the Application Power Profile "Bitsum Highest Performance".

Active processes TAB -> Rightclick on X4.exe -> Application Power Profile -> Bitsum Highest Performance

According to the pulldown menue Bitsum Highest Performance mode is selected / configured, BUT the actual power profile doesn't change.
Even worse, Idlesaver is entering Energy Safing Mode, ALTHOUGH, I am just typing like hell.

So bad it never worked before.

Manually clobbering everything like that should not be necessary. Use the 'Options / Reset all configuration' menu item instead.

Ed was trying to explain that rule conflicts are possible, where one rule says be in power plan X, and another indicates to be in power plan Y. It is unclear whether that is part of what you are seeing. However, you did have a rule for sidebar.exe to enter your Balanced power plan. That could be the cause of staying in Balanced. Check the log.

The only way IdleSaver would malfunction and engage despite your user I/O activity would be if the new session agent isn't running (bitsumsessionagent.exe). Check and make sure it is. I don't know why it wouldn't be.

Of course, there is a difference between IdleSaver actually engaging, as would be indicated in the log, and your PC entering the Energiesparmodus (or whichever) power plan through other means, inadvertently or not.

Strange, one time after new installation and full reset of option I had a strange issue, of starting a steam game, performance mode became enganged (although I did a full reset of options) and when enabling IDLE saver the energy profile Energy Saving was used although performance mode was set, so what I want to say, Bitsum Highest Performance has been left, although it should not.

Then I quit game, steam app and hit another time full reset of options and then it worked all properly.
The only strange thing is after full reset (Options: Reset all configurations to default)
- Pro Balance is enabled, is that correct after full reset ?
- When starting a steam game, Bitsum highest Performance is being enabled, although I didn't configure to do so.
- Furthermore, I do not find this option to auto recognize Steam and enter Performance Mode automatically
   anymore in the GUI after switching to "run as a service".

Questions:
1. Is the configuration now fully managed in the file K:\me\Eigene Dokumente\process lasso\config\processlasso.ini ?
2. Where is the configuration picked up from that enables Performance Mode for steam application ?
    There is no config file anymore under
    C:\Users\Administrator\AppData\Roaming\ProcessLasso
    C:\Users\me\AppData\Roaming\ProcessLasso
3. Is the location of the config file being stored in registry or where ?

Quote from: ranko on February 25, 2020, 01:13:08 AM
Strange, one time after new installation and full reset of option I had a strange issue, of starting a steam game, performance mode became enganged (although I did a full reset of options) and when enabling IDLE saver the energy profile Energy Saving was used although performance mode was set, so what I want to say, Bitsum Highest Performance has been left, although it should not.

Then I quit game, steam app and hit another time full reset of options and then it worked all properly.
The only strange thing is after full reset (Options: Reset all configurations to default)
- Pro Balance is enabled, is that correct after full reset ?
- When starting a steam game, Bitsum highest Performance is being enabled, although I didn't configure to do so.
- Furthermore, I do not find this option to auto recognize Steam and enter Performance Mode automatically
   anymore in the GUI after switching to "run as a service".

Questions:
1. Is the configuration now fully managed in the file K:\me\Eigene Dokumente\process lasso\config\processlasso.ini ?
2. Where is the configuration picked up from that enables Performance Mode for steam application ?
    There is no config file anymore under
    C:\Users\Administrator\AppData\Roaming\ProcessLasso
    C:\Users\me\AppData\Roaming\ProcessLasso
3. Is the location of the config file being stored in registry or where ?

Hi
1) Probalance is always set on by default.
2)auto steam enabled option is in the menu, Options>power>Performance mode.
There you will see options for a) enable steam "attempt automatic detection", b) "Disable idlesaver while the game is running", c) "Change power plan when engaged".

All three of those are enabled by default.
Most of all user process config options are in the prolasso.ini file but some are in reg for certain program settings of PL but not process settings (like GUI size, column sizes etc).

On config rest, it is appropriate for ProBalance to be enabled, as well as automatic game detection /w Performance Mode. So that sounds right.

Quote from: ranko on February 25, 2020, 01:13:08 AM1. Is the configuration now fully managed in the file K:\me\Eigene Dokumente\process lasso\config\processlasso.ini ?

Yes

Quote
2. Where is the configuration picked up from that enables Performance Mode for steam application ?

The config file. GamingModeEngageForSteam key.

Quote
3. Is the location of the config file being stored in registry or where ?

Yes, the registry. HKLM\Software\ProcessLasso

I do not know how to say it, PL Pro doesn't run reliable anymore.
Yesterday I had some strange situation, but later it ran well and I thought now I am through it .. everything resolved by proper resetting. Playing X4 foundation issues Performance Mode .. thats it.

Now I come back from work and after boot nothing works anymore.

1. Balanced Power Profile has not been restored properly
2. When starting a Steam game nothing happens, performance mode has not being set
3. Needed to manually set balanced power profile in windows
4. Tried to enable performance mode by rightclicking the icon in the bottom riight PL Pro icon in the Windows Info area.
    I can not enable it. It doesnt work.
5. Looked under the active processes "Induce Performance Mode" is set.

Thats my config file.
[Administration]
Version=4640100
ConfigPasswordMD5=
[OutOfControlProcessRestraint]
OocOn=true
ExcludeChildrenOfActiveForeground_2=false
DisableProBalanceWhenSysIdle=false
ProBalanceDropOneRandomCore=false
OocDisableCoreParkingWhileIn=false
DisableProBalanceIfSysIdleThisManyMS=30000
TotalProcessorUsageBeforeRestraint=9
PerProcessUsageBeforeRestraint=7
TimeOverQuotaBeforeRestraint=1100
PerProcessUsageForRestore=3
PlayOnRestraint=C:\WINDOWS\media\Windows Pop-up Blocked.wav
PlayOnRestore=C:\WINDOWS\media\Windows Feed Discovered.wav
MinimumTimeOfRestraint=4200
MaximumTimeOfRestraint=0
TameOnlyNormal=true
LowerToIdleInsteadOfBelowNormal=false
ExcludeServices=true
PlaySoundOnRestraint=false
PlaySoundOnRestore=false
RestrainByAffinity=false
RestraintAffinity=
ExcludeForegroundProcesses=true
DoNotLowerPriorityClass=false
RoundRobinAffinitySelection=false
LowerIOPriorityDuringRestraint=false
MatchExclusionsByPathnameToo=false
OocExclusions=
OocHardCodedExclusionOverrides=
[GUI]
ClearLogAtExit=false
ShowGraphLegend=true
ShowGraphCPU=true
ShowGraphResponsiveness=true
ShowGraphMemoryLoad=true
ShowGraphProBalanceEvents=true
ShowGraphSelectedProcessesCPUHistory=true
ProBalanceCountersOnGraph=true
ShowGraphLicenseName=true
[Advanced]
AutomaticUpdate=false
RoundRobinSkipCore0=false
[Performance]
DefaultsLevel=327942
GracefulWaitTimeInMs=5000
UpdateSpeedGUI=1000
UpdateSpeedCore=1000
ManageOnlyCurrentUser=false
ExitOnCloseWindow=false
SoundsOff=true
AggressivelyTrimProcessLassoWorkingSet=true
IsConfigWritable=true
ForcedMode=false
IgnoreProtectedProcesses=true
HideSuspendedProcesses2=false
[ForegroundBoosting]
BoostForegroundThread=false
BoostForegroundProcess=false
ForegroundBoostExclusions=
[SystemTrayIcon]
UseStaticIcon=false
ShowResponsivnessInTrayInsteadOfProcessorUsage=false
[Logging]
LogDisable=false
LogSmartTrim=true
LogCPULimiter=true
LogEmitCSV=false
LogPruning=true
LogProBalanceParkingChanges=true
LogProcessExecutions=false
LogProcessTerminations=false
LogProcessesDisallowed=true
LogDefaultPriorityAdjustments=true
LogDefaultAffinityAdjustments=true
LogProBalanceBegin=true
LogProBalanceEnd=true
LogInstanceLimitTerminations=true
LogPowerProfileChanges=true
[MemoryManagement]
SmartTrimIsEnabled=true
SmartTrimWorkingSetTrims=false
SmartTrimClearStandbyList=false
ClearStandbyFreeRAMThresholdMB=1024
ClearStandbyOnlyInPerfMode=true
SmartTrimAutoMinimumRAMLoad=65
MinimumProcessWSSInMb=196
SmartTrimIntervalMins=15
[SysTrayBalloons]
EnableSystemTrayNotification=false
BalloonTipDuration=10000
ShowBalloonsForOocPriorityRestoration=false
[ProcessAllowances]
ApplyInstanceCountLimitsToAllUsers=false
AllowedProcesses=
DisallowedProcesses=
InstanceLimitedProcesses=
InstanceManagedCPUAffinities=
ProcessThrottles=
OneTimeProcessThrottles=
CPULimitRules=
[ProcessDefaults]
DefaultPriorities=x4.exe,above normal
DefaultIOPriorities=x4.exe,3
DefaultMemoryPriorities=
DisableThreadPriorityBoost=
DefaultAffinities=x4.exe,4-11
KeepRunningProcesses=
MatchWildcardsToPathnames=true
MatchOnCommandLine=false
[AdvancedRules]
DivideCPUPercentThresholdsBySystemCPUCount=false
ProcessorGroupExtended=
WatchdogRules2=
[GamingMode]
GamingModeEnabled=false
GamingChangePowerPlan=true
TargetPowerPlan=Bitsum Highest Performance
GamingModeEngageForSteam=true
AutomaticGamingModeProcessPaths=c:\program files (x86)\steam\steamapps\common\x4 foundations\x4.exe
[MemoryManagement]
SmartTrimExclusions=
[PowerManagement]
Display=x4.exe
PC=
[PowerSaver]
ShowNotificationWhenActivePowerSchemeChanges=false
[ProcessDefaults]
DefaultPowerSchemes=x4.exe;bitsum highest performance
[PowerSaver]
PowerSaver_IdleTime=5
EnergySaverEnabled=true
EnergySaverForceActivePowerProfile=false
EnergySaverUpPowerProfileName=
EnergySaverEvents=true
DisableEnergySaverDuringGamingMode=true
PowerSaver_TargetGUID=Energiesparmodus
PowerSaver_Exclusions=



Sorry I don't know whats going on here of all sudden.

Check to ensure the governor is actually running. It sounds like it isn't.

You should see processgovernor.exe running in the SYSTEM context. Of course, you'll need to elevate Process Lasso to see it.

Similarly, the Services console should list the Process Governor and it should be set to auto-start (and started).

Of course, you should have been notified if the governor isn't running, so it isn't clear to me if this is the issue, or how such a situation would arise.

Thanks for your kind reply.

So you say this is something which should not happen and you think that the process governor is not running...

If I may do a proposal: I think it would be beneficial for you and the end user to get quickly information about,
whether core components of PL Pro are running or not.

Could this status information perhaps be included into the information in the Windows Info field,
either when doing a mouse over or maybe also when performing a right-click ?

Quote from: ranko on February 26, 2020, 05:58:25 AM
Thanks for your kind reply.

So you say this is something which should not happen and you think that the process governor is not running...

If I may do a proposal: I think it would be beneficial for you and the end user to get quickly information about,
whether core components of PL Pro are running or not.

Could this status information perhaps be included into the information in the Windows Info field,
either when doing a mouse over or maybe also when performing a right-click ?

Menu Help> About Process lasso lists info on config and log paths, along with version and Language.

And how is this related to my question / proposal ? Do you want it to place there ?

Its relatively complicated having to open the GUI 1st and then having to click to About.

Therefore my idea to place it there to easily identify whether all needed processes are there ..

Quote from: ranko on February 26, 2020, 08:23:56 AM
And how is this related to my question / proposal ? Do you want it to place there ?

Its relatively complicated having to open the GUI 1st and then having to click to About.

Therefore my idea to place it there to easily identify whether all needed processes are there ..

It has nothing to do with your proposal, I was just giving info on how to find paths of config and log (that shouldn't change with use).

Jeremy will comment on your proposal as he is the one coding (I am just a tester).
Maybe we could add something in the GUI graph, Like gov enabled, the thing is their limited room.

I also tried to reproduce your last issue but couldn't and not sure what's going on, if gov was not running you should see red system tray icon showing it is not running.

Thanks for the feedback we will test this more, just need to find the right conditions.

Quote from: ranko on February 26, 2020, 05:58:25 AM
If I may do a proposal: I think it would be beneficial for you and the end user to get quickly information about,
whether core components of PL Pro are running or not.

It should already notify you if the governor isn't running by graph overlay text and a change to the system tray icon (to a big red X thing).

Adding additional status info is certainly a possibility, though isn't generally necessary since the governor should be running under nominal conditions unless the user stopped it. If it is somehow crashing, then absolutely that needs triaged. If you do find it to not be running, let me know.

It is not clear this was/is the issue(s) with varying functionality you see though, I just don't have a better explanation at this time (and haven't heard or seen anything similar).

Today the system doesn't leave Energy saving mode anymore even under load.

In earlier versions the Power Profile was properly remembered on reboots.

Why not anymore ? Is there an option that I overlooked ?

Do I need to perform "trickeries" now to select one process that brings always Balanced Power Profile,
unless either IDLE Saver chooses "Energy Saving" or Performance Mode is being activated by Steam ?

Windows is responsible for remembering the power plan across a reboot. Therefore, it will depend on what the power plan was when it shut down, and that could vary based on timing with IdleSaver or other power rules.

Your reports have led to many important product improvements, so I appreciate that.

If I understand your last question: After setting an app power plan to Balanced, IdleSaver should still take precedence and act nominally. For Performance Mode, I'll have to evaluate the logic and get back to you to ensure I give a precise answer (but it should also take precedence, my concern is about process launch order).

Quick update.
Starting steam game X4.exe
Bitsum Highest Performance is being used.
Then of all sudden it falls back to Balanced.
Opening PL Pro GUI, TAB Active Processes, Rightclick to X4.exe
Application Profile -> Bitsum Highest Performance is selected.
Induce Performance Mode is also seleced.
But the result of this all is Balanced.
IDLEsaver does not work. Sure, because of Performance mode and because Bitsum Highest Performance has been selected for 1 process.
But the result is Balanced and not Bitsum Highest Performance.

Previously, the Performance Mode wasn't manually toggling for you because of a remaining limited user + service issue. It will work going forward.

The variance in behavior you observed was due to the GUI sometimes running elevated (after updates or install), and other times not (e.g. after auto-start).

Additionally, related or not, I have been able to replicate one problematic scenario related to the combination of manual invocation of Performance Mode and automatic (rule based) induction. Update: This is now fixed in latest beta.

1. Start in Balanced profile
2. Set test process to 'Induce Performance Mode'
3. Manually engage Performance Mode (switches to BHP)
4. Run test process.
5. Exit test process.
6. Power plan inappropriately set to Balanced.
7. Run test process.
8. Power plan remains inappropriately in Balanced.

Also note that, to be sure, we'll need to check your system for any other software that may be changing the power plan. These events are recorded in the Windows Event log.

You should also paste your Process Lasso log entries when this occurs. You can select all/multiple rows in the Log Viewer.

As an aside, 'Options / Forced mode' may help.

Hi guys,
hope you are well. Sorry I did not have much time the last weeks.
I entirely switched to Windows 10 and switched back to Process Lasso -STABLE train, currently using 9.7.5.44.

I noticed three problems:

1. Steam detection stays in "performance mode", even if the game ended.
    The bad thing: as a result of this "IDLE saver" does not work anymore because performance mode is still enganged.

Therefore I disabled Steam detection and simply configured everything that I need based on the X4.exe binary and get a 2nd problem.

2. X4.exe has been startet, in PL under active processes you see all the applied PL features in the rules column.
And although I configured, that the Power Profile "Bitsum Highest Performance" should "Always" be used for X4.exe
the Power Profile stays at "balanced" and "performance mode" is not being activated.
I noticed in the PL log that the power profile has not been changed.
And I see it also in the Windows Gadget, that the Profile stays at "Balanced", otherwise on unknown power profiles the Gadget would have shown nothing.
It only displays the three Windows default profiles or "nothing" = dark, nothing is lit.

3. Sometimes during gaming I notice that PC is in IDLE mode

4. After disabling Steam game detection mode and configuring all based on the X4 executeable "X4.exe" sometimes PC stays in balanced power profile.
I tried "forced mode" but this didn't change anything.
I stopped and restarted X4.exe then it worked, that Bitsum Highest Priority / Performance mode became active.

You can see it in this screenshot:
(https://www.dropbox.com/s/61iv8h89qwnv8go/2020-04-26%2009_02_21-X4-does-not-enter-bitsum-performance-mode.jpg?dl=1)

Question 1: is that correct behaviour, that performance mode stays on after a steam game has ended ?

If I remember right then it worked already "correct" in the past, that
- an ending steam game brings power profile back to balanced
- after the configured IDLE timer the PC is being set to IDLE
- that during a game IDLE saver does not put the PC into the chosen power profile "power saving"

Question 2: Or did I remember wrong, that Steam detection always worked based on recognition of the steam executable that you see in the Windows info bar.
But that would be bad, because in default installation it will be started automatically.
I tweaked it already by disabling the startup entry, but it will startup once I start a steam game and then runs in the background.

Question 3: is it still required under Win10, to fully install PL after update ? We had an issue where front/backend were out of sync, something didnt work,
and then you asked me to perform an over-installation of the real installer. Or do the update procedures work under Win10 ?

Question 4: I can't remember having worked with profiles in my new setup after reinstallation. Why do I have two different prolasso.ini files ?
According to the time stamps both become updated.

I am running PL in service mode and the config is in a folder under "documents" that I fully own.
Here is my current config:

<VOL>:\name\Eigene Dokumente\process lasso\configs\prolasso.ini

[Administration]
Version=4680500
ConfigPasswordMD5=
[OutOfControlProcessRestraint]
OocOn=true
ExcludeChildrenOfActiveForeground_2=false
DisableProBalanceWhenSysIdle=false
ProBalanceDropOneRandomCore=false
OocDisableCoreParkingWhileIn=false
DisableProBalanceIfSysIdleThisManyMS=30000
TotalProcessorUsageBeforeRestraint=9
PerProcessUsageBeforeRestraint=7
TimeOverQuotaBeforeRestraint=1100
PerProcessUsageForRestore=3
PlayOnRestraint=C:\Windows\media\Windows Pop-up Blocked.wav
PlayOnRestore=C:\Windows\media\Windows Feed Discovered.wav
MinimumTimeOfRestraint=4200
MaximumTimeOfRestraint=0
TameOnlyNormal=true
LowerToIdleInsteadOfBelowNormal=false
ExcludeServices=true
PlaySoundOnRestraint=false
PlaySoundOnRestore=false
RestrainByAffinity=false
RestraintAffinity=
ExcludeForegroundProcesses2=true
DoNotLowerPriorityClass=false
RoundRobinAffinitySelection=false
LowerIOPriorityDuringRestraint=false
MatchExclusionsByPathnameToo=false
OocExclusions=
OocHardCodedExclusionOverrides=
[GUI]
ClearLogAtExit=false
ShowGraphLegend=true
ShowGraphCPU=true
ShowGraphResponsiveness=true
ShowGraphMemoryLoad=true
ShowGraphProBalanceEvents=true
ShowGraphSelectedProcessesCPUHistory=true
ProBalanceCountersOnGraph=true
ShowGraphLicenseName=true
[Advanced]
AutomaticUpdate=false
RoundRobinSkipCore0=false
[Performance]
DefaultsLevel=327942
GracefulWaitTimeInMs=5000
UpdateSpeedGUI=1000
UpdateSpeedCore=1000
ManageOnlyCurrentUser=false
ExitOnCloseWindow=false
SoundsOff=true
AggressivelyTrimProcessLassoWorkingSet=true
IsConfigWritable=true
ForcedMode=false
IgnoreProtectedProcesses=true
IgnoreSuspendedProcesses=false
[ForegroundBoosting]
BoostForegroundThread=false
BoostForegroundProcess=false
ForegroundBoostExclusions=
[SystemTrayIcon]
UseStaticIcon=false
ShowResponsivnessInTrayInsteadOfProcessorUsage=false
[Logging]
LogDisable=false
LogSmartTrim=true
LogCPULimiter=true
LogEmitCSV=false
LogPruning=true
LogProBalanceParkingChanges=true
LogProcessExecutions=false
LogProcessTerminations=false
LogProcessesDisallowed=true
LogDefaultPriorityAdjustments=true
LogDefaultAffinityAdjustments=true
LogProBalanceBegin=true
LogProBalanceEnd=true
LogInstanceLimitTerminations=true
LogPowerProfileChanges=true
[MemoryManagement]
SmartTrimIsEnabled=false
SmartTrimWorkingSetTrims=false
SmartTrimClearStandbyList=false
ClearStandbyFreeRAMThresholdMB=1024
ClearStandbyOnlyInPerfMode=true
SmartTrimAutoMinimumRAMLoad=65
MinimumProcessWSSInMb=196
SmartTrimIntervalMins=15
[SysTrayBalloons]
EnableSystemTrayNotification=false
BalloonTipDuration=10000
ShowBalloonsForOocPriorityRestoration=false
[ProcessAllowances]
ApplyInstanceCountLimitsToAllUsers=false
AllowedProcesses=
DisallowedProcesses=
InstanceLimitedProcesses=
InstanceManagedCPUAffinities=
ProcessThrottles=
OneTimeProcessThrottles=
CPULimitRules=
[ProcessDefaults]
DefaultPriorities=
DefaultIOPriorities=
DefaultMemoryPriorities=
DisableThreadPriorityBoost=
DefaultAffinities=
KeepRunningProcesses=
MatchWildcardsToPathnames=true
MatchOnCommandLine=false
[AdvancedRules]
DivideCPUPercentThresholdsBySystemCPUCount=false
ProcessorGroupExtended=
WatchdogRules2=
[GamingMode]
GamingModeEnabled=false
GamingChangePowerPlan=true
TargetPowerPlan=Bitsum Highest Performance
GamingModeEngageForSteam=true
AutomaticGamingModeProcessPaths=
[MemoryManagement]
SmartTrimExclusions=
[PowerManagement]
Display=
PC=
[PowerSaver]
ShowNotificationWhenActivePowerSchemeChanges=true
PowerSaver_IdleTime=0
EnergySaverEnabled=false
EnergySaverForceActivePowerProfile=false
EnergySaverUpPowerProfileName=
EnergySaverEvents=true
DisableEnergySaverDuringGamingMode=true
PowerSaver_Exclusions=

<VOL>:\name\Eigene Dokumente\process lasso\configs\<SUBDIR>\prolasso.ini:

[Administration]
Version=4630100
ConfigPasswordMD5=
[OutOfControlProcessRestraint]
OocOn=true
ExcludeChildrenOfActiveForeground_2=false
DisableProBalanceWhenSysIdle=false
ProBalanceDropOneRandomCore=false
OocDisableCoreParkingWhileIn=false
DisableProBalanceIfSysIdleThisManyMS=30000
TotalProcessorUsageBeforeRestraint=9
PerProcessUsageBeforeRestraint=20
TimeOverQuotaBeforeRestraint=1100
PerProcessUsageForRestore=3
PlayOnRestraint=C:\Windows\media\Windows Pop-up Blocked.wav
PlayOnRestore=C:\Windows\media\Windows Feed Discovered.wav
MinimumTimeOfRestraint=4200
MaximumTimeOfRestraint=0
TameOnlyNormal=true
LowerToIdleInsteadOfBelowNormal=false
ExcludeServices=true
PlaySoundOnRestraint=false
PlaySoundOnRestore=false
RestrainByAffinity=false
RestraintAffinity=
ExcludeForegroundProcesses=true
DoNotLowerPriorityClass=false
RoundRobinAffinitySelection=false
LowerIOPriorityDuringRestraint=false
MatchExclusionsByPathnameToo=false
OocExclusions=
OocHardCodedExclusionOverrides=
[GUI]
ClearLogAtExit=false
ShowGraphLegend=true
ShowGraphCPU=true
ShowGraphResponsiveness=true
ShowGraphMemoryLoad=true
ShowGraphProBalanceEvents=true
ShowGraphSelectedProcessesCPUHistory=true
ProBalanceCountersOnGraph=true
ShowGraphLicenseName=true
[Advanced]
AutomaticUpdate=false
RoundRobinSkipCore0=false
[Performance]
DefaultsLevel=327942
GracefulWaitTimeInMs=1000
UpdateSpeedGUI=1000
UpdateSpeedCore=1000
ManageOnlyCurrentUser=false
ExitOnCloseWindow=false
SoundsOff=true
AggressivelyTrimProcessLassoWorkingSet=true
IsConfigWritable=true
ForcedMode=false
IgnoreProtectedProcesses=true
HideSuspendedProcesses2=false
[ForegroundBoosting]
BoostForegroundThread=false
BoostForegroundProcess=false
ForegroundBoostExclusions=
[SystemTrayIcon]
UseStaticIcon=false
ShowResponsivnessInTrayInsteadOfProcessorUsage=false
[Logging]
LogDisable=false
LogSmartTrim=true
LogCPULimiter=true
LogEmitCSV=false
LogPruning=true
LogProBalanceParkingChanges=false
LogProcessExecutions=false
LogProcessTerminations=false
LogProcessesDisallowed=true
LogDefaultPriorityAdjustments=true
LogDefaultAffinityAdjustments=true
LogProBalanceBegin=true
LogProBalanceEnd=true
LogInstanceLimitTerminations=true
LogPowerProfileChanges=true
[MemoryManagement]
SmartTrimIsEnabled=false
SmartTrimWorkingSetTrims=false
SmartTrimClearStandbyList=false
ClearStandbyFreeRAMThresholdMB=0
ClearStandbyOnlyInPerfMode=true
SmartTrimAutoMinimumRAMLoad=65
MinimumProcessWSSInMb=196
SmartTrimIntervalMins=15
[SysTrayBalloons]
EnableSystemTrayNotification=false
BalloonTipDuration=10000
ShowBalloonsForOocPriorityRestoration=false
[ProcessAllowances]
ApplyInstanceCountLimitsToAllUsers=false
AllowedProcesses=
DisallowedProcesses=
InstanceLimitedProcesses=
InstanceManagedCPUAffinities=
ProcessThrottles=
OneTimeProcessThrottles=
CPULimitRules=
[ProcessDefaults]
DefaultPriorities=x4.exe,above normal
DefaultIOPriorities=x4.exe,3
DefaultMemoryPriorities=
DisableThreadPriorityBoost=
DefaultAffinities=x4.exe,1-11
KeepRunningProcesses=
MatchWildcardsToPathnames=true
MatchOnCommandLine=false
[AdvancedRules]
DivideCPUPercentThresholdsBySystemCPUCount=false
ProcessorGroupExtended=
WatchdogRules2=
[GamingMode]
GamingModeEnabled=false
GamingChangePowerPlan=true
TargetPowerPlan=Bitsum Highest Performance
GamingModeEngageForSteam=true
AutomaticGamingModeProcessPaths=
[MemoryManagement]
SmartTrimExclusions=
[PowerManagement]
Display=x4.exe
PC=
[PowerSaver]
ShowNotificationWhenActivePowerSchemeChanges=true
[ProcessDefaults]
DefaultPowerSchemes=x4.exe;bitsum highest performance
[PowerSaver]
PowerSaver_IdleTime=0
EnergySaverEnabled=false
EnergySaverForceActivePowerProfile=false
EnergySaverUpPowerProfileName=
EnergySaverEvents=true
DisableEnergySaverDuringGamingMode=true
PowerSaver_Exclusions=

Wait .. I started over to have this all a little bit more controlled, not that some weired old config stuff is present
and to make it better reproduceable for you.

What I did:
- deinstalled PL
- removed all config file stuff <VOL>:\name\Eigene Dokumente\process lasso\{configs,log}
- installed PL 9.7.5.44
- used default parameters except customized configuration folder: <VOL>:\name\Eigene Dokumente\process lasso\{config,log}
- re-activated license for Pro version
- rebooted system

The 1st thing that I noticed after fresh reboot and loggin in is:
Without having configured anything on my own, that the system switched to "performance mode".

Process Name: steamwebhelper.exe
Action: Automatic Performance Mode ON
Automatic Performance Mode was turned on because a specific game process was found running.

I think it is not useful to enter performance mode only because steam starts up some supportive background services.

Wondering, didn't it work already properly in the past ?!

But Steam is not the only content provider for games. So I would propose to call this feature "Gaming Mode".

In "gaming mode" the machine should enter a configurable power profile, default: "Bitsum Highest Performance".

In the config section for gaming mode the user can
- maintain a list of full paths to game executeables and/or regular expression for process names
- enable steam detection by one or more customizeable regular expressions, default: "steamapps/common"

Even support for different Steam Libraries (which is supported by steam if you run out of diskspace) would be supported by this automatically, because I assume that in each of the configured Steam libraries there will be such a subfolder "steamapps/common" or another regular expression will catch all other cases. Even if you have another known directory structure with games like "G:\games".

Steamwebhelper.exe should not induce performance mode. The last user to report that had accidentally added steamwebhelper.exe to their automatic gaming list, but I don't think that is the case with you. I'll take a look and see if I can figure out how it could happen, and maybe prevent it from ever inducing even if it is in a user-configured gaming path.

You don't need to do anything special for updates. Those issues running as a Limited User were fixed.

Performance Mode used to be called Gaming Mode, but people use it for more than games, and I didn't want it to be confused with Windows Game Mode. So it isn't changing back ;).

Regular Expressions will eventually come to the Automatic Performance Mode list, though not for the next final version scheduled for May 1.

As for your two INI files, one may be a backup created in a previous update (no longer done), particularly if it is in that same folder. If it is in some other folder, then it is probably debris from past use.

Thanks for the feedback! Let me know if I missed any of your questions.

9.6.7 beta
(17) Core: Fix issue where Steam services could cause Automatic Game Detection Perf Mode to trigger under some circumstances

Today I noticed during gaming, that Performance Mode was not active although it was properly configured for X4.exe process.
I performed a right click and noticed performance mode enabled for this program.
As a result of this IDLE saver kicked in.
As soon as I moved my mouse again the energy profile switched back to Bitsum Highest Performance.
Could this kindly be fixed as it breaks the concept, that for certain programs I do not want IDLE saver to kick in ... those programs which have performance mode enabled and in IDLE saver I have the setting not to activate on performance mode.

Another issue: Updates -> include beta versions does not trigger this and I can not switch to Beta.
I am currently PL Pro NOT running as a service, as simple user process.
I try switching now to service mode.
OK .. after switching to service mode I can toggle again between getting Beta or not.
But ... is it ok, after switching now to Beta, that PL doesn't find a Beta version to update to ?
Again, I am running 9.7.6.26 and I can not switch to a beta.

I tried now to find out whats the last beta or whether the latest release is the latest and greatest.
Its not possible....
1st of all its not so easy to find information about the Beta, you need to know that you find it under "ChangeLog".
What I did the last month is to google for "Process Lasso Beta", because it was really hard to find this on your webserver,
because its kind of "hidden" on your Webserver under "ChangeLog".

Then under ChangeLog you do not tell what the latest Beta version is.
So currently I can not find out, whether there is a newer Beta Version.

Also you do not seem to maintain a separate ChangeLog for the beta version, which makes it hard to differentiate and follow
what has been introduced / fixed on the Release and What on the Beta Branch.

You also do not provide any version numbering in the file name.
Release versions, Beta versions, they all cary the same name. This is very irritating.

And now I would have to download and install the setup file that I get via the "download beta" link to find out whether the Beta is any newer ?

As of the release of 9.7.6.26 (5-2-2020) there are no beta's available yet.
To find version details, go to help menu >Visit Bitsum Technologies. Right in the center of the screen is the release version, then click on that and you get to DL beta or release page.
https://bitsum.com/changes/processlasso/

Well there is still something strange. I changed now back to run PL in service mode.

After clean reboot of system and fresh login the system enters balanced mode.
Thats ok, because I used sidebar.exe as trigger so that Balanced Energy profile is being used unless
- IDLE saver kicks in to lower the Energy Profile to -> "Energy Saving", if user was idle and as long as Performance Mode is not enabled
- A Program demands higher power profile -> Bitsum highest performance which sets performance mode to deactivate IDLE Saver

But this does not seem to work.
After entering Balanced mode I noticed per right mouse click to the PL icon in the Windows info area that Performance Mode is active.
And then the system changed to Bitsum Highest Performance but I see absolutely no indication for what reason.

In the PL log file I see:
processgovernor: Per request of process default the power plan is now Bitsum Highest Performance
But no entry for a certain program that issued this ...

What does "Per request of process default " mean ?

Here a screenshot and the config below.
I see no valid reason for PL changing into Bitsum Highest Performance power profile.

(https://www.dropbox.com/s/r1f8vp4ujahz0dm/2020-05-03%2017_01_29-Why-BitsumEnhancedPerf.jpg?dl=1)


[Administration]
Version=4780300
ConfigPasswordMD5=
[OutOfControlProcessRestraint]
OocOn=true
ExcludeChildrenOfActiveForeground_2=false
DisableProBalanceWhenSysIdle=false
ProBalanceDropOneRandomCore=false
OocDisableCoreParkingWhileIn=false
DisableProBalanceIfSysIdleThisManyMS=30000
TotalProcessorUsageBeforeRestraint=10
PerProcessUsageBeforeRestraint=7
TimeOverQuotaBeforeRestraint=1100
PerProcessUsageForRestore=3
PlayOnRestraint=C:\WINDOWS\media\Windows Pop-up Blocked.wav
PlayOnRestore=C:\WINDOWS\media\Windows Feed Discovered.wav
MinimumTimeOfRestraint=4200
MaximumTimeOfRestraint=0
TameOnlyNormal=true
LowerToIdleInsteadOfBelowNormal=false
ExcludeServices=true
PlaySoundOnRestraint=false
PlaySoundOnRestore=false
RestrainByAffinity=false
RestraintAffinity=
ExcludeForegroundProcesses2=true
DoNotLowerPriorityClass=false
RoundRobinAffinitySelection=false
LowerIOPriorityDuringRestraint=false
MatchExclusionsByPathnameToo=false
OocExclusions=
OocHardCodedExclusionOverrides=
[GUI]
ClearLogAtExit=false
ShowGraphLegend=true
ShowGraphCPU=true
ShowGraphResponsiveness=true
ShowGraphMemoryLoad=true
ShowGraphProBalanceEvents=true
ShowGraphSelectedProcessesCPUHistory=true
ProBalanceCountersOnGraph=true
ShowGraphLicenseName=true
[Advanced]
AutomaticUpdate=false
RoundRobinSkipCore0=false
[Performance]
DefaultsLevel=327942
GracefulWaitTimeInMs=5000
UpdateSpeedGUI=1000
UpdateSpeedCore=1000
ManageOnlyCurrentUser=false
ExitOnCloseWindow=false
SoundsOff=true
AggressivelyTrimProcessLassoWorkingSet=true
IsConfigWritable=true
ForcedMode=false
IgnoreProtectedProcesses=true
IgnoreSuspendedProcesses=false
[ForegroundBoosting]
BoostForegroundThread=false
BoostForegroundProcess=false
ForegroundBoostExclusions=
[SystemTrayIcon]
UseStaticIcon=false
ShowResponsivnessInTrayInsteadOfProcessorUsage=false
[Logging]
LogDisable=false
LogSmartTrim=true
LogCPULimiter=true
LogEmitCSV=false
LogPruning=true
LogProBalanceParkingChanges=true
LogProcessExecutions=false
LogProcessTerminations=false
LogProcessesDisallowed=true
LogDefaultPriorityAdjustments=true
LogDefaultAffinityAdjustments=true
LogProBalanceBegin=true
LogProBalanceEnd=true
LogInstanceLimitTerminations=true
LogPowerProfileChanges=true
[MemoryManagement]
SmartTrimIsEnabled=true
SmartTrimWorkingSetTrims=false
SmartTrimClearStandbyList=false
ClearStandbyFreeRAMThresholdMB=1024
ClearStandbyOnlyInPerfMode=true
SmartTrimAutoMinimumRAMLoad=65
MinimumProcessWSSInMb=196
SmartTrimIntervalMins=15
[SysTrayBalloons]
EnableSystemTrayNotification=false
BalloonTipDuration=10000
ShowBalloonsForOocPriorityRestoration=false
[ProcessAllowances]
ApplyInstanceCountLimitsToAllUsers=false
AllowedProcesses=
DisallowedProcesses=
InstanceLimitedProcesses=
InstanceManagedCPUAffinities=
ProcessThrottles=
OneTimeProcessThrottles=
CPULimitRules=
[ProcessDefaults]
DefaultPriorities=x4.exe,above normal
DefaultIOPriorities=x4.exe,3
DefaultMemoryPriorities=
DisableThreadPriorityBoost=
DefaultAffinities=x4.exe,1-11
KeepRunningProcesses=
MatchWildcardsToPathnames=true
MatchOnCommandLine=false
[AdvancedRules]
DivideCPUPercentThresholdsBySystemCPUCount=false
ProcessorGroupExtended=
WatchdogRules2=
[GamingMode]
GamingModeEnabled=false
GamingChangePowerPlan=true
TargetPowerPlan=Bitsum Highest Performance
GamingModeEngageForSteam=false
AutomaticGamingModeProcessPaths=c:\program files (x86)\steam\steamapps\common\shadow of the tomb raider\sottr.exe,c:\program files (x86)\steam\steamapps\common\star conflict\game.exe,c:\program files (x86)\steam\steamapps\common\star conflict\win64\game.exe,c:\program files (x86)\steam\steamapps\common\x4 foundations\x4.exe,c:\program files\freefilesync\freefilesync.exe
[MemoryManagement]
SmartTrimExclusions=
[PowerManagement]
Display=x4.exe
PC=
[PowerSaver]
ShowNotificationWhenActivePowerSchemeChanges=true
[ProcessDefaults]
DefaultPowerSchemes=sidebar.exe;ausbalanciert,x4.exe;bitsum highest performance
[PowerSaver]
PowerSaver_IdleTime=15
EnergySaverEnabled=true
EnergySaverForceActivePowerProfile=false
EnergySaverUpPowerProfileName=
EnergySaverEvents=true
DisableEnergySaverDuringGamingMode=true
PowerSaver_TargetGUID=Energiesparmodus
PowerSaver_Exclusions=

My guess is PL is getting confused, to many triggers.
Try removing all application power plans, just set idlesaver and performance mode ones, or us just application power plan and idlesaver. having all three can cause issues.

The log indicates that Process Lasso was previously shut down while Performance Mode had been manually engaged. When it started again, it resumed Performance Mode and switched back to Bitsum Highest Performance. This is done mostly for updates, so a user's manual entrance into Performance Mode isn't lost when the product updates itself. Yes, the log entry text is misleading.

Therefore, I suspect that Performance Mode being manually engaged is the source of your observation. Try unchecking Performance Mode manually in the Main menu of Process Lasso when you don't have a game also running.

Sorry I have not so much time for testing and troubleshooting at the moment.
I report you this with the aim, that you maybe check on your own, why in some situations PL Pro reacts different than one would expect.

One more wish / suggestion:

Since I moved to Win10 I have random audio drops even on an idle system.
Therefore I choosed for my MusicBee player with ASIO support to use Bitsum Highest Performance Profile.
By occasion I checked the settings of this power profile and see, that "USB selective suspend" is still enabled in your energy profile.

To my best knowledge and Windows tuning guides for DAWs (Digital Audio Workstations) its recommended to disable this
for computers with external USB audio devices. Could you kindly add this to your profile ?

That would be great to enhance the functionality of your power profile. Many thanks.

(https://cdn.windowsreport.com/wp-content/uploads/2017/10/usb-is-not-working-power-3.png)

There are still issues where "Induce performance mode" has been set by GUI for the executable "X4.exe"
but strangely it doesn't become active. IDLE saver kicks in and brings the machine from "Bitsum highest performance" to "energy saving".
And this should not be the case because in IDLE save I configured "Disable while performance mode is engaged".

So this is still not working reliably.

PL 9.7.6.26, being run as service. Gaming Mode with Steam detection intentionally turned off, because then the machine works at highest energy profile too early when steam service is detected but not game running ...

[Administration]
Version=4780300
ConfigPasswordMD5=
[OutOfControlProcessRestraint]
OocOn=true
ExcludeChildrenOfActiveForeground_2=false
DisableProBalanceWhenSysIdle=false
ProBalanceDropOneRandomCore=false
OocDisableCoreParkingWhileIn=false
DisableProBalanceIfSysIdleThisManyMS=30000
TotalProcessorUsageBeforeRestraint=10
PerProcessUsageBeforeRestraint=7
TimeOverQuotaBeforeRestraint=1100
PerProcessUsageForRestore=3
PlayOnRestraint=C:\WINDOWS\media\Windows Pop-up Blocked.wav
PlayOnRestore=C:\WINDOWS\media\Windows Feed Discovered.wav
MinimumTimeOfRestraint=4200
MaximumTimeOfRestraint=0
TameOnlyNormal=true
LowerToIdleInsteadOfBelowNormal=false
ExcludeServices=true
PlaySoundOnRestraint=false
PlaySoundOnRestore=false
RestrainByAffinity=false
RestraintAffinity=
ExcludeForegroundProcesses2=true
DoNotLowerPriorityClass=false
RoundRobinAffinitySelection=false
LowerIOPriorityDuringRestraint=false
MatchExclusionsByPathnameToo=false
OocExclusions=
OocHardCodedExclusionOverrides=
[GUI]
ClearLogAtExit=false
ShowGraphLegend=true
ShowGraphCPU=true
ShowGraphResponsiveness=true
ShowGraphMemoryLoad=true
ShowGraphProBalanceEvents=true
ShowGraphSelectedProcessesCPUHistory=true
ProBalanceCountersOnGraph=true
ShowGraphLicenseName=true
[Advanced]
AutomaticUpdate=false
RoundRobinSkipCore0=false
[Performance]
DefaultsLevel=327942
GracefulWaitTimeInMs=5000
UpdateSpeedGUI=1000
UpdateSpeedCore=1000
ManageOnlyCurrentUser=false
ExitOnCloseWindow=false
SoundsOff=true
AggressivelyTrimProcessLassoWorkingSet=true
IsConfigWritable=true
ForcedMode=true
IgnoreProtectedProcesses=true
IgnoreSuspendedProcesses=false
[ForegroundBoosting]
BoostForegroundThread=false
BoostForegroundProcess=false
ForegroundBoostExclusions=
[SystemTrayIcon]
UseStaticIcon=false
ShowResponsivnessInTrayInsteadOfProcessorUsage=false
[Logging]
LogDisable=false
LogSmartTrim=true
LogCPULimiter=true
LogEmitCSV=false
LogPruning=true
LogProBalanceParkingChanges=true
LogProcessExecutions=false
LogProcessTerminations=false
LogProcessesDisallowed=true
LogDefaultPriorityAdjustments=true
LogDefaultAffinityAdjustments=true
LogProBalanceBegin=true
LogProBalanceEnd=true
LogInstanceLimitTerminations=true
LogPowerProfileChanges=true
[MemoryManagement]
SmartTrimIsEnabled=true
SmartTrimWorkingSetTrims=false
SmartTrimClearStandbyList=false
ClearStandbyFreeRAMThresholdMB=1024
ClearStandbyOnlyInPerfMode=true
SmartTrimAutoMinimumRAMLoad=65
MinimumProcessWSSInMb=196
SmartTrimIntervalMins=15
[SysTrayBalloons]
EnableSystemTrayNotification=false
BalloonTipDuration=10000
ShowBalloonsForOocPriorityRestoration=false
[ProcessAllowances]
ApplyInstanceCountLimitsToAllUsers=false
AllowedProcesses=
DisallowedProcesses=
InstanceLimitedProcesses=
InstanceManagedCPUAffinities=
ProcessThrottles=
OneTimeProcessThrottles=
CPULimitRules=
[ProcessDefaults]
DefaultPriorities=x4.exe,above normal
DefaultIOPriorities=x4.exe,3,captureone.exe,3
DefaultMemoryPriorities=
DisableThreadPriorityBoost=
DefaultAffinities=captureone.exe,4-11,x4.exe,1-11
KeepRunningProcesses=
MatchWildcardsToPathnames=true
MatchOnCommandLine=false
[AdvancedRules]
DivideCPUPercentThresholdsBySystemCPUCount=false
ProcessorGroupExtended=
WatchdogRules2=
[GamingMode]
GamingModeEnabled=false
GamingChangePowerPlan=true
TargetPowerPlan=Bitsum Highest Performance
GamingModeEngageForSteam=false
AutomaticGamingModeProcessPaths=c:\program files (x86)\steam\steamapps\common\shadow of the tomb raider\sottr.exe,c:\program files (x86)\steam\steamapps\common\star conflict\game.exe,c:\program files (x86)\steam\steamapps\common\star conflict\win64\game.exe,c:\program files (x86)\steam\steamapps\common\x4 foundations\x4.exe,c:\program files\freefilesync\freefilesync.exe,c:\program files (x86)\musicbee\musicbee.exe,c:\program files\phase one\capture one 20.0.4\captureone.exe
[MemoryManagement]
SmartTrimExclusions=
[PowerManagement]
Display=x4.exe,musicbee.exe,captureone.exe
PC=
[PowerSaver]
ShowNotificationWhenActivePowerSchemeChanges=true
[ProcessDefaults]
DefaultPowerSchemes=sidebar.exe;ausbalanciert,x4.exe;bitsum highest performance,musicbee.exe;bitsum highest performance,captureone.exe;bitsum highest performance
[PowerSaver]
PowerSaver_IdleTime=15
EnergySaverEnabled=true
EnergySaverForceActivePowerProfile=false
EnergySaverUpPowerProfileName=
EnergySaverEvents=true
DisableEnergySaverDuringGamingMode=true
PowerSaver_TargetGUID=Energiesparmodus
PowerSaver_Exclusions=

try removing X4.exe from performance/game mode list, I see a duplicate of it in both game mode and application power plan.

Quote from: ranko on May 11, 2020, 03:30:15 AM
To my best knowledge and Windows tuning guides for DAWs (Digital Audio Workstations) its recommended to disable this
for computers with external USB audio devices. Could you kindly add this to your profile ?

BHP starts with a clone of the system's High Performance power plan, then makes known safe adjustments to dial-back CPU energy saving features

Making further tweaks would have consequences. While this or that tweak may work great for you, it might cause problems for other users. For this reason, adjustments such as disabling USB Selective Suspend are left to the user.

QuotePL 9.7.6.26, being run as service. Gaming Mode with Steam detection intentionally turned off, because then the machine works at highest energy profile too early when steam service is detected but not game running ...

That shouldn't happen anymore. It was traced to a timing issue that could occur sporadically.

QuoteThere are still issues where "Induce performance mode" has been set by GUI for the executable "X4.exe" but strangely it doesn't become active. IDLE saver kicks in and brings the machine from "Bitsum highest performance" to "energy saving"

At this time, I don't have any explanation for this observation. That doesn't sound right. What does the log say?

Try switching your Performance Mode processes to only filenames (e.g. x4.exe), instead of full paths.

You'll have to do this through 'Options / Power / Performance Mode / Designate High Performance processes'.

Let me know if you find that more reliable than the full pathname.

Sometimes, rarely, the pathname isn't immediately available, specifically when a process is enumerated prior to its first module (the EXE) being loaded. That could cause the pathname matches to sporadically fail. The handling of this rare scenario with regard to Perf Mode is being evaluated, and the default behavior changing to use basenames (filenames). I have no other theory under which Perf Mode matches wouldn't be 100% reliable.

EDIT: This scenario is now handled as of 9.8.0.21 beta.

Sorry, had not so much time.

9.8.0.54 Beta:
Today I experienced another issue.
Although "Induce Performance Mode" was set for X4.exe (I added this by PL  by right clicking under active processes tab and activating it)
Performance mode was not active and Idlesaver became active.

The configuration:
[Administration]
Version=4830200
ConfigPasswordMD5=
[OutOfControlProcessRestraint]
OocOn=true
ExcludeChildrenOfForeground=true
DisableProBalanceWhenSysIdle=false
ProBalanceDropOneRandomCore=false
OocDisableCoreParkingWhileIn=false
DisableProBalanceIfSysIdleThisManyMS=30000
TotalProcessorUsageBeforeRestraint=10
PerProcessUsageBeforeRestraint=7
TimeOverQuotaBeforeRestraint=1100
PerProcessUsageForRestore=3
PlayOnRestraint=C:\WINDOWS\media\Windows Pop-up Blocked.wav
PlayOnRestore=C:\WINDOWS\media\Windows Feed Discovered.wav
MinimumTimeOfRestraint=4200
MaximumTimeOfRestraint=0
TameOnlyNormal=true
LowerToIdleInsteadOfBelowNormal=false
ExcludeServices=true
PlaySoundOnRestraint=false
PlaySoundOnRestore=false
RestrainByAffinity=false
RestraintAffinity=
ExcludeForegroundProcesses2=true
DoNotLowerPriorityClass=false
RoundRobinAffinitySelection=false
LowerIOPriorityDuringRestraint=false
MatchExclusionsByPathnameToo=false
OocExclusions=
OocHardCodedExclusionOverrides=
[GUI]
ClearLogAtExit=false
ShowCPUCoreUtilGraphs=true
ShowGraphLegend=true
ShowGraphCPU=true
ShowGraphResponsiveness=true
ShowGraphMemoryLoad=true
ShowGraphProBalanceEvents=true
ShowGraphSelectedProcessesCPUHistory=true
ProBalanceCountersOnGraph=true
ShowGraphLicenseName=true
[Advanced]
AutomaticUpdate=false
RoundRobinSkipCore0=false
[Performance]
DefaultsLevel=327942
GracefulWaitTimeInMs=5000
UpdateSpeedGUI=1000
UpdateSpeedCore=1000
ManageOnlyCurrentUser=false
ExitOnCloseWindow=false
SoundsOff=true
AggressivelyTrimProcessLassoWorkingSet=true
IsConfigWritable=true
ForcedMode=true
IgnoreProtectedProcesses=true
IgnoreSuspendedProcesses=false
[ForegroundBoosting]
BoostForegroundThread=false
BoostForegroundProcess=false
ForegroundBoostExclusions=
[SystemTrayIcon]
UseStaticIcon=false
ShowResponsivnessInTrayInsteadOfProcessorUsage=false
[Logging]
LogDisable=false
LogSmartTrim=true
LogCPULimiter=true
LogEmitCSV=false
LogPruning=true
LogProBalanceParkingChanges=true
LogProcessExecutions=false
LogProcessTerminations=false
LogProcessesDisallowed=true
LogDefaultPriorityAdjustments=true
LogDefaultAffinityAdjustments=true
LogProBalanceBegin=true
LogProBalanceEnd=true
LogInstanceLimitTerminations=true
LogPowerProfileChanges=true
[MemoryManagement]
SmartTrimIsEnabled=true
SmartTrimWorkingSetTrims=false
SmartTrimClearStandbyList=false
ClearStandbyFreeRAMThresholdMB=1024
ClearStandbyOnlyInPerfMode=true
SmartTrimAutoMinimumRAMLoad=65
MinimumProcessWSSInMb=196
SmartTrimIntervalMins=15
[SysTrayBalloons]
EnableSystemTrayNotification=false
BalloonTipDuration=10000
ShowBalloonsForOocPriorityRestoration=false
[ProcessAllowances]
ApplyInstanceCountLimitsToAllUsers=false
AllowedProcesses=
DisallowedProcesses=
InstanceLimitedProcesses=
InstanceManagedCPUAffinities=
ProcessThrottles=
OneTimeProcessThrottles=
CPULimitRules=
[ProcessDefaults]
DefaultPriorities=x4.exe,above normal,imageranger.exe,below normal,eac.exe,above normal,foobar2000.exe,above normal
DefaultIOPriorities=x4.exe,3,captureone.exe,3,imageranger.exe,1,eac.exe,3,foobar2000.exe,3
DefaultMemoryPriorities=
DisableThreadPriorityBoost=
DefaultAffinities=captureone.exe,4-11,x4.exe,2-11
KeepRunningProcesses=
MatchWildcardsToPathnames=true
MatchOnCommandLine=false
[AdvancedRules]
DivideCPUPercentThresholdsBySystemCPUCount=false
ProcessorGroupExtended=
WatchdogRules2=
[GamingMode]
GamingModeEnabled=false
GamingChangePowerPlan=true
TargetPowerPlan=Bitsum Highest Performance
GamingModeEngageForSteam=false
AutomaticGamingModeProcessPaths=c:\program files (x86)\steam\steamapps\common\shadow of the tomb raider\sottr.exe,c:\program files (x86)\steam\steamapps\common\star conflict\game.exe,c:\program files (x86)\steam\steamapps\common\star conflict\win64\game.exe,c:\program files (x86)\steam\steamapps\common\x4 foundations\x4.exe,c:\program files\freefilesync\freefilesync.exe,c:\program files\phase one\capture one 20.0.4\captureone.exe,c:\program files\latencymon\latmon.exe,c:\program files (x86)\musicbee\musicbee.exe,c:\program files\imageranger\imageranger.exe
[MemoryManagement]
SmartTrimExclusions=
[PowerManagement]
Display=x4.exe,musicbee.exe,captureone.exe
PC=
[PowerSaver]
ShowNotificationWhenActivePowerSchemeChanges=true
[ProcessDefaults]
DefaultPowerSchemes=sidebar.exe;ausbalanciert,musicbee.exe;bitsum highest performance,captureone.exe;bitsum highest performance,latmon.exe;bitsum highest performance,imageranger.exe;bitsum highest performance,eac.exe;bitsum highest performance,foobar2000.exe;bitsum highest performance,x4.exe;bitsum highest performance
[PowerSaver]
PowerSaver_IdleTime=15
EnergySaverEnabled=true
EnergySaverForceActivePowerProfile=false
EnergySaverUpPowerProfileName=
EnergySaverEvents=true
DisableEnergySaverDuringGamingMode=true
PowerSaver_TargetGUID=Energiesparmodus
PowerSaver_Exclusions=

Your config shows x4 was previously added by path. As of 9.8, new Perf Mode processes are added by basename.

Try removing that path from the list and adding it back by basename, "x4.exe". That will be much more reliable. You can optionally do this for the others too.

Handling of the previously described scenario was improved in 9.8, but there are imits as to how long it will wait to get a filename. Some games may also be impacted by anti-cheat protections. In any event, it won't be much of an issue now that basenames are used for that list by default.