Nikon reports possible View NX-i image data corruption when using Nikon Transfer 2 on the latest versions of macOS Sierra

Nikon ViewNX-i
Nikon Japan published a warning about a possible image data corruption in View NX-i when transferring images with Nikon Transfer 2 on macOS Sierra version 10.12.2.Β The latest ViewNX-i version 1.2.4 is compatible with macOS Sierra version 10.12 but it is not compatible with macOS Sierra version 10.12.1 or later and you should not use Nikon Transfer 2 until an update is released.

This entry was posted in Nikon Software and tagged , . Bookmark the permalink. Trackbacks are closed, but you can post a comment.
  • Yep, happened to me. Drove me nuts initially – I was sure my SD card was completely corrupt.

    • Heitschmidt

      Happened to me, too, yesterday with D800e and D810 files, but not D700. Only portions of the files appeared normal, however, the files on the CF cards were not affected. Copying using Finder worked and ViewNX-i and CaptureNX-D both displayed the files normally.

  • JoCarpenter

    You know, I’m deeply disappointed in Nikon’s transfer software. It’s a simple task that should work flawlessly, yet it’s buggy and difficult to use. Mine will only read one of the card slots in the camera, there’s no (easy) way to view the second slot.
    It used to work.

  • Wayne Wynn

    I had the same problem as well with my raw files being transferred . All of the files it transferred were half photos half black. I end up having to extracted the JPG from the raw files to edit them.

  • Chris Whitty

    I’ve had a problem reading from the SD slot on my MacBook Pro where Transfer 2 does not launch on inserting it. When it does finally launch only some of the shots on the card show up. Ejecting it and re-inserting it sometimes shows the same few, sometimes others but not all of them. The shots are from a Coolpix B700. Using a Firewire card reader the CF card from my D800E comes up OK. With the SD card I have to open Apple’s Image Capture and import them into Transfer which works. However, I get a message saying that Image Capture cannot open them with each shot coming up with its own individual message which is a pain to cancel when I have a lot on the card.

  • Fly Moon

    I’ve seen that just last week. I googled it but couldn’t find anything. I stopped using Transfer 2 on macOS Sierra.

    Here is what I got.

    • Heitschmidt

      I observed very similar results, either 3/4 black or the bottom half contained diagonal stripes. (NEF files from CF cards)

    • saywhatuwill

      I used to get that with ViewNX. I lost numerous really good photos I wanted because of it. Since RAW and JPG were in the same window I lost them both. I separated them after that happened so that JPG showed in one window and RAW in a different window.

  • yepits me

    I deleted this upgraded version as it has lots of problems,,went back to previous version.

  • TheInfinityPoint

    How embarrassing.

  • nwcs

    Imagine what would happen if Apple let people beta test an OS before it is released. You could see what happens to your software. Too bad Apple won’t let anyone use a beta release…

    Or maybe it’s just the latest in a string of problems with camera makers and anything software. You’d think at this point they’d just contract the work to people who can do it and do it well but it goes against the tight grip of control they have to have on everything.

    • Um, you CAN Beta test Apple’s OS… I do. You can too:

      • nwcs

        Lol, you didn’t recognize what I thought was my obvious sarcasm.

    • Fly Moon

      Have you been under a rock for the last 2-3 years? It’s even a public beta not just developers. Stop blaming Apple!

      • nwcs

        Lol, I was being totally sarcastic.

        • Fly Moon

          Then, you’re forgiven πŸ™‚

    • Spy Black

      Actually, you’re beta testing Apple’s, or anyone else’s software the moment it comes out, whether you want to or not. Just look at the recent iOS and OS versions, or Windows, or Adobe. End-users are forever perpetual beta testers, most just don’t realize about their part-time job. πŸ˜‰

      • nwcs

        Well, software is never truly done because after a certain point it gets literally too difficult and expensive to test everything and users tend to do things that aren’t predictable. πŸ™‚

      • Fly Moon

        Can you give a name of a software company that you admire?

        • Spy Black

          I can name several, but they all have you beta testing. πŸ˜‰

    • Thom Hogan

      You sarcastically point out the real problem here. If Nikon actually had a well though out testing and QC program, they’d be doing tests of their products against all pre-release OS’s, and they’d have known about the Transfer problem before the macOS Sierra update shipped and could have either (a) warned about it; or (b) fixed it.

      As someone who was in charge of third-party software products that lived very close to the OS, we spent a great deal of time and effort on that, because the downside would be that we lost users and increased customer support costs.

      The problem, of course, is that Nikon’s software is free. There’s no revenue stream associated with virtually all of it now, thus it’s always looked at as a cost to the company. And what does Nikon’s CEO keep saying? “Cut costs.”

      While some of Nikon’s software can be useful, a couple of years ago I stopped recommending it, regardless of what it might achieve for a user. The likelihood that you’ll have a downstream event like this one with Transfer is high. Very high. And Nikon’s response has been traditionally slow. You can’t really rely on their products in workflow.

  • Eric Calabros

    You know what boggles my mind? That so many people still using this software!

    • Fly Moon

      haha. I tied to use it in my workflow, but I am back to Lightroom now.

    • whisky

      what boggles the mind even more is why people continue to use Nikon branded software. seems to cost everyone in the end. :-

      • Thom Hogan

        My point exactly when I dropped my recommendation for using Nikon software back in 2015.

  • Bakker

    I’ve definitely lost tens of photos from my Nikon D5 today as I’ve deleted the files from my XQD cards after the transfer using Nikon Transfer 2. This is not acceptable from Nikon !!!

    • silmasan

      Wait, wouldn’t you at least review the images (both on your computer and) directly on the camera before you delete them?

      • Eric Calabros

        Take that comment with a grain of salt

        • Thom Hogan

          No, don’t. If @disqus_SolqkZOt4p:disqus has selected “automatically delete files after transfer” in his preferences, then there’s a teaching moment here: don’t do that!

          It actually doesn’t matter whether Transfer works or not to get the files transferred. Allowing your computer to touch and modify anything on a card is fraught with peril. A bit less so today than it used to be, but some camera makers are still using non-standard partition tables and other oddities.

          The correct procedure is always this: after transferring your images and verifying that they’re fine, format the card in the camera to remove files.

          SD cards are a little better in this respect. I’d add that you can use the SD Associations low level card formatter on your computer, but I still wouldn’t do a file delete on a computer with them.

          • Spy Black

            Capture One and Lightroom also give you the option to delete files from the source after download. Over the course of time I’ve seem multiple programs that give this option. Although I can see what the original intent was, I really think it’s high time programs stop having this as an option in their data transfer process. It’s outright stupid.

          • Eric Calabros

            There are also some articles on the web suggesting Don’t Delete Images Until Card Is Full.

            • Allen_Wentz

              Heck even Apple’s workflow had Aperture users auto-deleting incoming images from within Aperture (which was nuts). Like Thom said:

              “The correct procedure is always this: after transferring your images and
              verifying that they’re fine, format the card in the camera to remove

              Personally I also consider a backup-to-separate-drive step essential prior to reformatting in-camera.

            • Thom Hogan

              I would say ignore them, because that’s clearly wrong.

              1. Using Format on the camera is fine any time.
              2. Using Delete Image(s) on the camera is suspect, and it’s especially suspect as the card approaches being full (see the interview I did at NAB with one of the leading data recovery experts).

            • El Aura

              Of course, Format-in-Camera is fine. It’s more than fine, it of course is by definition the safest solution. But that doesn’t mean that other solutions should be avoided. People constantly delete images in-camera without any ill-effects. Just because re-installing your computer OS every six months is better than not doing it (putting effects of wear and tear aside), doesn’t meant that running the same OS ‘installation’ for multiple years (ie, without performing clean re-installs) should be avoided.

              ‘Only’ deleting images might lead to fragmentation and cameras might not do any defragmentation like computers do. But that only affects speed (and data recovery in case of accidental deletion or hardware failure). Very few people reformat USB sticks after every use, even though, like memory cards, they are more at risk of unplugging without un-mounting than internal drives.

              Changing the oil in your car every 2000 to 3000 miles was an American practice I first heard about 20 years ago, while in Germany people changed their oil once a year normally. My current car is 13 years old and indicates an oil change every 15’000 miles or so.

            • Thom Hogan

              Go back and read that interview I did. What he said is dead on. Delete in camera does file fragmentation, and file sizes are variable for images. Thus, you eventually get to the point where you will be trying to save a file into a spot too small for it. The question then becomes what happens. As I’ve seen time and time again, what happens is that the camera’s cheap electronics are not fast enough to deal with this, and you get the classic failure: the image is “saved” but the data never got to part of the drive. Note that Nikon and some others also do calculations in between moving the write pointer, which slows things down more.

              No, you won’t always be hit by an error in this situation. But your if you never deleted in camera your failure rate would be 0, if you do delete, you failure rate is >0.

            • silmasan

              Holy F. I just read that (thanks). It does make total sense. Low volume shooters like me may not experience any problem deleting stuff as they go. But I can see high volume shooters and especially video shooters having serious trouble with that habit sooner or later.

            • El Aura

              I have never dealt with a computer system (going back more than 30 years) where disk fragmentation lead to not writing data to disk while reporting a write success. Are you telling me that cameras have problems that were solved on computers 30 years ago?

              I know you are telling me just that or that some computer systems also had such problems less than 30 years ago, but I guess I reserve myself the right to delete images in-camera when needed and if this leads to an error than so be it. I am not going to format a memory card unless I am absolutely sure that all images on it are copied to my computer and backed up in at least one additional location. I once sold a memory card with a camera that had images on it that were not copied to my computer yet. For me personally, the risk of loosing images by formatting the card in-camera is much higher than the risk to get write errors due to only occasionally formatting the card in-camera.

            • Thom Hogan

              Yes, I’m telling you exactly that.

          • Across a few Nikon bodies/generations, I’ve never had any issues with Linux deleting files from cards. Now true I’m not a professional so my photo volume is low, but I never ever have seen photo corruption during transfer or problems after deletion.

            Of course, I don’t allow Windows anywhere near my cards.

  • TwoStrayCats

    This is why I’m still using Yosemite… and will be for a while.

    • I’m using El Cap and it’s fine. I will not be going to Sierra…looks dicey at best.

      • Thom Hogan

        There’s nothing wrong with Sierra (at least nothing more than is usually wrong with Apple OS iterations). There is something wrong with a company that produces software for the Apple ecosystem that doesn’t use the beta program to test and keep up.

        Why? Because in the Apple world, there’s generally a very huge percentage of folk that stay up-to-date with the OS on their devices. If you have a failure point in your software that a new OS will reveal, you’re going to have a customer support issue very quickly.

        It’s unlikely that Nikon has a QC team that is running betas of new OS’s against a full test suite to look for issues before users encounter them. Nikon’s officially stated position is that they’re an ISO 9000 compliant company, and that this somehow requires them to wait (it doesn’t).

        • It took me a long while to give up command line and go to Windows. Finally had to, of course. I’m just old and stuck in my ways and don’t like the idea of having to talk to my computer. I talk to my phone and half the time that idiot doesn’t understand what I want. Thus, I resist. I’ll get there. Meanwhile, I wonder if Nikon are seeing a lot of noise at ISO 9000.

          (Just kidding, fully aware of what that means in this context. Just couldn’t help myself).

    • jvossphoto

      Plus one, but don’t use any Nikon software anyways.

  • yrsued

    One more reason I stopped using these products years ago!!

  • silmasan

    You know what, using a software of any major new release younger than at least a year isn’t a very wise thing to do, unless you deliberately intending to be tester. Especially if it’s an OS with a new file system!

    • Photog

      True, macOS 1-year cycle release is too short, two or even three years would make more sense.
      However the software released by both Nikon and Canon is really of very poor quality.
      Moreover both haven’t fixed yet their issues with Sierra three months after its release and they had also access to beta versions… For example tethering is not functional at all on macOS Sierra 10.2.2!

      • Thom Hogan

        Personally, I would like them to go to a tick-tock release schedule, but stay on the yearly boundaries. The tick release is new features (including new foundation elements), the tock release is absolute stabilization and performance tuning.

        What most people don’t know is that at the OS level you would generally have thousands of known bugs in the database on launch. You’re always in a chase situation, as new bugs are constantly being discovered. When you’re trying to build out new features you’re also generating new bugs. Thus, what happens is a bug priority loop where some things just never get fixed because they can’t attain the priority given to new features. No one has time to fix and test them properly.

        • Photog

          The problem is that in fact this is how Apple is proceeding nowadays. For example Yosemite and El Capitan and we all know the end results…

          • Allen_Wentz

            I do not agree with your implication as regards “how Apple is proceeding nowadays.” The OS upgrade process has always been pretty much as Thom described it.

            • Photog

              Recent OSes are less stabilized than older ones, reducing the life cycle to one-year, even if you go tick-tock, doesn’t work well and third parties have problems keeping up as well. While keeping the one-year cycle a switch to at least tick-tock-tock would be necessary.

            • manattan

              I also agree that they could slow down new feature introduction. I really liked that it when Apple took the time and released snow leopard and basically said “Hey, we are not adding much feature wise, but are rebuilding the OS to make it solid and faster”. If that is a “tock”, then what I would like to see is something like tick, tock, tock, maybe even a third tock before we get another tick.

      • silmasan

        This kind of hiccups happen across industries. I’ve also seen a surge of complaints on DAW (music production) forums everytime there’s a new release.

        The least resourceful ones (I’d only guess Nikon and Canon software team belong to this group) would definitely be the ones to suffer the most from this practice.

        • Photog

          C’mon they both have the resources and if they don’t then they should get more people. Anyway to fixes shouldn’t take them over three months as it isn’t a complete rewrite of the software, unless of course their software is so crappy that every time they have to reinvent the wheel!

          • silmasan

            Maybe they have this quota/threshold for hiring talents on demand… measured in number of users complaining. πŸ˜€

        • Allen_Wentz

          I agree with Photog. It is not about CaNikon being “least resourceful” so much as both being really badly managed as regards consumer software.

          • silmasan

            I too agree with Photog. I simply forgot the /s on that one. πŸ˜‰

    • Thom Hogan

      That’s a trickier proposition than you think, and especially in the Apple ecosystem. Should you buy a new computer/tablet/phone, you’ll be on the latest OS whether you want to be or not. If you start mixing and matching OS versions among your products in the Apple ecosystem, you start running into issues, because iOS and macOS now march in lockstep. Beyond that, you’ll be last (if at all) to get security updates.

      That said, it’s rare that I move immediately to a new macOS version. But I don’t wait a year. There’s generally a point about two or three quick updates in when things stabilize. We’re at or approaching that point now with macOS Sierra.

      • Photog

        Well .2 Sierra is nowhere near this point. Hopefully .3 will, nevertheless those constant “updates” are creating more issues than they are bringing in useful features.

      • The rush to have arm compatible os seems to be won by Microsoft although MS tend to get a hard time and are often dismissed. Any way will be interesting to see what happens to intel and amd when all OS can run on arm chips natively. Also apps will change dramatically if users have the ability to run open source code on any device.
        Personally i only use view-nx to purge images i don’t want,Nikon software is pretty poor, I really wish Nikon would sell their raw codecs to adobe.

        • Allen_Wentz

          MS did NOT win some “rush to have ARM compatible OS.” Apple’s mobile iOS has always utilized ARM architecture, and Apple-designed mobile ARM chips have been leading the smartphone industry in performance for years. ARM-based flagship mobile Apple devices have led worldwide sales for years, while MS ARM device worldwide sales (mobile+desktop) have been very small, usually reported in some “Other” category.

          Apple and MS have been taking different approaches toward OS applications in the modern era. MS chose to build one OS for all devices, while Apple chose to develop a full-strength 64-bit mobile iOS (fully implemented since ~2013) based from the same core as its x86 desktop OS while increasingly sharing documents across the two OS versions via the cloud.

          There are obviously proponents of both approaches. Some (like me) consider ergonomics to be of critical importance, and want their desktop OS to be optimized for desktop usage and their phone/tablet to run an OS optimized for mobile. Others prefer a single OS, which has a certain theoretical elegance but (except for tiny-sales convertible devices) leads to less than optimum ergonomic operation.

        • Spy Black

          I’m not sure MS won any race, or was even trying to be in a race to begin with, other than a catch-up one. What they did do was to completely upset their user base by shoving an OS down people’s throats that nobody asked for, or cared for, in a desperate attempt to catch up to Google and Apple. This cost them their bottom line, as corporations had no desire to spend time and money to have to retrain their employees how to re-invent the wheel just because MS wanted to say “me too”. To this day you can still buy business machines with Windows 7 because of that backlash. All my personal workstations that I build still run Windows 7 as well, because I have work to do.

      • Thom, do you have any idea/details/rumors what will happen next week at the CES show? In the best case scenario, I expect a new Nikon 1 J6 and the D5600 for the US market. I find it strange that there have been no rumors at all.

        • Thom Hogan

          I have one thing I can’t talk about that should happen in January, maybe at CES.

          I think it’s safe to say the DLs get reintroduced and the D5600 appears.

          Nikon would probably be shooting themselves in the foot introducing a J6 at the same time as the DLs. Given their previous moves, they should understand that launching a J6 simultaneous to the DLs doesn’t result in the maximum sales of either.

          • So it will be actually worse than I imagined – reintroducing already existing products. This probably explains the lack of rumors/leaks.

            • Plug

              Surely there must be new lenses? The telephoto upgrades to FL and E? There was talk a while back about a replacement fisheye. For me Nikon have excellent bodies and it is glass that interests me.

            • CES is usually not a place to unveil new lenses, maybe the CP+ show in February.

            • Richard Haw

              Registration for CP+ is up. have to be there!

            • waiting for your report/pictures πŸ™‚

            • Thom Hogan

              Without saying anything substantive, I expect Nikon’s bigger 2017 announcements are in the February to August time period.

            • Makes sense, thanks!

            • HF

              I would like a baby D5 before May. Could turn out difficult.

    • CERO

      Tell that to Microsoft. Which you can barely “delay” by up to 6 months. Most home users are screwed and are forced to update/upgrade.
      I wouldnt be surprised if MacOS moves into that style next.

      • silmasan

        That’s 8 months if you set a W10 install to CBB (it’s at least easy on Pro), likely longer if you’re on Enterprise with LTSB. Also removing Flash completely (incl. WU-CBS detection parts in registry) will help a lot, as it significantly reduces frequency of critical security updates in my experience.

        If a year was too much to ask, then anywhere between 6~10 months should do. With their much-publicized initiative in entering the enterprise market, I’m expecting Apple to come up with a LTSB path.

        I’m sure many studios would rather stick with old stable versions of their programs and keeping their machines mostly offline, for as long as possible.

        • CERO

          Weird, the longest figure I remember seeing was 6 months for enterprise, and 3 months for PRO installations.

          Did they fix that?
          also wishing you could just completely remove Cortana.
          That thing feels as bad as Denuvo and other rootkits…

          • silmasan

            Yeah, I tried to play hard with ‘her’ but it brought issues as it’s tied with desktop search.

            Btw, here’s how to set up that 8-months defer for Pro: (google) pureinfotech defer-windows-10-upgrades-updates
            IIRC t’s alwasy been there and I hope they don’t remove/decrease it. I got the reboot loop problem when one of my systems tried to upgrade to 1607.

            Enterprise sounds like the ideal build for workstations, and it comes without Store and Cortana. But getting a perpetual license outside volume licensing is not easy.

            • CERO

              Oh gods, I hated the darn anniversary patch.
              It caused pletora of problems for me.
              In one machine, it made the detection of videocards impossible (Nvidia).
              I had to literally reinstall windows on top (win10 on top of win10 with anniversary ISO) to make it work.
              Others got in the loop you said. Others simply threw the BSOD with empty error code. (freaking hate the useless BSOD screen of Win10)

  • Focuspuller

    This is probably more Nikon’s fault than Apple’s, based on Nikon’s software history. When I was using CNX2, and Nikon announced it would no longer support it, I bailed INSTANTLY, knowing full well some future MacOS update would render CNX2, and all my adjusted files, unusable. Maintaining a Mac with obsolete OS just to run CNX2 was NOT an option for me. Nikon should just get out of the software business completely and make business alliances with more serious and conscientious vendors.

  • CERO

    Yo Admin, question…

    This is corruption based on damaged files(aka the program sends or receives garbled data)? or because the connection simply fails and the image cuts down and is incomplete?

  • A-Sign

    Simple solution: Don’t use MacOS πŸ™‚

  • John vdK

    MY TEMPORARY SOLUTION: copying from the SD to the HD, using the Finder (and renaming it with Skooby). And after that proces the NEF’s in Photoshop. I hope the update of Transfer 2 will be soon.

    • JIm

      back when I got my D800 I did something like that and got in trouble and was not able to use the RAW files, the jpegs were ok. For some reason, I was informed that I had to use Nikon Transfer. I don’t know if if that is still true.

  • Samuele

    I’ve also had this problem, I thought it was my sd card.

  • Rubber Johnny

    When it comes to software Nikon is failing, there hardware is bang on apart from a few faults(D600) which they’ve learnt there lesson! But there need to employ someone young to be in charge of there software department…

  • Wayne Wynn

    From what I can tell after trying several things including repair the . NEF files, it’s not that they are corrupted, it’s that the file are not being completely transfered. Luckily I found this

    It pulled JPEGS from my NEF files. All of the JPEGS where fine and from what I can tell these are not like the normal JPEGS from the camera with all of the setting, just JPEG version of the NEF files. Not a perfect fix but at least I was able to edit the files. For now I am just coping and pasting from the SD card in Finder or using Adobe Bride.

  • JIm

    One of the wonders of the age of computers – configuration management – getting everything to work together and stay working together as programs, hardware and operating systems change,

  • Back to top