For Terminal/RDS and other 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.
For home/single-user systems
This warning is normally seen when a person is running Process Lasso as Limited (Standard) User, but has opted to start the Governor as a service. In that scenario, the user should consider changing 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, a user can fully close and re-launch Process Lasso manually, as an administrator. When started manually, there will be a prompt for administrative credentials. Entering those will start the Process Lasso GUI elevated, and thus it will be able to edit the configuration file during that instance.
Full warning text: “WARNING: The configuration file is not writable. Please check the path via ‘Options / General / Configure Startup...’.”