I have an environment set up where some of the environment variables are pointing to another path (network drive)
and these variables are not used.
For instance, %LOCALAPPDATA% points to "x:\users\USERNAME" but the files are still created in "c:\Users\USERNAME\AppData\Local"
This is a problem because in that environment user is not allowed to write to drive c:
What file exactly is created in the wrong folder?
Regards
David Hervieux
the complete folder "c:\Users\USERNAME\AppData\Local\Devolutions\PasswordVaultManager" is created in the standard path if it does not exist, not in the changed location of LOCALAPPDATA
When i look in SysInternals process explorer the LOCALAPPDATA points to the changed location, but that is not used
at least not at program start
when i create a new datasource it is placed in the changed location where LOCALAPPDATA is pointing at.
(after creating an entry in that file)