Our company keeps a single preferences file on a server that every user accesses as read only.  We do not want people changing the settings.   I’m not sure when the behavior changed, I know it was not a problem with version 2017.12, but you can no longer select the read only file.  When exiting it says the preferences have changed do you want to save, select yes and It wants to access the unchanged read only file and gives the error “Unable to save”.  This was never a problem before and it was only noticed because a user had to reinstall from scratch.   Why does it need to access the preferences file when selecting it?

It seems the only option now is to install an older version of the tool (we start with 2017.12) which allows read only files to be selected, select the read only preferences file, then upgrade to the latest version.  There must be a better way to handle this.  I would think site control should be possible.

Can the use of read only preference files be returned to the software?

Regards,

Chris