Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.

lindros2

macrumors 6502a
Mar 21, 2011
927
572
Another Apple bug, they deny.
2 hours with support, nothing. Except an Apple employee in Austin stalking my web site.

Classy, Apple. Also interesting their support (or legal) is running "Mac OS X 10.14.0")

1606403819387.png
 

opanto39

macrumors newbie
Nov 27, 2020
7
3
The solution is rather simple. Although there are many reasons for error 4000, including a bad cable - in this case there is a problem with updating via Windows 10's current version of iTunes and it is related to having a pass code and lock screen. Temporarily disable 1) your device pass code 2) screen autolock and try again. This solved my problem on 3 separate iOS devices. Once updated via Win10 iTunes, I simply turned my device pass codes and autolock back on.
I've been getting this problem for a couple years, I always had to make space on the phone so I could do the update on the phone instead of from iTunes, but this solves the problem.
 
  • Like
Reactions: lindros2

mcadjgfrank

macrumors newbie
Nov 28, 2020
1
0
The solution is rather simple. Although there are many reasons for error 4000, including a bad cable - in this case there is a problem with updating via Windows 10's current version of iTunes and it is related to having a pass code and lock screen. Temporarily disable 1) your device pass code 2) screen autolock and try again. This solved my problem on 3 separate iOS devices. Once updated via Win10 iTunes, I simply turned my device pass codes and autolock back on.
Kudos to you! 👍 I receive the same error 4000 even though my iTunes Version is 12.11.0.26. Problem solved after following your instructions and using the exact same cable. Just register to say "really appreciate your help!"
 

lindros2

macrumors 6502a
Mar 21, 2011
927
572
The solution is rather simple. Although there are many reasons for error 4000, including a bad cable - in this case there is a problem with updating via Windows 10's current version of iTunes and it is related to having a pass code and lock screen. Temporarily disable 1) your device pass code 2) screen autolock and try again. This solved my problem on 3 separate iOS devices. Once updated via Win10 iTunes, I simply turned my device pass codes and autolock back on.
Having dealt with this on three phones and three updates, I now don’t agree with your “simple”. I’ve wasted hours backing up locally, only to have this sting me at the end. New iTunes, false hope. Coupled with failures on Easy Transfer to iPhone 12.
It’s a PITA when someone has Wallet/credit cards, Apple Pay, corporate stuff requiring passcode enabled... and Apple pushing for everyone to update (see Korean guy smashing MacBook).
It’s a bug in sloppy crap software which freezes, and the same but different error code on macOS.
 

Lio91

macrumors newbie
Dec 22, 2020
1
0
Hello all,
I have also followed this solution. It works perfectly.
Thanks a lot as the apple hot line was enable to do anything...
Regarding this error 4000 (itunes) and the fact the IOS update can't be neither done by wifi. Do you think this issue can be linked to hardware issue or is it definitively 100% software issue. I'm raising the question as this issue appears after having bought a SE2020, I installed the new iphone with IOS 13.5 and had each time after each new version the error 4000. This issue with IOS 13.6 & 13.7 and all the 14th... So I'm finally wondering as my phone is still under warranty if changing it for a new one would help solving this issue. Thanks for your feed back.
And again may thanks for this solution to avoid making an iphone restore.
 

redfox_tpa

macrumors newbie
Dec 22, 2020
1
0
The solution is rather simple. Although there are many reasons for error 4000, including a bad cable - in this case there is a problem with updating via Windows 10's current version of iTunes and it is related to having a pass code and lock screen. Temporarily disable 1) your device pass code 2) screen autolock and try again. This solved my problem on 3 separate iOS devices. Once updated via Win10 iTunes, I simply turned my device pass codes and autolock back on.
I've been trying to update for months every which way imaginable and gave up many times. I have to say the fact that such a far fetched, unthinkable remedy worked, "turn off passcode," shows the hype the glitter the gold is just cotton candy.
 

dariuxzy

macrumors newbie
Dec 24, 2020
1
0
The solution is rather simple. Although there are many reasons for error 4000, including a bad cable - in this case there is a problem with updating via Windows 10's current version of iTunes and it is related to having a pass code and lock screen. Temporarily disable 1) your device pass code 2) screen autolock and try again. This solved my problem on 3 separate iOS devices. Once updated via Win10 iTunes, I simply turned my device pass codes and autolock back on.
I have an iPhone 7, and at the time of updating it tells me the error 4000. Since I had not yet read this solution, I tried to restore it before updating but now in the configuration it says "Unable to activate", and if I want to update it it always tells me error 4000. What could I do? I've already tried to do it with another cable, and also with another PC, both windows and mac
 

