So what if the only Winsock Provider listed is the Bonjour Namespace Provider?

AppleMobileDeviceService.exe is constantly hogging one CPU on my machine. I've tried the Winsock command line reset (netsh winsock reset) and that seemed to work for awhile. Then the problem reappears.

I've tried stopping/starting or restarting the processes via the MS Services interface, and again, this resolves the issue temporarily. I've also, mostly out of frustration, stopped the process manually. Always comes back.

I've taken a look at Apple's suggestion (TS4123) which implies that their is some sort of conflict with another program. Back to my initial question:

So what if the only Winsock Provider listed is the Bonjour Namespace Provider?

Overall, at this point, I have to agree with the vast majority of users who are capable of both recognizing that this is a problem and troubleshooting it to this point: This is an Apple problem and it needs to be fixed by Apple, not passed off as a conflict from some other program that is "doing something wrong" in the eyes of Apple.

My next step is to continue troubleshooting on my own to come up with a workaround solution that doesn't require me resetting winsock or killing multiple processes every day in order to use a processor that shouldn't be taken hostage to begin with.

Has anyone out there explored the onset of this problem (I've seen iTunes 10.5) in relation to updating devices via WiFi network (also iTunes 10.5 feature add?).

I'm going to start by there and disable updating of all devices over WiFi to see if that prevents the CPU hogging. Hopefully that's not it, because that sure is a great feature.

As a Mac user since 1985 and a M$ programmer for more than a decade, this is an extremely disappointing problem and one that should be an easy fix considering the resources AAPL manages to accrue.