Issues running governor-as-service with limited rights user

[ranko]

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.

[Jeremy Collake]

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.

[ranko]

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 ?

[edkiefer]

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.

[ranko]

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 ..

[edkiefer]

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.

[Jeremy Collake]

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).

[ranko]

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 ?

[Jeremy Collake]

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).

[ranko]

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.

[Jeremy Collake]

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.

[ranko]

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:


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=

[ranko]

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".

[Jeremy Collake]

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.

[Jeremy Collake]

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

[ranko]

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.

[ranko]

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 ?

[edkiefer]

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/

[ranko]

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.




[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=

[edkiefer]

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.

[Jeremy Collake]

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.

[ranko]

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.

[ranko]

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=

[edkiefer]

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

[Jeremy Collake]

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.

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 ...

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

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"

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

[Jeremy Collake]

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.

[ranko]

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=

[Jeremy Collake]

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.