I am developing an application suite and one of the programs is started by the installer, which also places it in the start-up folder. When this application is started for the first time (by the installer) it discovers it does not have a configuration file and creates it. The problem is that the file permissions given to this configuration file prevent other applications in the suite being able to write to it.
If I delete the configuration file and restart the PC then when the application starts up it recreates the configuration file and permissions are good.
What is the best way to resolve this problem. I do not want to disable the auto-run of the application by the installer as this would mean the user would either need to start it manually for the first time or ask for a PC restart.