Arduino Zero driver not matching with windows


I am trying to install the Arduino zero on windows 7, 32 bit. when i connect the arduino to the laptop, in device manager nothing is appearing under USB , it appears under portable device, refer to the attachment capture 1.

However when i am trying to update the driver manually, a windos pop up showing that the selected driver file is not matching with the hardware refer to the attachement capture 2.

Since one week I stuck and I couldn’t connect my Arduino zero.

I am looking for support in getting the arduino connected.

thanks in advance

Capture 1.PNG

Good Afternoon,

Since this seems to be your first post, it seems likely that you haven't gone to the Boards Menu, then to Board Manager to download the Arduino SAMD Boards Package. I assume that your ZERO board says "" on the back.

I am using Windows 7.1 and 8.0 64-bit versions. My Arduino version is 1.6.5 and it seems more stable than earlier or later versions.

If the board is plugged in you should notice its presence under "Ports" in the Device Manager. It will be assigned a new port number. I am assuming that your usb cable is of good quality and is firmly connected to the EDBG port of your ZERO. I have spent more time than you would believe chasing problems that stem from this USB connection.

If by chance your ZERO board says "" on the back then the Board Manager won't apply and you will have to go to their Web site for help.

Hi surfingDude, thanks for your answer.

Actually in the rear side it is mentioned

SAMD board package already installed.

I am having IDE 1.6.6

Many usb cable I tried. Same problem.

As i mentioned in the snapshot the problem is that the pc shows the arduino under portable device and not under the "other device" or under " unkown usb".

Appreciate your support

OK amerlagha,

Next steps.

  1. Your zero may have come with the "blink" program preloaded. Try plugging in both ports to see if it is running. This is just a basic power test, you should see a green led on solid and next to it a yellow led that may be blinking. I am using a USB 2.0 port on my computer, USB 3.0 might be different.

  2. The Windows Device Manager - "Ports (COM & LPT)" should change as you plug and unplug the ports. When things are running right, my computer shows the following: For the EDBG port: Atmel Corp. EDBG CMSIS-DAP (COM10) For the native port: Arduino Zero (COM12) If it shows something else you may have the wrong drivers loaded. Windows will of course assign different COM port numbers. If it shows nothing I have no further thoughts, but perhaps you might wish to try on another computer or contact your vendor for RMA information.

  3. On either port, when it's active you can right mouse click for properties. Check through all the settings. Under Details, the Device Instance Path of the EDBG port of my zero will show VID_03EB and PID_2157. The rest of the value contains the Serial Number of your device, and other information.

  4. The VID of 03EB is Atmel. My Zero board has both Atmel and Arduino logos on the back. The PID of 2157 is apparently assigned to the zero, may have a different PID (and this may be the problem!). These values are flashed somewhere in the bowels of the chips. The native port will have a different VID and PID.

  5. What I have seen is on Windows 7.1 and 8.0, 64-bit. Different versions of Windows do things a little bit differently, so you will have to peek and poke and fiddle around.

  6. To reload the drivers, disconnect your computer from the internet (because otherwise Windows will helpfully find some wrong drivers somewhere on the internet).

  7. From the device manager you can uninstall the drivers that Windows wrongly installed, then install the right drivers from the drivers directory in your Arduino installation. Before doing this you might wish to read the text of the arduino.inf file, it should contain the lines:, USB\VID_03EB&PID_2157&MI_01, USB\VID_2341&PID_804D&MI_00, USB\VID_2341&PID_004D

The information in this .inf file populates all the details that you saw from the Device Manager. You can also examine this with regedit under HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Enum\USB, and if you are bold you can change this information.

I should note that when I install Arduino software I download the zipped package and unzip it. I find that the Windows installer arduino package hides things too well for me, and prevents installing multiple versions of arduino software.

Let me know how this works out for you.


I Uninstall the re-install it. however During the installation when i reached the step to select the required file, after selection of the Arduino.inf the pop up windows appear, stating.

"the folder specified doesn't contain a compatible software driver for your device. if the folder contains a driver, make sure it is designed to work with windows for 32-bit systems"

yes the below are mentioned in the .inf file, USB\VID_03EB&PID_2157&MI_01, USB\VID_2341&PID_804D&MI_00, USB\VID_2341&PID_004D

still i am having the problem

Hello amerlagha,

We have reached the limit of my debugging experience. You might need to contact the vendor of your zero to get it replaced.

Here is the last little bit that I can suggest.

  1. Those mini-usb connections are in my view a weakness of this product It is possible for the cable to seem to be seated when it is not fully in place. But since you are getting this far in the driver installation, that is very unlikely.

  2. You might find a friend with 64-bit Windows and test on his system to isolate the problem to either your windows system or the genuino zero unit.

  3. As the Genuino Zero is a very recent product it is remotely possible that the VID and PID recorded on your unit is different from the ones in the .inf file, if so and you can somehow determine what values your unit has you can edit the .inf file accordingly.

  4. Again, as the Genuino Zero is recent, it is possible that your unit is defective, perhaps a bad solder joint or an out-of-tolerance part was used, or else the manufacturing failed to install the right VID, PID, or boot loader, or a unit that failed their testing was shipped accidentally. Your vendor is your recourse.

That's all I can think of, but maybe some other reader of this forum will have the correct answer for you.

Hello amerlagha,

I had one more thought, which might just solve your problem.

In the arduino 1.6.6 there is a file "genuino.inf" containing the following two lines:, USB\VID_2341&PID_824D&MI_00, USB\VID_2341&PID_024D

These lines are not present in the arduino 1.6.5 drivers directory.

So it may be that the genuino zero has different PID values than the arduino zero. The 1.6.6 did not include the edbg in this, I don't know why, so someone more aware of USB drivers and the genuino may have to answer the question. Since 1.6.6 dates only from earlier this month, it may be that 1.6.6 was shipped without being tested on the genuino zero.

In simple terms, you may be able to get the drivers for the native USB port to work for you. It is just as good as the edbg port for developing under the arduino ide.

You might want to look at the arduino software daily build to see if support for the edbg port has been added to the genuino.inf file.

I do want to commend you for being a pioneer adopter of this product, I expect will resolve the issue soon. Keep up your good work.


are you connecting to the laptop using a USB HUB?

it’s really weird that the device is detected as MDR, may you paste here the Hardware ID detected by your PC, after conneting the board using both the Programming port and the Native port?
you can find the Hardware ID by opening the properties of the device in the device manager like the following

Hi guys,

Finally it is working.

My mini usb port in Arduino was the problem. I press on the mini port while I am connecting it to laptop to ensure 100% connectivitey, and it is connected.

It worth to mention something really weird that the same cable and the same arduino are working fine in other laptop before resolving the problem.

It seems The mini port was little bit bigger then the standard or the usb cable was smaller then the standard...

Thank you everybody.

Hello amerlagha,

That's great news. I knew that the USB connection would sometimes not connect, so this gets added to the list of Frequent Issues. Maybe it also depends on the temperature or humidity.

Which USB port works for you, the native port or the programming port, or can you also get it to connect on either port?