Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
You're right. I have a Windows 10 gaming PC. Nothing exotic. Bog standard Haswell CPU, Z87 chipset. I have nvidia drivers, Steam, and Firefox installed. Nothing else. On two occasions Windows 10 updates have destroyed the installation so badly I had to reinstall.

Very true. Update 2009 completely trashed my gaming rig. Had to reinstall from backup. In all honesty however, this was the first Win 10 Professional that ever wiped my data and prevented my login.

I‘m still running 10.14 on my 2017 iMac and have no intention of going near Catalina or Big Sur until I have no choice from a security standpoint.

Apple rushed out Big Sur to tie up with the M1 Macs. This “rushing” is becoming more of an issue every year. 😟
 
Last edited:
  • Like
Reactions: Stridr69 and IG88
c) Stop forcing users who rely on software like XCode to update just to get the latest version.
Yep, the only reason I upgraded. Have to have macOS 11 to development for software that will be released next year. Cannot emulate it on prior releases. The only problem I have right now is Time Machine seems to be unreliable.
 
Good to know. Will hold off on my mid 2014 mbp. As to why I haven't upgraded my Mac... no need to. It runs without issues, has no touchbar has USB A ports, has magsafe, sd card reader. Amazing machine.
 
That's why you shouldn't update on day one.

This has been in beta for a really long time. They should have this solved a long time ago.
A major issue like this is a developer-release or beta release only kind of issue.
This is completely pathetic. Considering the iOS 13 and up mess they created.
The sticky keyboard, the usb-c only, the artificial keyboard sounds you can't turn down and on and on...
 
Big Sur made this 2017 MBP almost unusable due to pre-installed Cylance Protect software. There were Kernel panics and reboots every few minutes before I was able to uninstall Cylance CyOptics. This software caused overheating in Catalina already but no Kernel panics. It's working fine now.
 
  • Like
  • Wow
Reactions: tsa1 and JosephAW
There were comments in the beta release notes stating that the first upgrade from a previous OS version could take a very long time. Not only do us beta testers get quick access to those release notes and are expected to read them, but we're also prepared for betas to be potentially disastrous.

For the public release, which is what this thread is about, there needed to be a prominent warning that the upgrade could well take many hours. It seems that many people, reasonably assuming that an upgrade appearing to hang for an hour or two had frozen, rebooted their machines and then "bricked" them. Having an upgrade, or any process, sit for minutes let alone hours without any indication that it's working, is stupid.

In the old days we'd look at our PC cases for the hard disk light to flicker. And even if there was no light, I could put my hand on it and feel it reading/writing. Staring at a black screem with a cartoon pic of an apple and a line which doesn't move, with no warning saying it'll take hours, and with no indication that something is happening, the natural reaction is to power off/on.

The upgrade should be written in a way that either the recovery partition works, or the main partition works, if not both. I'm no OS developer (can you tell?), but that sounds fundamental to me. Sure, we often get warnings stating "do not power off during the firmware upgrade" for stuff like TVs and AVRs etc, but those upgrades take minutes and a reset back to factory defaults pretty much always gets the device working again whatever state it's left in.

Many people upgrade their apps and the OS, whether laptop or phone, as soon as a red badge tells them to. So it's not unexpected that as soon as Apple pushes out an upgrade notification that people pretty much immediately click on it.

I feel sorry for those who have bricked their machines due to what, in my opinion, is Apple's mistake.
 
It seems to running quite well for me. I a few apps that are being quirky, but they are specialized apps that most people do not use.
 
If they are truly bricked and Apple can’t fix them you think Apple will replace them with a 2020 model? :rolleyes:
 
I‘ll stay on Mojave until I am forced to upgrade after my fingernails have been ripped off.
I will keep one older laptop with Mojave to use Adobe Photoshop CS6 as long as possible. Unfortunately, the most recent security update for Mojave broke Google Drive File Stream, which I use all the time. I had to reinstall an older version of Mojave using Cmd-R to get File Stream to work again, quite annoying.
 
here's Obdev's response (little snitch dev company) regarding these privacy issues. They phrased it rather nicely. What it basically means, apple is whitelisting all their telemetry communication making it so that no 3rd party app or user can prevent let alone detect it. Network firewall rules must now prevent your Macs from telling Apple and others what Apps you run and when and where. Bypassing VPNs.... really... I'm losing it!
Little Snitch ought to continue maintaining and offering their kernel extension based approach in parallel to their new one, for users who are concerned about this problem and (!) who are willing/able to disable System Integrity Protection.
 
It's almost ruined my 13" 2015, which is almost top spec, 16 GB ram and 3.1 GHz i7. Even Safari is ridiculously laggy. Hoping further updates will resolve this, otherwise it's a new M1 Air and I'm going broke..
 
It's almost ruined my 13" 2015, which is almost top spec, 16 GB ram and 3.1 GHz i7. Even Safari is ridiculously laggy. Hoping further updates will resolve this, otherwise it's a new M1 Air and I'm going broke..
You could wipe your machine and make certain only 64bit apps are being installed. I doubt that you'll need to buy a new Mac.
 
  • Like
Reactions: Zeus65
This has to be the most disappointing OS in the last ten years I owned Macs...
Beta was full of installation problems: I could not run Beta 1-5, and then for no reason beta 6 worked; then RC1 initiated a reboot loop and RC2 did the same... Then on the release day -- what a joke for many of us... And NOW this???
 
  • Like
Reactions: chrickers
Big Sur is sure looking like a huge headache more and more by the day. First the Apple servers crashed on launch day, and now this debacle... I usually am the first the jump ship to the latest OS, but gonna wait a bit for this one
And the Safari mess. Apple is absolutely sucking lately. Not software developers - just hackers hacking away and rolling out junk software.
 
There were comments in the beta release notes stating that the first upgrade from a previous OS version could take a very long time. Not only do us beta testers get quick access to those release notes and are expected to read them, but we're also prepared for betas to be potentially disastrous.

For the public release, which is what this thread is about, there needed to be a prominent warning that the upgrade could well take many hours.
Not only that, but the UI is just bad.

It went through multiple different screens, including a weird one with a menu bar showing "Language Choice"(I think?) and a progress bar that seemed stuck at about 3% for ~10 minutes, only to disappear entirely.

It rebooted multiple times, it sometimes showed estimates (none of which were cumulative) and sometimes didn't, and at no point did it go into any detail if everything is alright. You're basically just left there panicking "I hope it's not bricked".

So yes, like you said, I can imagine some people concluding "I guess it's messed up; let's try a hard reboot".
 
  • Like
Reactions: adrianlondon
Dr. Cook was nice enough to abandon 32-bit apps with the introduction of Catalina. Since I have a number of 32-bit apps that were never updated to 64-bit (for a variety of reasons), I'm stuck in the time warp of Mojave forever. I weep each time I consider the hundreds of emojis I'll never be able to use on my MacBook Pros. Oh, the humanity! Uh, and thanks, Tim!
 
  • Like
  • Haha
Reactions: Stridr69 and R2FX
This exact scenario happened when I updated my 2020 iMac (stuck on black screen). Apple support had me reinstall Catalina, and then I upgraded to Big Sur with no issue. Machine is running great now.

A friend with a 2017 iMac got completely bricked with the update, and it had to be sent in for service.
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.