>To put it in simple terms. %programdata% is read only for users for decades.
>It is stated that it does not require elevated privileges - what only means a admin can write to it without extra dialouge.
>You can use your installer to create a folder with permissions if you realy need this.
>
>The file should end up in some roaming folder. I'm no expert in this folders (It's Redmond idiotic - one can write or not). But simply give it a unique name and search your whole comp for the file.
>There should be some environment variable or a reg key that gives you the path to the roaming (don't trust hard coded here). Google will be your friend.

Prior to Windows 10 we're been using ProgramData without any issues. The program still works fine and writes to ProgramData when we run it as a program (at least in my earlier tries). But it doesn't work anymore if testing from VFP directly when not running VFP as Admin. I raised that question yesterday to my colleagues and one of them said he is running VFP as Admin. Well, it will work as a workaround for me, but perhaps we would need to figure out a different folder for our apps log files (and .ini files).