ViewNX-i and Capture NX-D cannot read 16-bit TIFFs made by PS 2020 latest versio

[Ilkka Nissilä]

Hi,

I have this problem that about one month ago, when Adobe issued some security updates to Photoshop CC, my Windows 10 desktop PC's ViewNX-i started to show the 16-bit TIFFs as garbled images and do not display the image correctly. 8-bit TIFF images display ok, as do 16-bit images saved from PS 2019. I am using the latest version of Nikon software. On my laptop, the apparently same versions work correctly and 16-bit TIFFs are displayed correctly.

What could be the cause of the problem and what can I do about it?

Thanks.

[Ann]

Has there been a recent Windows 10 Security patch? Or is there a new Patch waiting to be installed?

Perhaps View NX-i itself needs an update to become compatible with the newer and more secure operating Systems?

Will a different image editing software open the 16-bit Tiffs on the Windows machine?

Perhaps you could try to reopen and then Save As to a new name in a different image-editing program; and then see if the file opens in Ps on Windows?

[Ilkka Nissilä]

Has there been a recent Windows 10 Security patch? Or is there a new Patch waiting to be installed?

Perhaps View NX-i itself needs an update to become compatible with the newer and more secure operating Systems?

Will a different image editing software open the 16-bit Tiffs on the Windows machine?

Perhaps you could try to reopen and then Save As to a new name in a different image-editing program; and then see if the file opens in Ps on Windows?

Thanks for your suggestion. I tried DXO Photolab 2 and that could read the files correctly.

I think I found the problem. PS 2020 on my desktop was saving the files using ZIP compression and Nikon software doesn't display those correctly in 16-bit format. If I use LZW compression or no compression, Nikon software displays those correctly. My laptop was saving the TIFFs with no compression, so that's why it was working. I'm wondering if I accidentally nudged the selected radio button down in the dialog box and caused this problem. Anyway, my problem seems to have been solved!