itunes 11.1.4.62 breaks wifi sync

Just great, another buggy version passes by. Now what do I miss from 11.2?

I'm experiencing the same! Just to let you know that there are more people suffering like you... :-(

Hi guys!

I found something new which seems to work for me!

As stated in various posts, it helps to disable IPv6 for the network adapters. That was the case for me too until iTunes 11.1.4 arrived, then it failed.

Now I learned from other forums that just unchecking the TCP/IPv6 checkbox in the adapter properties does not completely disable IPv6 and sometimes even causes more problems. To completely disable IPv6 you have make a change in the registry in HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\TCPIP6\Parameters! You have to add or set the key "DisabledComponents" of type REG_DWORD to the value FFFFFFFF!

Now my devices no longer disappear and syncing works most of the time! (sometimes when the device is locked, iTunes still says "looking for iPhone... - not found")

Hope this helps!

We use iPV6 at work a lot it has great potential for QoS. see

I wonder if there is a much simpler way to mitigae this issue. BindIP binds an IP address to an app i wonder if this this app could be leveraged or if a similar app could simply turn off iPV6 *just* for iTunes ?

Sorry for the second post. But i just had another brain blimp.

I think the apple mobile device service is what controls the connection between devices and that is what and where the mitigation would need to be made.

You can see the service in windows by doing

Start > run > SERVICES.MSC

(CNTRL+SHIFT+Enter to launch it as admin i think)

Sorry for the premature cheer! Unfortunately I still see my devices disappear using the above mentioned IPv6 fix. But it seems to work "more often..."

Yes, iTunes 11.2.2.3 finally fixed the issue for me!

I found some more information that might be helpful about iPV6 disable in windows vista, 7 and 8.

http://eitwebguru.com/disable-ipv6-components-on-windows-vista-windows-7-and-win dows-server-2008/

The post goes on to talk about the different methods of disabling iPV6 but i have no idea what they mean.

Maybe someone with more technical knowlege could clear this up and we could use the correct iPV6 disable method. Essentially using a scalpal instead of a hatchet.

FYI: Following are the other values which you can use to configure the IPv6 protocols (From Microsoft Website)

1. Type 0 to enable all IPv6 components. The value “0″ is the default setting.
2. Type 0xffffffff to disable all IPv6 components, except the IPv6 loopback interface.
3. Type 0×20 to use IPv4 instead of IPv6 in prefix policies.
4. Type 0×10 to disable native IPv6 interfaces.
5. Type 0×01 to disable all tunnel IPv6 interfaces.
6. Type 0×11 to disable all IPv6 interfaces except for the IPv6 loopback interface.

Read more: http://eitwebguru.com/disable-ipv6-components-on-windows-vista-windows-7-and-win dows-server-2008/#ixzz338oYUhdB

Uh, why are we still discussing that instead of the new release?

Just thought it would be important to bring it up seeing iPV6 is important to the health of the internet.

The new version might not work for everyone.

DRSCEB wrote:

Uh, why are we still discussing that instead of the new release?

Yeah disabling an important thing to the health of the Internet...

Clearly success isn't the only thing worth discussing. How about your trial of the new version?

DRSCEB wrote:

Yeah disabling an important thing to the health of the Internet...

Clearly success isn't the only thing worth discussing. How about your trial of the new version?

Sorry, yea i should have said something about that as well. Fact of the matter is i've just become so disgusted with the hole thing ive given up.

I did try 11.2.2.3 and was able to see one of my devices for a short period of time but then when i tried to sync i got an error about the connection being reset. So i tried rebooting and starting the process again.

Same thing. Saw the device only this time just like before the device disapears immediately after.

A few other things i was trying today as well was switching up some of the files inside

\Program Files\Common\Apple\Mobile Device Support\

... with the ones from the old version of iTunes.

To the person above that wanted this reported to apple. I did already report the issue as well as filed a full ticket and sent them my system logs as well.

I think this issue stems from a problem with the iTunes UI itself and not so much the windows connection socket. Something is systematically wrong with the windows version of iTunes whithin the iPod service.

I should also probably add that none of my devices currently are modified in anyway by any 3rd party.

I have no pirated software on any of my devices or anything to suggest some 3rd party element might be interfering with the connection.

The problem is definitely on apples end. The apple is in their court now.