iPhone and Windows 7 don't play nice, Intel P55 chipset to blame

The iPhone is one of the most wildly popular phones the world has ever seen, while Windows 7 is well on its way to becoming the globe's most ubiquitous OS. So compatibility between the two would be kinda sorta important, right? Tell that to Intel's quality control team who seem to have somehow missed an issue between Apple's app carrier deluxe and the P55 Express chipset's USB controller. Consistent (and persistent) syncing issues have been reported on Apple's support forums, wherein iTunes on Windows 7 machines recognizes the iPhone, but spits out an "error 0xE8000065" message whenever the user attempts to sync. While some have found limited success with using PCI-based USB cards (and bypassing the chipset), this is clearly a major issue and something Apple would expect to be fixed before shipping its Core i5 / i7 iMacs, which are likely to sport the chipset. Hit the read link for the original thread of sorrow and regret, and do chime in with your own experience in the comments.

[Via The Register]

[(Unverified) Posted Oct 31st 2009 5:43PM]

"error 0xE8000065"

Hmmm, new OS, same retarded error messages that mean nothing to the user. So when is Microsoft going to learn how to make a user friendly OS? How many revisions does it take?

[A Man Posted Oct 31st 2009 5:28PM]

Clearly you have no reading comprehension skills.

[(Unverified) Posted Oct 31st 2009 5:49PM]

Comprehension is fine. iTunes is throwing an error. The error is a hardware based error that it is getting from the OS when it is trying to do a sync. The OS is telling iTunes the 0xE8000065 error that it is then just passing through. Instead the OS should tell the application something usable.

The blame for the error happening is intel, but Windows 7 should be handling it better than it is. iTunes is just talking through the USB driver. Drivers are the responsibility of the hardware and OS maker not the application vendor.

Windows versions throughout the years are full of these wonderful error messages in the OS errors, blue screen errors, application errors, office errors. Ever try and write something to automate an office product? Wonderful errors in that product telling you what is going on, not.

Learn how things work then post a meaningful response. You probably won't but that's par for the course.

[(Unverified) Posted Oct 31st 2009 6:36PM]

Some Windows API probably returned that error code, and iTunes is displaying it verbatim instead of formatting it with readable text. The OS isn't going to format error messages for you, that's up to the application. It's not going to know anything about the context. What do you expect it to say? What you want is some sci-fi artificial intelligence from the future that can deduce why the error happened, the context in which it occurred, and translate it into whatever user language the application is displaying.

[(Unverified) Posted Oct 31st 2009 6:30PM]

funny ive been using Windows 7 since the beta though the RC and now official, and have never had a sync error issue once with the iphone.

[(Unverified) Posted Oct 31st 2009 7:01PM]

painful

[(Unverified) Posted Oct 31st 2009 8:04PM]

My iPhone and iPod Touch work fine with Windows 7 Ultimate from Beta to Release without any errors - So it must be a hardware conflict

[(Unverified) Posted Oct 31st 2009 8:49PM]

No problems here. Win7 rtm and iPhone 3GS.

[(Unverified) Posted Nov 1st 2009 1:54AM]

I had the same problem (error 0xE8000065), but downgrading to iTunes 9.0.0 x64 seemed to fix the problem for me. Syncing now works fine.

You can find the old version at: http://www.filehippo.com/download_itunes_64/6156/

My System:
Intel Core i7 860
Gigabyte P55-UD3R

[(Unverified) Posted Nov 1st 2009 12:45PM]

Maybe by design... hmmm?