2 Replies Latest reply: Nov 16, 2013 11:25 AM by Levoy Hurley
Levoy Hurley Level 1 (105 points)

My iPhone 5 has been doing just fine until I did the latest iTunes update a couple of days ago.  Now I get an error (-50) and it kicks out when I plug the iPhone in and it tries to sync.  A hard power off/on of the iPhone fixes the problem - until the next time I plug in for a sync. 

iPhone 5, iOS 7.0.3
  • norm123 Community Specialists

    Hello Levoy


    Typically, error -50 is due to it connection to the computer via USB cable lightning or 30-pin cable or through other software on the computer. I have provided the steps to troubleshoot the issue further.


    iTunes: Specific update-and-restore error messages and advanced troubleshooting



    Error 13, 14, 35 and 50 (or -50)

    These errors are typically resolved by performing one or more of the steps listed below:

    1. Perform USB isolation troubleshooting, including trying a different USB port directly on the computer. See the advanced steps below for USB troubleshooting.
    2. Put a USB 2.0 hub between the device and the computer.
    3. Try a different Dock Connector or Lightning Connector to USB cable.
    4. Eliminate third-party security software conflicts.
    5. There may be third-party software installed that modifies your default packet size in Windows by inserting one or more TcpWindowSize entries into your registry. An incorrectly set default packet size can cause this error. Contact the software manufacturer that installed the packet-size modification for assistance. Or, follow this article by Microsoft to reset the packet size back to the default for Windows: How to reset Internet Protocol (TCP/IP).
    6. Connect your computer directly to your Internet source, bypassing any routers, hubs, or switches. You may need to restart your computer and modem to get online.
    7. Try to restore from another known-good computer and network.



    -Norm G.

  • Levoy Hurley Level 1 (105 points)

    Thanks, Norm, but most of that note looks like it's for Windows.  The good news is that I haven't gotten the error since installing the recent iTunes updates.  It's probably too soon to say for sure (I also updated iOS last night) but the problem may have solved itself.