#Macos big sur patcher install#
#Macos big sur patcher update#
#Macos big sur patcher pro#

I've now blocked them outside the machine. However, these Apple servers are constantly connected as indicated by my network firewall. I had updated to little snitch 5 and it no longer can block any OS services from calling home. HUGE privacy concerns are popping up!Īpparently trustd and other Apple services and apps will now BYPASS firewall tools like little snitch and even VPNs. Safari often seems frozen and doesn't take clicks or other UI input anymore, having to refresh a website. The OS sometimes (!) is not as responsive as Catalina was. It also seems to take an age to display the Apple logo when it boots, and has a very strange boot sequence that involves showing the Big Sur background with a progress bar, then reverting back to a black screen with an Apple logo, followed by a really weird graphical distortion with tearing all across the screen and then finally the loaded desktop. The booting sequence looked weird and restarting the machine doesn't work and causes weird behaviour just like it was described here: I erased the SSD and did a clean install.

Apple deserves every ounce of heat they'll get over this and then some. Unless it can be shown that it is a small number of machines and or related to a factor completely out of Apple's control (I really can't imagine what that would be), this level of **** up is new territory for Apple and deserves to be recognized as such.ĭon't normalize this. This is completely unacceptable, particularly during a pandemic when its not safe (or at the very least far from ideal) for many people to to go out and people are relying on these machines for their livelihood more than ever. BRICKING machines such that only Apple can restore them has, as far as I can remember, never happened before.

#Macos big sur patcher update#

That's why you shouldn't update on day one.Īll of you, and everyone else in this thread needs to stop pretending this is normal.

#Macos big sur patcher install#

Furthermore while I'm not saying bricking should happen I think it's a stretch trying to install the latest OS on near 7 and 8 year old computers and expect to have no issues. Sometimes I get the feeling that these issues are made up in order to crap on Apple when they release new products. Interesting how Apple put out the Public Beta months ago and this is discovered just now? You mean nobody with a 2013/2014 MBP ever had a bricking issue all the time during the public beta? Hmmm. Never update straight away as there are always bugs.

#Macos big sur patcher pro#

Until it is clear what may be causing the issue and Apple releases a fix, late 2013 and mid 2014 13-inch MacBook Pro may wish to hold off on installing macOS Big Sur. Another on an Apple Support thread said that the issue has been escalated to Apple's engineering team, so Apple should now be aware of the problem.

One commenter on Reddit said that they were told by Apple support to book their MacBook Pro in for a repair. It is also of note that these are the oldest models supported by macOS Big Sur. It appears that the overwhelming number of users experiencing problems are owners of the late 2013 and mid 2014 13-inch MacBook Pro, but it is unclear exactly how many users of these models have been affected. Key reset combinations, including NVRAM, SMC, safe mode, and internet recovery, are all reportedly inaccessible after attempting to install the update, leaving no way to bypass the static black screen. Users are reporting that during the course of updating to macOS Big Sur, their machines are stuck displaying a black screen. A MacRumors forum thread contains a significant number of users reporting the issue, and similar problems are being reported across Reddit and the Apple Support Communities, suggesting the problem is widespread. A large number of late 2013 and mid 2014 13-inch MacBook Pro owners are reporting that the macOS Big Sur update is bricking their machines.