XnView Software

I was used to launching XnView MP in Windows 10 with a double-click on an image file in Windows Explorer. XnView browser then opened on that directory. Since last update it launches but point on the last opened directory.

Not sure if this is a bug or a new options hidden somewhere?

Win10pro 19045.5247

Thank you.

no need to post a duplicate

looks like a bug until it's fixed, you can:
- check "Purge 'Recent files and folders' on exit" in Settings > Interface OR
- disable "Save session on program exit" in Settings > General

to reproduce:
0. prerequisites
- have 2 folders with files inside, eg A\1.png and B\2.png
- set the following settings:
-- 'Save session on program exit' [Always]
-- Start with file [Browser] - for issue A
-- Start with file [Browser - Fullscreen] - for issue B
1. double-click 1.png in win file explorer
Browser opens correct folder - OK
2. press Enter to open 1.png in Viewer
it opens, and you have 2 tabs open - OK
3. close app via Ctrl+Q or X

Issue A
4. double-click 2.png in win file explorer
Browser opens previous folder

Issue B
4. double-click 2.png in win file explorer
Browser show black screen in Fullscreen
5. press Enter
nothing happens
6. navigate to the next file
now 2.png is loaded

yes normal browser opened in previous saved folder. If you want to open it in 2.png, press enter

I have updated prev post with issue B

xnview wrote: Mon Mar 10, 2025 9:20 am yes normal browser opened in previous saved folder.

there is inconsistency in behavior, that depends on the number of tabs in session:

• Browser tab only
  Browser opens correct (current) folder on start, not last one

• Browser and Viewer tab
  issue as described above

I think behviour should be unified to always use current folder, not last one.
As it is expected that current folder will overwrite last (saved in session) folder in case when app uses single Browser tab.

Thanks to your detailed description I can reproduce the problem.

This problem is supposed to be fixed in XnView MP 1.8.7. Please check and confirm the bug fix here.

fixed in 187