Currently Being ModeratedNov 11, 2011 1:08 PM (in response to NotImpressedApple)
Did you invoke the CMD window with Admin privileges? This is a basic question, but I wasn't to make sure that's not the difference.
Currently Being ModeratedNov 20, 2011 6:50 AM (in response to kpm800)
I have a Windows 7 laptop. Ran Windows Update to get all latest critical updates and patches - have no idea if this affected the fix but thought I would include it in my post. Can't remember who originally posted this CMD but opened CMD prompt under "run as administrator." Ran the following command:
netsh winsock reset
Rebooted and all is well with the world. The Apple Mobile Devices service no longer consumes 50% of the CPU cycles and I can now access the Apple Store via iTunes.
Also, someone else on this thread mentioned to set the Apple Mobile Devices service to start in "Automatic (delayed)" mode. This seemed to also greatly improve boot up time on my computer.
Currently Being ModeratedNov 20, 2011 1:18 PM (in response to potestas)
Yes, this was my experience as well the Winsock Reset was the fix for me, both for the CPU utilization problems and for the inability to access the Itunes Store.
Currently Being ModeratedNov 25, 2011 10:32 PM (in response to kpm800)
AppleMobileDeviceService.exe (part of Apple iTunes) may cause very high CPU usage. Typically it consumes one whole (logical) CPU.
There is an easy fix for that – restoring winsock catalog. Open Command Promt with Administrator’s privileges and run:
netsh winsock reset
then reboot Windows.
Currently Being ModeratedNov 26, 2011 5:24 AM (in response to Madblaster6)
So we've established that winsock reset works for some people, which is good.
However, it seems that Apple couldn't give a toss about the conflict that there seems to be with a number of brands of child protection software, for which the only "solution" has been to uninstall that software. That is NOT an acceptable solution.
Currently Being ModeratedNov 26, 2011 10:32 AM (in response to GoochyB)
I realized after I did that my network card program started to say that my LSP is wrong and asked me to change it. I said yes and it started going crazy again. I also couldn't connect to iTunes store durring all of this. So I ran the command again and it went back to normal. I have a bigfoot netwok card. I stopped the software from running. I even got improved netwok speeds after and itunes store connected in seccons. What ever it is. t has to do with the netwrk.
Currently Being ModeratedNov 29, 2011 5:54 AM (in response to Madblaster6)
Open Command Promt with Administrator’s privileges and run:
netsh winsock reset
then reboot Windows.
Thank you very much, that fixed it!!!
Currently Being ModeratedNov 30, 2011 1:24 PM (in response to Madblaster6)
YES! YES! YES!
Just bought the Iphone 4S and couldn't get sync to work: finally! Thank you Madblaster6.
My CPU isn't burning out of my pc anymore!
(now solve my other problem: charger is getting very hot and smells like burned plastic: it doesn't charge. But that is another *hot* issue)
Currently Being ModeratedDec 6, 2011 5:32 PM (in response to Jack-NL)
Can someone write down the steps a little more descriptively? I'm not savy enough to follow what the solution is here.
Currently Being ModeratedDec 6, 2011 11:54 PM (in response to kpm800)
I was also struggeling several weeks with this problem. None of the above solutions worked for me.
Finally I got iTunes running after unistalling some software from Vodafone (Vodafone Connector and Vodafone Mobile Connect).
May be this info will help some others as well.
Currently Being ModeratedDec 24, 2011 9:17 AM (in response to kpm800)
I don't sync wirelessly because it needlessly eats power, and all my data are stored on local devices, not in iCloud. My Apple devices sync with a meticulously-maintained Windows Media Center 2002 box.
Why aren't there simple means to tune or disable the components not needed while idling? Running the latest version of iTunes (10.5.2.11), iTunes uses the following program components when it's not open, doing absolutely nothing useful for me:
AppleMobileDeviceService.exe 18 MB
distnoted.exe 7 MB
iPodService.exe 9 MB
iTunesHelper.exe 24 MB
mDNSResponder.exe 5 MB
SyncServer.exe 20 MB
These total 83 MB while doing absolutely nothing useful. That's far too much idling memory devoted to programs that are doing nothing. And the idea of an uninstall and reinstall while holding your left arm skyward and scratching your right calf with your left big toe is typical software maldesign and bloat. They should instead be shut off when they're not used, and *there should have been a pilot program that starts them and shuts them off when they're not used.* Simple idea, easy for Apple to have done. But instead they've used the Windows approach of sucking power from the machine hoping not enough people will notice or care.
Currently Being ModeratedDec 24, 2011 9:50 AM (in response to Blue Planet Man)
No worries, Blue Planet Man. The good news is that things don't work like you think they do.
Server processes that aren't doing anything don't slow you down measurably, and memory that isn't being actively used will be paged out when something else needs it. All operating systems handle server processes and memory like that.
Apple has plenty of problems w/ iTuens and its server processes in terms of how they actually work, but neither of the things you listed is a concern. Hope that helps!
Currently Being ModeratedDec 24, 2011 10:18 AM (in response to Mike S HT)
Thanks, Mike SH T: What's said to work in theory, and what happens in practice are two different experiences. If all the memory resident Apple processes I listed are shut off, the machine is noticeably faster and more responsive. I find that to be the case with memory resident bloat on any Windows machine, no matter the flavor.
Currently Being ModeratedDec 28, 2011 8:47 AM (in response to edwardfromseekonk)
Unfortunately, "it depends". On Windows 7, here's what I do:
- Click the round "icon formerly known as the Start button" in lower left of your screen
- Type "cmd" in the "Search programs and files" field -- but DON'T hit <enter> just yet
- "cmd.exe" will show up as one of the found Programs...
- Right-click on "cmd.exe" and choose "Run as administrator"
- Issue your "netsh winsock reset" command
By the way, this worked for me! Got my CPU back :-)
Currently Being ModeratedDec 28, 2011 10:54 AM (in response to jefflogullo)
In my case the command "netsh winsock reset" worked and my CPU usage gets back to normal, BUT the "filternet" Parental control service stopped working. After re-installing "filternet" the CPU was hogged again.
Filternet has confirmed this is problem they are working on.