XnView Software

How do you get xnview to show .jfif files on windows 10 pro? you can't specify the file type association in xnview. windows app defaults settings will not allow you to select xnview for .jfif file type. and i don't see a plugin for .jfif. thanks.

are you able to view your jif files with Xn?

Good question. If i load them through File>Open, yes, they view just great.

so you want only associate .jfif to Xn?

Yes. It is the file association of .jfif to XnView that I would like to add in Windows 10 Pro. I have not found a way that works for me. (Looks like my thread title was somewhat misleading; I would edit it if I knew how.) Thanks, Jon

Which version of Windows 10, as it is a moving target, the tread may be referred to in the future?

Edit:

If you haven't tried it, a search for 'associate file type with program windows 10' produces several links that might be helpful...

If you find an easy solution could you please post a link to the answer, I think I've seen similar requests recently on the forum.

Well, this is interesting.
If you right click the file and select "Open with", then select XnView (which is possible here and not in Settings) and select "Always use this app to open .jfif files"; it opens XnView with an < Empty > file. This would suggest to me that there is an integration problem between XnView and Windows 10 Pro (OS build 17763.678). It stays associated, but always opens < Empty >. The association also shows in Windows>Settings now; so that is only part of the underlying problem.

I'm having trouble associating JFIF images with XnViewMP 0.96.5 64bits, double clicking on a JFIF image in XYplorer pro opens XnViewMP in Browser mode but thats as far as it goes.

ckit wrote: Thu Sep 10, 2020 1:45 am I'm having trouble associating JFIF images with XnViewMP 0.96.5 64bits, double clicking on a JFIF image in XYplorer pro opens XnViewMP in Browser mode but thats as far as it goes.

please check the registry key

which registry key?

Windows Registry Editor Version 5.00

[HKEY_CLASSES_ROOT\.jfif]
@="pjpegfile"
"Content Type"="image/jpeg"
"PerceivedType"="image"

[HKEY_CLASSES_ROOT\.jfif\OpenWithProgids]
"AppX2jm25qtmp2qxstv333wv5mne3k5bf4bm"=hex(0):
"AppX43hnxtbyyps62jhe9sqpdzxn1790zetc"=hex(0):
"AppXcdh38jxzbcberv50vxg2tg4k84kfnewn"=hex(0):
"pjpegfile"=""

[HKEY_CLASSES_ROOT\.jfif\PersistentHandler]
@="{098f2470-bae0-11cd-b579-08002b30bfeb}"

Now, before anyone says it... yes I could change "pjpegfile" to "jpegfile" manually but then others would still run into the problem at some other point in time. Hence, it needs fixing!

Update:
manually changing to "jpegfile" doesn't fix it

Update 2:
Renaming all JFIF images to JPG images, works LOL

Attempting open .jfif files from windows explorer launches xn, but it opens xn browser of the directory where the file is located instead. Opening .jfif from xn browser opens the image as it should.

The same exact issue with other extensions, such as .ico

This issue present in xn Classic and MP

The .jfif extension was associated with xn via right click -> open with -> XnView