ericwn

macrumors G5
Apr 24, 2016
12,118
10,910
Another Apple bug, they deny.
2 hours with support, nothing. Except an Apple employee in Austin stalking my web site.

Classy, Apple. Also interesting their support (or legal) is running "Mac OS X 10.14.0")

View attachment 1680263

Denial or lack of knowledge? I’m sure you helped them out then and provided the link this discussion.

How can a website be stalked, by visiting it?
 

MrsCasieri

macrumors newbie
Jan 4, 2021
1
0
Lawrenceville, NJ
The solution is rather simple. Although there are many reasons for error 4000, including a bad cable - in this case there is a problem with updating via Windows 10's current version of iTunes and it is related to having a pass code and lock screen. Temporarily disable 1) your device pass code 2) screen autolock and try again. This solved my problem on 3 separate iOS devices. Once updated via Win10 iTunes, I simply turned my device pass codes and autolock back on.
OMG, add me to the list of people who made an account to say thanks for this response. My son could NOT get the iOS update, which he needs to install the DoorDash app and *get a job*. Your response saved the day!! 🙌🏻👏🏻🎉
 

xskyfire

macrumors newbie
Jan 7, 2021
1
0
The solution is rather simple. Although there are many reasons for error 4000, including a bad cable - in this case there is a problem with updating via Windows 10's current version of iTunes and it is related to having a pass code and lock screen. Temporarily disable 1) your device pass code 2) screen autolock and try again. This solved my problem on 3 separate iOS devices. Once updated via Win10 iTunes, I simply turned my device pass codes and autolock back on.
i have just created an account here not more than 5 minutes ago just to type this comment and say a huge heartfelt "THANK YOU" to you.

i just got my iPad Pro 2017 back from an "apple certified" repair center due to Water Damage and had been shelved for the last 3 years (LCD, Flex, Home, and Sim Tray Damage accumulated). Obviously my iOS version got stuck in 11.4 and both via Settings and iTunes update didn't work until i disabled passcode lock.

YOU SIR ARE A LEGEND!
 

Man!c

macrumors newbie
Jan 11, 2021
1
0
I also just made an account to say thanks. It finally worked after driving me insane.
 

lelisa13p

macrumors 68000
Mar 6, 2009
1,946
47
Atlanta, GA USA
Does this action have to be performed every time that you want to update via iTunes, or is it something that is corrected and remembered by iTunes going forward? I decided to work around by disabling screen lock (but not passcode) and then using OTA for update, which got the job done for the moment.
 

corrtiel

macrumors newbie
Jan 22, 2021
1
0
The solution is rather simple. Although there are many reasons for error 4000, including a bad cable - in this case there is a problem with updating via Windows 10's current version of iTunes and it is related to having a pass code and lock screen. Temporarily disable 1) your device pass code 2) screen autolock and try again. This solved my problem on 3 separate iOS devices. Once updated via Win10 iTunes, I simply turned my device pass codes and autolock back on.
I've created an account simply to reply to this post. IT WORKS!!! Thank you so much. I've scoured the internet and came up with nothing...not even Apple's website included this information. Cheers!!
 

WaxedJacket

macrumors 6502a
Oct 18, 2013
690
1,071
The solution is rather simple. Although there are many reasons for error 4000, including a bad cable - in this case there is a problem with updating via Windows 10's current version of iTunes and it is related to having a pass code and lock screen. Temporarily disable 1) your device pass code 2) screen autolock and try again. This solved my problem on 3 separate iOS devices. Once updated via Win10 iTunes, I simply turned my device pass codes and autolock back on.
I remember doing this in early 2020 and for some reason I had totally forgotten about this fix. Digging through some searches I found your comment and it hit me "ah-ha!"

Hopefully I can remember this the next time I try to update via iTunes.
 

alzoo

macrumors newbie
Apr 28, 2013
5
2
The version of Windows 7 or 10 should not matter. Deactivate your pass code and lock screen, plug in your device and then try and update.
Hi guys, just want to say this worked for me on the latest itunes 12.11.0.26 on windows 10 updating an iPhone 12 pro from 14.3 to 14.4.1 It did remove all my cards in Apple Wallet which I had to add back..
 
