Got a tip for us?
Let us know
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
"An error occurred while installing the selected updates."
- Thread starter SW3029
- Start date
- Sort by reaction score
Worse for me. I got this at first, then it finally downloaded, but now I am stuck in a loop at startup, and cannot get past the black startup screen. I get a message an error ocurred at startup, press a key or wait. Not good.
First, I trust you had a Time Machine backup before you upgraded....in case you need it. Second, did you try holding the Option key down when you turn on the computer to see if it loads the Startup manager? If it does, see if you can boot into 'Macintosh HD' (or whatever your volume is called).
Finally got it installed, biggest pain of an update I can remember. But wow is this new UI hideous. Looks so cartoonish and tacky, what were they thinking?!
Now that it has finally restarted to download does anyone know why the download starts quite fast (4.48 MB/s on my connection) but as the downloaded amount gets bigger, now at 10.14GB, the download rate gets slower and slower and is down to between 500 KB/s to 1 MB/s? This is not just Big Sur, I have noticed this on other very large downloads. Like everyone in the UK, who is not on fibre, I am on a line leased from British Telecom to my ISP, which is FTTC (Fibre to the Cabinet), where the last 1/2 mile from the cabinet to my house is copper. My nominal rate is 39 Kbits/sec = 4.8 KB/s on VDSL/2.
Not for me. Still errors out at the end and no installation
Still issues for me. Took 3 tries this morning to download the full file and then it just craps out and closes the download window. Download then has to restart from the beginning. This is on a March 2020 base Air. Not even going to attempt the upgrade on my main iMac until Apple sorts their s*** out.
same thing happened to me. i have already downloaded installation 12gb file twice. can anyone help me what should be done ?
Worked with Apple support this morning. Still had install error after download. He took all the log information with their support tool and handed it off to Engineering. 48 hours before he will tell me if they find anything. More than just me having issue he said.
i have completed the download, now preparing time machine backup of my Mac OS Catalina just in case if anything goes wrong during installation of Big Sur
Try this link:
macOS Sequoia
macOS Sequoia brings effortless window tiling, web browsing with fewer distractions, new iPhone Mirroring, and support for Apple Intelligence.
www.apple.com
Lou
Last edited:
Interesting .. & concerning that Apple's processes can compromise all macs & apps; I guess one answer is to take the computer off line when doing critical work. See https://arstechnica.com/gadgets/202...-temporary-slowdown-in-even-non-big-sur-macs/
The issues seemed to begin close to the time when Apple began rolling out the new version of macOS, Big Sur—but it affected users of other versions of macOS, like Catalina and Mojave. Other Apple services faced slowdowns, outages, and odd behavior, too, including Apple Pay, Messages, and even Apple TV devices.
It didn't take long for some Mac users to note that trustd—a macOS process responsible for checking with Apple's servers to confirm that an app is notarized—was attempting to contact a host named ocsp.apple.com but failing repeatedly. This resulted in systemwide slowdowns as apps attempted to launch, among other things.
The affected hostname (which is really just a pointer to a whole bunch of servers on Apple's CDN) is responsible for validating all manner of Apple-related cryptographic certificates—including the certificates utilized by app notarization. First introduced in Mojave and made mandatory in Catalina, notarization is an automated process Apple performs on developer-signed software:
The Apple notary service is an automated system that scans your software for malicious content, checks for code-signing issues, and returns the results to you quickly. If there are no issues, the notary service generates a ticket for you to staple to your software; the notary service also publishes that ticket online where Gatekeeper can find it.
The "OCSP" part of the hostname refers to Online Certificate Status Protocol stapling, or just "certificate stapling." Apple uses certificate stapling to help streamline the process of having millions of Apple devices checking the validity of millions and millions of certificates every day.
When an Apple device can't connect to the network but you want to launch an app anyway, the notarization validation is supposed to "soft fail"—that is, your Apple device is supposed to recognize you're not online and allow the app to launch anyway. However, due to the nature of whatever happened today, calls to the server appeared to simply hang instead of soft-failing. This is possibly because everyone's device could still do a DNS lookup on ocsp.apple.com without any problems, leading the devices to believe that if they could do a DNS lookup, they should be able to connect to the OCSP service. So they tried—and timed out.
The issues seemed to begin close to the time when Apple began rolling out the new version of macOS, Big Sur—but it affected users of other versions of macOS, like Catalina and Mojave. Other Apple services faced slowdowns, outages, and odd behavior, too, including Apple Pay, Messages, and even Apple TV devices.
It didn't take long for some Mac users to note that trustd—a macOS process responsible for checking with Apple's servers to confirm that an app is notarized—was attempting to contact a host named ocsp.apple.com but failing repeatedly. This resulted in systemwide slowdowns as apps attempted to launch, among other things.
The affected hostname (which is really just a pointer to a whole bunch of servers on Apple's CDN) is responsible for validating all manner of Apple-related cryptographic certificates—including the certificates utilized by app notarization. First introduced in Mojave and made mandatory in Catalina, notarization is an automated process Apple performs on developer-signed software:
The Apple notary service is an automated system that scans your software for malicious content, checks for code-signing issues, and returns the results to you quickly. If there are no issues, the notary service generates a ticket for you to staple to your software; the notary service also publishes that ticket online where Gatekeeper can find it.
The "OCSP" part of the hostname refers to Online Certificate Status Protocol stapling, or just "certificate stapling." Apple uses certificate stapling to help streamline the process of having millions of Apple devices checking the validity of millions and millions of certificates every day.
When an Apple device can't connect to the network but you want to launch an app anyway, the notarization validation is supposed to "soft fail"—that is, your Apple device is supposed to recognize you're not online and allow the app to launch anyway. However, due to the nature of whatever happened today, calls to the server appeared to simply hang instead of soft-failing. This is possibly because everyone's device could still do a DNS lookup on ocsp.apple.com without any problems, leading the devices to believe that if they could do a DNS lookup, they should be able to connect to the OCSP service. So they tried—and timed out.
It didn't work...Try this link:
macOS Sequoia
macOS Sequoia brings effortless window tiling, web browsing with fewer distractions, new iPhone Mirroring, and support for Apple Intelligence.www.apple.com
Lou