Riot desktop doesn't read config.json with roaming Windows profile

[nE0sIghT]

Description

We using roaming Windows profiles in our environment.
%APPDATA% variable for user user is \\server.domain\Folders$\user\AppData
We copyed config.json to %APPDATA%\Riot, but Riot doesn't reads config.json from roaming location, however Riot folder is properly populated with other runtime data.

Version information

• Platform: Desktop
• OS: Windows Server 2016
• Version: 1.6.0

[Nils-GitHub1]

Same behavior confirmed on Element v1.7.10 :

Version information

**Platform**: Desktop
**OS**: Windows 10 (Pro, build 2004) 
Version: 1.7.10

[Nils-GitHub1]

Workaround / source of the issue identified:

Element on Windows still load config.json from %APPDATA%\Riot instead of %APPDATA%\Element

We confirm Element v1.7.10 on Windows do load %APPDATA%\Riot\config.json

Note: %APPDATA% in our case is on a local disk, not on an SMB share.

Platform: Desktop
OS: Windows 10 (Pro, build 2004)
Version: 1.7.10

[t3chguy]

This issue predates the Rebranding.
The issue you are having is that IF there's Riot data then it'll continue to use it, otherwise Element will be used

[Nils-GitHub1]

Thanks, I confirm after testing that Element v1.7.10 Windows desktop app do properly read config.json:
from %APPDATA%\Riot\config.json if Riot data exist, or from %APPDATA%\Element\config.json
at least if %APPDATA% is on local disk. I'm not able to test with %APPDATA% on SMB share in my setup, so cannot comment if the initial bug reported is fixed or not in V1.7.10 with profiles on SMB shares.

[t3chguy]

Wrongly closed due to action misconfiguration

[nE0sIghT]

I have no access now to environment I previously described and can't test this issue anymore. So closing it.