XnView 2.39 forgot the settings on Win7

Woodman wrote:But what happens if in the About the "INI file location" is "C:\Program Files (x86)\XnView\xnview.ini"

[…]

and in the Options>System integration"Save options as INI in folder "User""?

• xnview.ini & cache folder setting not obeyed
• xnview.ini in program folder with Windows 7
• Win7 64bit: Avoid loosing settings!
• Folder tree very slow to load
• XnView et "User Account Control Data Redirection"
• Help! INI File has Disappeared!
• fichier ini
• Need to change the location of settings
• Windows 10
• How to hide menu in viewing mode?

GeorgD (Win7 64bit: Observation + Registry Export) wrote:Hi, I reinstalled Win 7 DE 64bit Home Premium (I had the RC whose lifetime ends soon). Hence, I reinstalled XnView. Installation worked fine. .ini etc were copied to C:\Users\MYUSERNAME\AppData\Roaming\XnView which is fine. I overwrote the ini with my old ini from Win XP, after which it is important to do the settingF12 - System integration - Save Options - as ini in folder - User as without the setting, XnView might get the setting to save in XnView folder or in Windows folder which can be accessed by XnView in Win XP but can not in Win 7 - so XnView can't write there and looses the complete ini, also the one in user folder!

gothate (Folder tree very slow to load) wrote:Okay, I found where it keeps the files if you have it set to Options > System Integration > Save options > *as INI in folder - XnView. The files are kept in:
C:\Users\*username*\AppData\Local\VirtualStore\Program Files\XnView
This webpage explains why (if you're curious): http://zone.ni.com/devzone/cda/tut/p/id/5538#toc3

For example, take a legacy software application that attempts to write to a configuration INI file located in:

C:\Program Files\\Setup.ini

Windows Vista automatically detects that you do not have permission to save to that location. Windows Vista then copies the file (if it already exists) to:

C:\Users\\AppData\Local\VirtualStore\Program Files\\Setup.ini

Windows Vista then allows the write operation to succeed at the new file in the VirtualStore folder. Subsequent read and write operations for that file will always use the file copy located in the VirtualStore folder. However, the application will continue to believe that it is accessing the Program Files directory (see Figure 4).