Previous 1 8 9 10 11 12 13 Next 193 Replies Latest reply: Dec 19, 2013 2:12 PM by Mike S HT Go to original post Branched to a new discussion.
  • Jelley2 Level 1 Level 1 (0 points)

    God Bless you Madblaster!  I haven't been able to run iTunes since October, and have spend hours on the phone with Apple tech support to no avail!  This worked.  Hope fix doesn't affect anything else, but at least I don't have to purchase a new computer, as was suggested to me by Apple tech phone support!

  • Madblaster6 Level 1 Level 1 (0 points)

    Yeah no problem

     

    here are the instructions again so people don't miss them.

     

    Also make sure you're not running the software that may reset it. Like my bigfoot ethernet card software kept reseting it.

     

    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.

     

    *Fixed*

  • dr_jon Level 1 Level 1 (0 points)

    The main issue with this is it'll probably unhook your Anti-Virus software from looking at anything coming from the internet. It does usually work around the problem though. (I found upgrading my AV was a final fix.)

    John

  • Jelley2 Level 1 Level 1 (0 points)

    Thanks Dr Jon, but "how do I know?". In the process of trying to eliminate any possible conflicts prior to this fix,, I removed all my anti software and installed only MS Security Essentials (which is probably like the fox watching the henhouse). If I go back and reinstall my McAfee, will it start all over or should the new install work around the ntshr winsock reset already performed? ( I'm way over my head here's you can probably tell).  I appreciate your help!

  • Mike S HT Level 1 Level 1 (5 points)

    This is long, but it includes an *easy* solution that works for me 100% of the time...

     

    Exactly, John.  A netsh reset to fix this problem is like reinstalling Windows (albeit on a smaller basis) to fix a problem w/ one program.  It will fix the program -- but can cause other hard-to-figure-out problems.  I had pointed that out on a different thread: "You'll also see solutions that use "netsh winsock reset".  That seems to work for some people, too.  But: the downside is that a reset may reset other things and require that other programs be reinstalled, possibly reintroducing this problem.  Make sure you do a "netsh winsock show catalog >c:\winsockcat.txt" first so you'll have a record.  I didn't try the reset b/c I'm worried about creating other problems."

     

    Here is my current solution for my iTunes problems, restating what I wrote above and elsewhere and adding a few tweaks.  I hope it helps someone else -- it makes iTunes usable for me.

     

    For the search engines, let me state a list of symptoms...

     

    Symptoms -- any of the following: iTunes hangs after launch; iTunes won't recognize your iPhone, iPad or iPod after you plug it in; Apple Mobile Device service uses up a lot of CPU; your iPhone/iPod/iPad/Apple TV won't connect to iTunes via Wifi (e.g. Sync with Wifi or making your iTunes library available to Apple TV).

     

    Workaround for when any of the above happens.  A little annoying, but only 20 seconds worth of work whenever you want to use iTunes to sync w/ your iPhone/iPod/iPad/Apple TV.  Works 100% of the time for me:

     

    --Exit iTunes.  Is your iTunes hung?  If so, use Microsoft's Process Explorer (free, search for it) or Windows' Task Manager (search for a tutorial) to kill itunes.exe.  For PE, Run as Administrator to be sure you can kill what you need to.

    --Unplug your device.

    --Log onto an admin account if you're not.

     

    --Go to the Start menu and type in services.msc (in Vista and Windows 7, type it in the search box; in XP, use the Run command).  [If you like, set up a desktop or QuickLaunch shortcut to services.msc for convenient access.  Be sure to set the properties to Run as Administrator.]

     

    --Scroll down to "iPod Service" and left click it once.  If there is a restart link on the left top, click it.  If not, right click iPod Service and select Stop.  Repeat, clicking Start.

     

    --Scroll up to "Apple Mobile Device" and do the same thing.

     

    --Open iTunes.  Wait a few seconds until it looks like it's done initializing.  Plug in your device or boot up your Apple TV.  That should do 'ya!  It will work fine until it gets hosed again -- simply repeat the process. 

     

    BTW, I now always right click on my device name in iTunes and select "Eject" before I unplug it.  I'm not sure that actually helps, but I'm trying it to see if it prevents hangs.

     

    If I wasn't clear above, let me know and I'll restate.  Again, 20 seconds for me to do the above -- it's an easy process once you have done it twice. 

     

    I suspect that the problems fixed by the above are conflicts between antimalware programs and Apple's software system that includes iTunes and the two helper services I listed.  I use Webroot and Comodo.  But, who knows -- I just know my solution works for me.  Good luck!

  • dr_jon Level 1 Level 1 (0 points)

    MSE's okay as an AV tool (I use ESET NOD32 BTW, using v2 had the problem, upgrading to v4.2 fixed it, which I had to do anyway as v2 was coming to the end of its life - I was only using as was more lightweight than v3).

     

    Listing the catalogue will show you what's hooked in (see the previous post, you will need to redirect it to a file as it'll be pretty long) and it's worth doing to see if anything's there that you think shouldn't be (i.e. you thought you'd removed).

     

    You get a lot of stuff like:

     

    Winsock Catalog Provider Entry

    ------------------------------------------------------

    Entry Type:                         Layered Chain Entry

    Description:                        NOD32 protected [MSAFD Tcpip [TCP/IP]]

    Provider ID:                        {74ED6954-26D5-4C7D-8F09-2FDF977B6329}

    Provider Path:                      C:\WINDOWS\system32\imon.dll

    Catalog Entry ID:                   1033

    Version:                            2

    Address Family:                     2

    Max Address Length:                 16

    Min Address Length:                 16

    Socket Type:                        1

    Protocol:                           6

    Protocol Chain Length:              2

    Protocol Chain: 1032 : 1001

     

    I'd just look at the Layered Chain ones first. Also if you do try the reset game doing another catalog will show you what got nuked, then you can reinstall and see what happens.

     

    Hope that helps...

    John

  • GoochyB Level 1 Level 1 (0 points)

    After denying that there was a problem Apple eventually published a "solution" on their website, which was to uninstall the content filtering software that iTunes was conflicting with - inspired, after all, who needs to protect their children or themselves online! 

     

    So Apple couldn't care about the problems that iTunes 10.5 causes, nor even explain why it is digging around within winsock at such a low level in the first place.

     

    Fortunately some of the content filtering software publishers have chosen to work around Apple's bug, and both Bsecure and SafeEyes have issued updates which mean that their LSPs make specific provision for iTunes' awkwardness.

     

    10/10 to those companies and 0/10 to Apple for their arrogant indifference.

  • Mike S HT Level 1 Level 1 (5 points)

    Thanks, GoochyB.

     

    For others, here's the article referred to: http://support.apple.com/kb/TS4123

     

    I always forget about MSINFO32 -- another good way to get some detailed system info.

  • GoochyB Level 1 Level 1 (0 points)

    Thanks for that Mike - that article is actually more recent than the one that I had seen, although not really any more helpful!

  • paulfromfarmingdale Level 1 Level 1 (0 points)

    Well said!

  • denomolos Level 1 Level 1 (0 points)

    Please Apple fix this with an update or tool you can run, I can't believe you haven't patched it. This is wide spread and makes iTunes worthless.

     

    You need to work better with security software, if that many companies are having issues with your software it would be best for you to fix it, right?

  • golfingdad Level 1 Level 1 (0 points)

    As someone that has beein in IT a long time, I was shocked at what the folks at the Apple store told me regarding this issue...(Note: I opened up an official support call with Apple and followed their tech doc #1923 to a T)

     

    The high CPU problem occurred immediately after turning on my PC, so on a recent business trip, I merely visted the genius bar...They told me, I had two options

     

    1) Reload my windows operationg system & truy again

    2) Stop using Itunes on my windows 7 Ibm think pad

     

    Incredulously, I asked (at the genius bar mind you...), is that really Apple's official response to my issue?!?

     

    The techie said, "I'm afraid sometimes it is"

     

    I said, let me get this straight...I've been using itunes with no problems for years... you guys introduce a bug with a new release of code, and now you want me stop using the application?!?

     

    What I always loved about Apple, is their level of professionalism and their focus on customer service. They were always striving to have impecable products and would NEVER go through the motions on any thing

     

    Genius bar...ya right

     

    This morning, I deinstalled itunes because I don't have time to fight my environment, especially when the high CPU issue is causing web meetings to fail

     

    Steve Jobs is rolling in his grave right now

  • MichaelBurg Level 1 Level 1 (0 points)

    Problem still exists in ver 10.6.1.7.  This fixed the problem. Won't know if it broke something else until I run it a while.  Thanks!

  • jamesmanning Level 1 Level 1 (0 points)

    I've had this problem with iTunes for ages (including current version, 10.7.0.21), and sure enough, the winsock catalog reset did the trick!

     

    Awesome!