446737 Views Previous 1 2 3 … Next 207 Replies Latest reply: Apr 15, 2015 5:42 AM by akshaypatil1234
I too am facing the same problem... I updated to 8.2 and updated my iphone to 3.0. At first itunes displayed a message saying my iphone was detected but couldnt be identified properly and said to disconnect and reconnect. I did so and now it says "iTunes could not connect to this iPhone because an unknown error occurred (0xE8000065). And everytime I unplug and reconnect iTunes displays this message, and sometimes it doesnt even recognize my iPhone. My pc recognizes the iPhone as a Camera(??) but iTunes does nothing... nonetheless iTunes syncs my sons iPod....
I have also gone and removed iTunes and then reinstalled as mentioned in the support page (http://www.apple.com/support/iphone/troubleshooting/itunes/#), but the problem still exists....
I have the same issue. Also on a DELL. Since half a year I could only work around this problem with running the iphone on a motiontablet LE1700 with Windows Vista.
On the DELL it didn't work with WinXP (0xE8000065), then I installed Windows 7 RC, the same error came up. However when having the USB connection on the front of the DELL PC, Windows 7 said that AppleServices were successfully installed but "MTP USB Device" failed to install. On a USB Hub, no errormessage came up from Windows 7, however, above error message appears when trying to restore the iPhone
I bought my iPhone brand-new. always had apple products (even a macintosh portable which weighted kilo's...) but not even apple responded to this error. I would be extremely grateful if somebody can look into this. I am also willing to provide more information.
Message was edited by: oliveranthony
Message was edited by: oliveranthony
Interestingly enough, after switching from front USB connectors to a hub, iTunes pointed out an error and showed up the iphone twice (as iPhone and <<Name>>'s iPhone. Afterwards it demands to restore the iPhone.
I can only assume that MTP (Media Transfer Protocol) from M$ could be causing issues here. I recognized now that Windows Mediaplayer comes into NotResponding State when trying to restore the iPhone. When fiddling around with WMplayer in that very moment (= pressing play) also iTunes ceases living. (I did not reproduce this on XP though)
Windows Media Player 12.0.7100.0
Help is still appreciated
- Complete Reinstall of iTunes (incl. Bonjour, Apple USB Driver etc.)
- Restore of iPhone conducted on 2nd PC (motiontablet LE1700, vista)
- Connected over USB front connector of DELL XPS420 -> iTunes does not detect iPhone
- Connected over USB hub on DELL (Hub is plugged in at the backside) -> iTunes detects iPhone
-> iPhone get's recognized, did not restore from backup. Complete new config and new name for iPhone, works well
However: After adding 1(!) music file to the newly installed iTunes and pressing "Synchronize", the following happens:
- iTunes freezes for 3 Minutes
- Error: Copy attempt to Volume "....'s iPhone" has failed. The attempt to establish a connection to ... has been aborted due to a timeout
- Error: iPhone cannot be synchronized
-> Plugging it out of the USB Hub and now back into the front connector, reproduces Error 0xE8000065
hope this helps to pinpoint this thing a bit better?
I discovered that there Windows 7 is always trying to install a "MTP USB Device". Interestingly, when I switch to a USB Hub, Windows 7 does not try to link the MTP USB Device to it. However that is only the first part.
If Windows Media Player is present on the Computer, there seems to be a protocol clash. If I have the iPhone connected over the USB Hub and I completely remove Windows Media Player over the Systems Panel (Turn Windows features off -> Media Features UNTICKED) and restarted, it works.
here in short:
-Reinstall USB Apple Driver
-Plug in iPhone, forcefully choose Apple Driver (instead of MTB USB Device)
-Check in Control Panel if MTB USB Device is NOT present under "Portable devices" (worked on my DELL XPS420 with using an USB Hub // Otherwise Windows will keep you prompted with the MTP USB Device Driver)
-Completely turn off Windows Media Player Features (Control Panel - Programs - Turn on and off windows features - Media features UNTICKED)
However, the question will still be open...I don't think that de-installing Windows Media Player is a valuable option? I guess Windows 7 struggles with the DeviceID and WMP/iTunes struggles with using MTP vs. Apple Device Driver...
For older versions of windows I guess the three options which you have to check through (in all combinations):
-Check with an USB Hub OR
-Check with rear USB connectors OR
-Check with front USB connectors OR
-Either update Windows Media Player to 10 (11 would be better) OR
-Completely remove Windows Media Player
I guess people tend to disregard this problem as it needs to have an exact combination of USB Problems and WMP/Media Transfer Protocol Issues.
I would appreciate someone from Apple Support can confirm this bug?
Finally fixed it. I don't trust DELL internal USB HUB's.
I guess what happens is the following, the chipset of the DELL USB Hubs seems to add nonsense characters to the iPhone DeviceID (VID05AC&PID1292) in my case it added a 2nd Device plus "&MI_00" (VID05AC&PID_1292&MI00). Resulting in two devices being "connected". While this might be OK - I'm not a HW Person - it lead to Windows 7 believe the second is a standard MTP Device. Whilst the DeviceID has not been used for the second, I guess it run's over the deviclass (Class06&SubClass_01&Prot01).
So it's trying to install it as a 2nd MTP Device which then results in the protocol clash & timeouts between Apple USB Driver and Windows trying to speak over MTP.
- Bought a VIA PCI USB 2.0 Host Adapter (Via Chipset)
- Plugged my iPhone into it
- Enjoy my music and other features.
Maybe my journey is of help to anybody.
I will now reinstall Windows Media Player and see if the problem is definately gone.
I found a fix that might work without getting a card. Something you should check in the bios is enabing C-state mode on the processor. This is a hardware monitoring/low voltage and frequency mode for cpus to save power on different cores. It also apparently has something to do with the power output to the usb chipset. I was trying everything prior to this including running a vm of windowsxp to see if it was a driver issue, but after I enabled c-state in the bios, everything worked out. My system was a newer core i5 system with a p55 chipset. I was running windows 7 64 bit RC. Please post if this is successful for anyone else.