Hello All. I have a promblem when i installed arduino on my windows 7. I've installed it again and again but i don't get what i want XD
CH340 driver
Mm, non of my CH340 Arduino's is detected as Arduino Uno...
Is it indeed a real Arduino (aka, you didn't bought it on eBay/AliExpress/Amazon/China)?
If so, you can try to manually update the driver. Right click => Update driver => Browse my computer => Let me pick => Have disk => Goto the driver folder inside the Arduino folder (program files if you installed Arduino IDE via the installer).
septillion:
Mm, non of my CH340 Arduino's is detected as Arduino Uno...Is it indeed a real Arduino (aka, you didn't bought it on eBay/AliExpress/Amazon/China)?
If so, you can try to manually update the driver. Right click => Update driver => Browse my computer => Let me pick => Have disk => Goto the driver folder inside the Arduino folder (program files if you installed Arduino IDE via the installer).
i had done it XD but stay that way.
it's Arduino Uno
ppabcd:
it's Arduino Uno
We can see that 
But is it a real one or did you buy it on Amazon/eBay/AliExpress etc?
i'm buy it in my friend and my friend buy in Ebay
Then it's probably not a real Arduino then. Try the CH340 driver indeed. Or look closely at your Arduino and try to find a chip that has CH340 on it.
Examine the integrated circuit near the USB connector. It will either be an Atmel mega 16u2, a CH340G, an FT232R (probably fake and likely bricked by the driver update - this could be the problem - google FTDIgate for more info), or some other serial chip (theres one starting with PL, and one starting with CP - they're significantly less common though).
That will guide future investigation.
DrAzzy:
(probably fake and likely bricked by the driver update
If bricked Windows doesn't detect them as something useful so I doubt it.
Also, I thought the bricking driver was pulled back and replaced by one that simply doesn't work with fake chips or annoy the crap out of people by injecting messages in the serial data...
septillion:
If bricked Windows doesn't detect them as something useful so I doubt it.Also, I thought the bricking driver was pulled back and replaced by one that simply doesn't work with fake chips or annoy the crap out of people by injecting messages in the serial data...
Right, but the bricking driver could have previously bricked the board. The new driver doesn't unbrick fake chips that it previously bricked.
IIRC "bricked" FT232 devices still showed in device manager, but couldn't be made to do anything.
You're right. I thought Windows then didn't recognized it as all, so as a Unknown Device.
If you think it might be bricked, check the PID and VID.