Why am I receiving a warning that ‘the configuration file is not writable’?
For Systems That Are Not Servers
This warning is seen when Process Lasso auto-starts in a limited (standard) user context. In that scenario, it cannot make changes to the configuration file without elevation.
You can safely check ‘Do not ask me again’. If you then click the Yes button, you’ll be asked for administrative credentials every time Process Lasso starts. If you select the No button, you’ll not be asked for credentials, but won’t be able to change the Process Lasso configuration unless you use ‘Main / Elevate Now‘ first.
Alternatively, the user can change the configuration and log paths to something under their user directory. This can be done via ‘Options / General / Configure Startup…’. See screenshot below.
Note that for multi-user systems, changing the path to a user folder is not recommended since other users won’t be able to write to it. Instead, when a configuration change is necessary, use menu item ‘Main / Elevate Now‘.
For Terminal/RDS Servers
On servers, this warning is best resolved by simply setting the Process Lasso GUI to not auto-start for all users. The GUI (ProcessLasso.exe) hosts the system tray icon and main window of Process Lasso. It does not need to be running. The separate Governor (core engine) will enforce all rules in the background regardless. The GUI can then be opened manually when needed, or auto-started only for administrators.
Use the menu item ‘Options / General / Configure Startup…‘ to change the GUI auto-start to only your administrative user, or no users.
Full warning text: “WARNING: The configuration file is not writable. Please check the path via ‘Options / General / Configure Startup…’.”
Should I rank all processes in importance to me, changing their priorities?
We recommend a conservative and selective approach. Only adjust the priorities processes that you are concerned about, not all of them.
Should I raise the priority of my application?
Possibly, but the best practice is to approach it from the other direction – lowering priorities of anything that might interfere with your critical applications. This approach of lowering priorities is much more effective than raising the priority class of your applications.
