-
All replies
-
Helpful answers
-
Nov 29, 2012 8:29 PM in response to Rdcapebtby erwinscott,I had the same problem. I just read that unplugging the wired connection and going wireless worked?? Not sure why but sure enough I just did it and it downloaded and installed.. Weird, I know...
-
Nov 29, 2012 9:14 PM in response to stevekorby insainlewey,Middle of update on ATV3. Moving VERY slow. Like 20 minutes to the half point slow. But still going. We shall see.
-
Nov 29, 2012 9:19 PM in response to stevekorby Dave Ings,My step 1 took roughly 45 minutes to complete. Step 2 took the normal 2-3 minutes and then all was well.
-
Nov 29, 2012 10:15 PM in response to stevekorby insainlewey,Update took 1 hour 15 minutes. And all is well!
-
Nov 29, 2012 10:48 PM in response to stevekorby Mikerbuddy,I downloaded it for my atv3 it downloaded just fine from wireless. I find the air play a lot less laggy with mountain lion as I can actually use airplay now
-
Nov 30, 2012 4:13 AM in response to stevekorby 5uck3rpunch,Man am I ever glad it was not only me with this issue. Really, W_T_F is going on at Apple these days? I think we have seen Apple's best days & we are on the downhill now. I hope I'm wrong.
-
Nov 30, 2012 4:50 AM in response to stevekorby adamfromorange,Mine took about 90 minutes and the last 50% of the progress bar seemed to take longer than the first 50% but it eventually got there and is working fine without any intervention needed.
-
Nov 30, 2012 4:51 AM in response to adamfromorangeby 5uck3rpunch,Did you update on wifi or thru ethernet? I'm going to try wifi when I get home later. No luck thru ethernet for me.
-
Nov 30, 2012 5:08 AM in response to indyhillby Gary Tate,Opened ATV this morning and it told me I had an update available right away... d/l went sucessful, update install sucessfull. took aprox. 5 min.
Servers must have been swamped yesterday.... guess its not a hobby
-
Nov 30, 2012 5:20 AM in response to JCShroyerby _systemaddict,Thank You
Your answer worked for me too. I removed the Ethernet cable and the update was successful over WI-FI.
-
Nov 30, 2012 5:28 AM in response to Gary Tateby 5uck3rpunch,@Gary - mine downloaded fine & it sounds like it did like others that posted here. It just failed during the install. MANY times. I will try wifi later like the others & keep my fingers crossed.... We need the old Apple back!
-
Nov 30, 2012 5:51 AM in response to stevekorby danjc2,I was having the same problem, eventually gave up and tried to do a restore via cable and itunes. iTunes 11 didn't recognise my Apple TV, but by chance I plugged my box back into a TV, and it booted with an update notification, blitzed through it in about 2 minutes. So something must be working, it just likes to take its sweet time doing so.
-
Nov 30, 2012 6:21 AM in response to WPOby WPO,After unplugging ethernet and updateing over WiFi -- success!
-
-
Nov 30, 2012 8:37 AM in response to stevekorby bravescoach,I have an Apple TV 3rd generation wired via Ethernet to a nearby router.
I had the 5.1.1 update fail on an Apple TV 3rd generation last night and this morning repeatedly. It failed at the end of Step 1 after about 5 minutes (progress bar would hang at the end), then an error message appeared saying that the "update was not successful" and suggested a restart.
- Soft restart and update did not work.
- Hard restart and update did not work.
- Reset to factory default did not work.
- Plugging into a PC with iTunes 11 via a micro USB cable gave the error message that hardware could not be located or something along those lines. I tried this on two Windows 8 64-bit PCs with fresh iTunes 11 installs.
I was going to attempt a restore from an iTunes 10 Mac today, which I have access to at work (BYOT school). Right before leaving for work this morning after several failed updates, I tried unplugging the Ethernet and connecting the Apple TV to my home WiFi network. Sure enough, the update only took about 5 minutes and was successful.
Bottom line, connect to WiFi for the update. The box is working fine after then reconnecting to Ethernet.
I wouldn't call this a fix, but a workaround.