Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
Nervous about rebooting it while it is still in the "install phase". Don't want to risk corrupting the install. I think I may just wait it out.

Shouldn’t cause any issues - it should pick up right where it left off - but I don’t blame you. I’ll let mine go for awhile and see what happens this time. I can always use my old MB Air as a backup while i unwrangle this mess.
 
started hours ago in delaware on comcast. failed, repeated a few times. rebooted. gave up. started again 30 minutes ago and got the dl in 15 min. after the dl finished, the safari 14.0.1? update appeared. ran that then Big Sur. several auto reboots and now installing. 29 min and counting. done!
 
  • Sad
Reactions: Babygotfont
Took an hour for Big Sur to install on 2014MBA.

everything is working fine so far.

No 4K videos on YouTube. Even though my 10 year old Dell with Win8.1 can play 4K videos with lower screen resolution than my MBA.
 
My solution on Late 2013 MBPro was switching from Canada/USA to Hong Kong via Nord VPN. Once connected to Hong Kong the download started and completed with no issues.

After 45 min install Big Sur up and running perfectly.

Spent the afternoon searching for download links as the update stalled with error message advising of failed install. Tripped across this thread and originally skimmed over reference to VPN (too complicated were the implications!!??). In process of creating boot drive for beta version install thought I'd run my VPN only to discover USA continued to fail but Hong Kong worked!

Now on the hunt to figure out a Big Sur install path for my 2012 Mac Mini (i7-CPU/SSD/16GB RAM).
 
"About 12 minutes remaining..."

1605235466966.png
 
Waitasecond - are you saying that if we get the 'installation failed' message, we have the update downloaded and it is simply not able to install?

That is a different kind of problem, if that is what is happening.

My interpretation until reading your post was that the problem was accessing one of the Apple servers in order to pull the upgrade file. I do not think that my earlier upgrade attempts were successful in getting the full download to my computer . . .
I saw it said fully downloaded (12 GB or so) and then gave that error.
 
Finally finished installing and had a chance to look around. I'm not sure if I like the iOS-like design but maybe it'll grow on me.
 
  • Like
Reactions: Dekema2
Pathetic.

Netflix, etc, can handle the load when a new movie or TV series is dropped. You'd think Apple would've figured this out by now.
I can appreciate some disappointment, but given what we all paid of this upgrade (nothing), and given the pent-up demand, the bandwidth requirements must be huge, and configuration errors can happen.

I have a good background on issues like this....in. my former job we prepared payment processing systems for the deluge of transactions associated with Black Friday and the holidays. Volumes could go up 400% to 500% and you needed to handle it. While things were configured for failure is not an option, failures happened. Learning experience each year. The key take away is don't make the same mistake .... twice.

I assume everything you do is well honed and delivers to perfection.
 
Finally done installing with a few 'restart because of problems' messages. That plus the download issues really look like amateur hour, pretty embarrassing for Apple.
 
I can appreciate some disappointment, but given what we all paid of this upgrade (nothing), and given the pent-up demand, the bandwidth requirements must be huge, and configuration errors can happen.

I have a good background on issues like this....in. my former job we prepared payment processing systems for the deluge of transactions associated with Black Friday and the holidays. Volumes could go up 400% to 500% and you needed to handle it. While things were configured for failure is not an option, failures happened. Learning experience each year. The key take away is don't make the same mistake .... twice.

I assume everything you do is well honed and delivers to perfection.
Let's have a moment of silence for the Apple IT Engineers who won't be with us tomorrow. :(
 
Finally completed. Strangely, the wired ethernet connection was not set to any kind of DHCP so I had to set that and then it recognised the connection. Works now.
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.