Last edited:

bezoss

macrumors member
Jul 24, 2019
31
13
I really wish Apple would fix their bug. I am doing over the air updates to avoid the hassle of having to re-add all my cards. This is still broken even under latest itunes 12.11.3.17.
1 year later we still cannot update our iphones with itunes without a stupid workaround.
what is happening?
 
  • Like
Reactions: smorrissey

Oxie

macrumors newbie
Sep 23, 2020
4
2
Bezoss, the last version that updated normally for me was 13.7 and since updating to 14.0 on 23 Sep 2020 it has not updated normally giving the 4000 error. I wish they would fix it. Oxie
 

Oxie

macrumors newbie
Sep 23, 2020
4
2
Sorry Bezoss. I just reread your post. You were asking about version of iTunes, not IOS. Looking back at my records V 12.10.1.4 all worked normally. I am not sure if my problems began when I updated to 12.10.8.5 on 15 Sep 2020 or 12.10.9.3 on 23 Sep 2020. Has anyone determined if the fault lies with the version of iTunes or IOS? Lyn
 
  • Like
Reactions: bezoss

BrianC0000

macrumors newbie
Jul 20, 2021
1
0
The solution is rather simple. Although there are many reasons for error 4000, including a bad cable - in this case there is a problem with updating via Windows 10's current version of iTunes and it is related to having a pass code and lock screen. Temporarily disable 1) your device pass code 2) screen autolock and try again. This solved my problem on 3 separate iOS devices. Once updated via Win10 iTunes, I simply turned my device pass codes and autolock back on.
While the solution does seem simple, I'd hardly call it a solution... it's a workaround to a pretty large bug that a LOT of people are clearly encountering. I work for a software company, and this would not be at all acceptable in my organization. That said, I believe I have a workaround which eliminates the need to disable your passcode. Disabling passcode means re-authorizing apple pay cards and the like, which is just not acceptable to me.

That said, I can get iTunes to update my phone in this manner without disabling the passcode:

1 - Request the update in iTunes with the phone connected and unlocked as you normally would.
2 - Let it FINISH downlaoding and extracting the software - be patient.
3 - As the phone is being backed up by iTunes, navigate (on the phone) to the OTA Update screen... and WAIT...
4 - When the phone backup progress bar in iTunes is ALMOST done, request the OTA update on the phone... (Download and Install)
5 - The iPhone/iPad will actually be updated via iTunes after entering your passcode one more time. Works every time!

It's like the phone is not going into some update mode or whatnot, and requesting the OTA update at the right time allows it to accept the update from iTunes (my working theory).

Good luck all... I sure hope Apple decides that those of us who prefer to update via iTunes for a variety of reasons are important enough to actually fix this issue.
 

lelisa13p

macrumors 68000
Mar 6, 2009
1,946
47
Atlanta, GA USA
While the solution does seem simple, I'd hardly call it a solution... it's a workaround to a pretty large bug that a LOT of people are clearly encountering. I work for a software company, and this would not be at all acceptable in my organization. That said, I believe I have a workaround which eliminates the need to disable your passcode. Disabling passcode means re-authorizing apple pay cards and the like, which is just not acceptable to me.

That said, I can get iTunes to update my phone in this manner without disabling the passcode:

1 - Request the update in iTunes with the phone connected and unlocked as you normally would.
2 - Let it FINISH downlaoding and extracting the software - be patient.
3 - As the phone is being backed up by iTunes, navigate (on the phone) to the OTA Update screen... and WAIT...
4 - When the phone backup progress bar in iTunes is ALMOST done, request the OTA update on the phone... (Download and Install)
5 - The iPhone/iPad will actually be updated via iTunes after entering your passcode one more time. Works every time!

It's like the phone is not going into some update mode or whatnot, and requesting the OTA update at the right time allows it to accept the update from iTunes (my working theory).

Good luck all... I sure hope Apple decides that those of us who prefer to update via iTunes for a variety of reasons are important enough to actually fix this issue.
Given that I've been updating OTA for more than a year and having to manually backup my iPhone and iPad Pro first, this is something I plan to try this weekend. I hope it's a solid workaround for me, too! Will update this post with results of process.
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.