Problems with nikon transfer software

If this dialog is displayed, click OK each time. In addition, we do not plan to provide compatibility for other software, or SCSI- or serial-connection products. We apologise for any inconvenience this may cause.

For more information regarding this matter, please contact Nikon Customer Support. FCC disclosure statement: this post may contain affiliate links or promotions that do not cost readers anything but help keep this website alive. Thanks for your support! Nikon Rumors. So, heads up if you are considering the upgrade. I seriously regret that I did. Nothing gained but stupid issues like this. Create a shortcut to "explorer.

I do not have Windows 10 but have used this method on 7 for backward compatibility of many programs. It won't work. This is a driver issue. It takes place in a different level.

It doesn't matter what the software does if the connection with the camera isn't working. Someone said that with Nikon ViewNX file transfer would work. I haven't tested it but if so I'm wondering how it does it I guess I have to install it and try to find out. The drivers are probably included with ViewNX software and can't be used by Windows Explorer or another application. It seems you are right. I guess there's little else to do than wait for a fix. Well, maybe put some pressure to them to do it sooner than later.

But what I noticed is that when I went directly from 7 can't remember when I last had reinstalled it to 10 I had some issues with hardware sound crackling, artifacts etc. I then did a clean format and install of Win 10 no key needed again btw and things went from night to day.

Everything suddenly became very fast and things that previously had some issues started working perfectly. Not sure of course a clean reinstall could fix this particular issue, but it might be something to keep in mind - the reinstalling is very fast btw and other than programs I didn't have to install any drivers myself for anything. I even skipped installing Acrobat Reader since this functionality seems to be built into EDGE instead, one less annoying program to update.

I noticed that, when connected, my D appears in the 'This PC' list in alphabetic order rather than in the 'drives' section. This has been a problem That Microsoft has never taken seriously and never tried to solve ever since Microsoft changed their transfer-protocol to MTP Media transfer protocol , with as far as I remember Windows7. With my upgrade to Windows 10 is the first time I didn't have the issue on neither of my PC's.

As far as I remember, it's a matter of repairing some "Services" and some Registry keys - and somewhere, if you google the error-number hard enough, you'll find the solution for your problem among a lot of solutions. I always succeded to - but in different ways every time, as far as I remember. I'll try to "google" too - see if I find it again - and return In the meantime, you could see if the latest Microsoft Portable MTP-device driver-tool kit, which is to be downloaded from Microsoft, solves the problem.

I would try manually deleting the driver via the device manager , and then let windows automatically look for most current drivers. That seems to be working with the few issues I've come across when updating to Windows This is what happened to me with the D and D In the Settings panel select "Devices". In the Devices panel select "AutoPlay" last option on the list.

That brought up a screen that allowed me to select the action I wanted to happen. I don't shoot tethered but I would guess the steps would probably be the same with the only thing changing being what action you select to tell Windows 10 what you want to happen.

As far as I know this particular issue won't affect such new models so the problem you had have very likely been a different one. Someone suggested clean install. I did that. Letting Windows seek new drivers.

Did that too. This is simply an issue of USB protocol changed in a way that certain older camera models can't handle. Unless there's a way of using an older MTP protocol driver in Win 10 I'm afraid there's nothing to be done but wait for Microsoft or Nikon to fix this. Someone said in a different forum that Windows seems to be now sending a little longer version numbers to devices. Some devices like D don't expect that so when they receive messages they go like: "What's this? Too many numbers?

I don't know what to do with this! I'm ignoring the messages and shutting down. Sorry I couldn't help. Hope you don't have a long wait for a fix from Nikon or Microsoft.

It seems MS has been aware of this problem for at least a few weeks. The affected cameras are at least D, D, D and D Probably others too, if they are at least that old. It seems they've just released a Windows update. After reboot file transfer works, in Lightroom 5 too.

But when I try to start tethered capture in LR it won't find the camera and the file transfer brokes down again in Windows Explorer too. I also used View NX2 because it allowed me to quickly review and rate photographs, which in turn helped me cull thousands of pictures down to the keepers. Everything seemed normal, that is until I arrived home. When I uploaded my pictures to my local storage drives and began rating and culling, I noticed that all pictures taken with the D weren't previewing properly in View NX2.

Instead of opening up a x pixel file, files measured a measly X pixel. Moreover, I was unable to select a camera preset e. This happens presumably because Nikon Transfer does not recognize the camera. That being said, even though the information is all there in MB , there is no way to open the NEF files.