Arduino Mega not recognized by PC

Hi,

I'm new here, it's my first post in the forum. First at all, I'm sorry for my poor english

I can't solve my problem, that is identical to the one in this video:

My Arduino Mega 2560 can't be recognized by my computer with Windows XP, while it has no problem with arduino Uno. However, both Mega and Uno works correctly in my other computer with windows 10.

Have someone had an similar problem and can help me?
Thank you

Install the drivers on the XP system.

Note that if the board is a clone, it may use a different serial adapter and hence need different drivers. Look at the black chip near the USB port - it will either be a 16u2 (uses normal arduino drivers), CH340G, CP2102 or FT232. If it's something other than a 16u2, google the part number, and "windows XP drivers", download and install.

Hi Drazzy, Thanks for you reply.

My board isn't a clone and the chip near the USB port is a 16u2.

Anyway, maybe I used the wrong verb: my board is not even DETECTED from computer with windows XP, while there is no problem with my other computer with windows 10.

I followed your advice anche I tried to install new driver for 16u2 that I found here:

but the problem persists.

Then I also downloaded the new Arduino IDE 1.8.3, but nothing is changed :frowning:

Do you get the message of new hardware detected and a device in device manager (possibly an unknown device - which indicates driver problems)?

If you do, do you have it selected in the IDE?

(note - I have not watched video - I don't watch videos)

Are you using a known good USB cable? Seeing LOTS of complaints about bad USB cables lately.

Are you using a known good USB port? USB 3.0 ports are probably not a good bet, particularly on XP.

Hi Drazzy, I finally solved my problem!
Until this morning my arduino mega can't be detected even in device manager. But after that I downloaded the IDE installer again (not the zip-folder) and installed the driver for atmega16u2 the hardware is detected in the device manager as unknown device in device manager. Once I saw that, the problem became simple to solve.

To be honest I don't know if this is due to the new IDE or to 16u2 driver or something else...

Anyway, I really want to thank you for your patience!