X

Send us a Topic or Tip

Have a suggestion for the blog? Perhaps a topic you'd like us to write about? If so, we'd love to hear from you! Fancy yourself a writer and have a tech tip, handy computer trick, or "how to" to share? Let us know what you'd like to contribute!

Thanks for reaching out!

macOS Big Sur Reportedly Causing Problems for Certain MacBook Pros

2013 MacBook Pro on Big Sur wallpaper with black screen

I usually wait a few months before upgrading to the latest and greatest macOS, or at the very least, the first major revision (macOS 11.1 in this case). But this time around, I decided to bite the bullet and load up Big Sur on my MacBook Pro.

The result?

So far, so good. But that hasn’t been the case for many. According to MacRumors, the installation of macOS Big Sur is causing problems and bricking their machines. No chime, no keyboard lights, no fan – nothing. During the installation process, the impacted computers freeze on a black screen, and none of the usual key commands for NVRAM reset or booting into safe mode appear to be working.

There is a support thread on apple.com indicating that the Macs being affected are the late 2013 and mid-2014 MacBook Pros, and some have had some success in unplugging the I/O board before attempting to re-install macOS 11. That doesn’t sound like fun, and hopefully something Apple will be addressing soon.

The machine on which I successfully installed the new OS? A late 2013 MacBook Pro. I guess I dodged a bullet when I bit the bullet. Even still, I am not going to play Russian Roulette and will wait to update my iMac.

How wide-spread this issue is right now is unknown, but if you are experiencing Big Sur installation problems, let us know in the comment section below.


OWC Mark C
the authorOWC Mark C
Content Marketing Manager
A creative by nature, Mark is a writer, programmer, web developer, musician, culinary craftsman, and interpersonal artisan. He loves the outdoors because greenspace is to the soul as whitespace is to the written word. He does not like Diophantine geometry or mosquitos. Most everything else is okay. Oh yeah, he is also the managing editor of the Rocket Yard blog.
Be Sociable, Share This Post!

Leave a Reply

Comment

Name

20 Comments

  • Several problems…updated my Mac Pro mid-2010 this past month to the 2019 Mac Pro, which had its own problems had to take it to the store for them to fix the software/firmware so that I could install my Time Machine files properly and still had problems afterwards. It was working well and then came along Big Sur…the plus so far is that I was able to combine my 2 different Apple ID’s into one, which I have been wanting to do for the past 25 years and enlarged the desktop icons and print so that I could read them with our ruining my eyesight…YEAH! The minuscule problems that I have noticed so far is that the cursor jumps and skips around especially when I’m using the magic pad. I’ve noticed the email problems as well plus Websites in Safari are more sensitive to VPN’s to the point I almost have to disconnect my VPN if I want any particular page to open up. But the plus side to the emails, I like the fact that you can “block” email addresses, however, I’ve noticed that even though I have blocked certain emails they continue to be posted in my inbox continuously only with a small notice that “This email came from a blocked address.”…really?

  • My Wife (iMac, Retina 4K, 2019) and I (Mini 6-core i5, 2018) upgraded to Big Sur despite my long-held belief that Apple cannot handle both a big hardware transition and a big software transition at the same time – my cynical view sustained again. Both of us are having significant problems with Mail application database coherence (2 and 3 mail accounts, respectively) with messages disappearing from the inbox and junk mail box at random intervals. Reboots may restore the db sometimes and re-building the db sometimes helps, too.

    By-the-way, the complete silence Apple has always had at the user interface regarding progress in the re-build and completion of re-building the email db is both annoying and may be damaging because the user is tempted to do things such as delete mail or move items while the re-build is in-progress – this is really bad user interface design, IMO – it mistakes lack of information for cleanliness of design.

    In another area, we have noticed in a couple of instances that existing iMessage threads have opened windows without an input area for further use of the thread. A work-around is to attempt to open a new thread with the same addressees and you’ll get the old thread window with an input area.

    • I noticed the iMessage issue myself, and interestingly it also started happening on my Catalina iMac once I installed Big Sur on my MacBook Pro. Possibly a sync-issue, or the iMessage service itself?

  • I have a late 2013 and have had problems. Something about external drives connected via USB seems to cause a problem. It started when I tried to run Time Machine from my external drive and it wouldn’t connect. Then when I rebooted, the keyboard and mousepad wouldn’t respond. Only when I pulled my external memory and reboot could I get it to work. Not good, Apple.

  • I booted up my mid-2014 MacBook Pro off my OWC back-up drive (running macOS 10.15.7), downloaded the Big Sur installer on it, and then attempted to run the installer but the screen froze almost immediately. I couldn’t move the mouse or use keyboard commands. I forced a restart and removed the installer and will await macOS 11.1.

  • Any news on when there will be a fix for upgrading to Big Sur on a Mac Pro (late 2013) running your SSD 1TB? I keep getting an error message stating that the third party storage storage is not compatible.

      • Here is the exact message when trying to install Big Sur:
        “Mac OS cannot be installed because the 3rd party storage on your Mac is not compatible. Please contact the supplier directly for assistance.”
        I did contact support and they said there is a solution being developed?
        Thanks for your help,
        Steve

  • Have a new 2019 16” MacBook Pro. Upon installing Big Sur, all external drive became “Read Only”! I finally found a work around. To write to external discs or edit files on these discs, I have to open Disk Utilities, run first aid on the data portion of the drive, then open get info and check ignore ownership on this volume. Have to do this each time. All of this may be due to the fact that my external drives are bootable.

  • I tried twice on my 2019 iMac. When I came back to check progress the Mac would be off. Trying to restart wouldn’t work. It would turn on for 3 seconds and then shut down. Fortunately command R worked so I could reinstall from a backup which is where I left it till a new version comes out.

  • When this issue occurred with Catalina, the issue with older machines (that don’t have the T2 chip) was that the OS update tried to update the SPI Rom chip which is where the EFI (the Apple equivalent of BIOS) is stored. The purpose of trying to update/rewrite this chip is to prevent the user from downgrading to earlier versions of MacOS.

    It’s not confirmed that this is the same problem with Big Sur, but the symptoms appear to be identical.

  • Sounds a lot like more of the same after Catalina upgrade whole gambit of Macs went wonky from brand new Macs to older 2012 Mac mini from MacBooks Pro Air to iMacs .

    Some sort of firmware glitch involving inactivity causing random shutdowns .

    No one on this mega thread has reported any hardware issues & the Mac systems to diverse for it to be combination of components .

    iMac keeps crashing after Catalina upgrade
    https://discussions.apple.com/thread/250717203

    My 15″MacBookPro14,3 been crashing multiple times a day since Catalina upgrade & now still crashing multiple times a day with Big Sur as well .

    Every OS update I keep thinking maybe this time … Apple will fix the shutdown issue like back in the old days

    Using my MacBook alone crashing multiple times daily .. Walk away from MacBook 50/50 chance its crashed .

    I don’t understand how a completely OS firmware bug that effects this many Macs goes unaddressed by Apple & unreported` by any of the Apple Mediasphere for a year .

    • My brand new 27” 5k iMac 2020 at work has been shutting down constantly. One day it shut down about 10 times throughout the day. It came with Catalina installed. Not a good look Apple.

      • If that’s happening right out of the box, could have a hardware issue of some kind. Catalina isn’t my favorite OS, but shutdowns – do you get a message that it wasn’t properly shutdown after each reboot? Really sounds like a hardware issue with the noted iMac.

        • I was I’m thinking the same thing. It gives some type of CPU error most of the time. I’ll have to look up the specific crash log. I did a Carbon Copy Cloner of my old machine and migrated it to the new one. We ordered it with a basic 8gb of RAM. It would give me out of memory errors and then when shut down on me, we already had 64gb upgrade kit (4×16) on order from OWC, so I want too worried about it, even though I thought it was really weird. Been using Macs for nearly 30 years and I’ve never seen an issue like this. After installing the OWC RAM it never gives any out of memory error and goes straight to shutting down. I was going to test a few things before contacting Apple because I know they are just going to tell me to do those first anyway. I’m already talking to another guy on the Apple support forums that is having the same issue. Apple told him to wipe the drive and install everything from scratch instead of migrating. I may test the ram by putting one stick in at a time, but I really don’t think that’s the issue either.

        • Thanks for the response. I typed a reply yesterday on my phone, but I’m not sure if it ever went through. It didn’t end up being posted.

          I have got a few different error messages. One is a CATERR, which from looking online seems to be a CPU error. I also got a few Kernel Panics mixed in. Which I’ve maybe only had two or three of those in the last 10 years. We ordered the machine with the base 8gb of RAM from Apple. It would run out of memory after a few hours of running Adobe apps and a few 3d apps (Modo, C4d). It would give me an out of memory error and then the force quit window would pop up telling me to close some apps. Then shortly after that, the whole machine would shut off. I thought it was just a memory issue, even though I thought it was still pretty odd for that to happen. I knew we had some new OWC RAM on the way, so I waited for that to arrive. Now I don’t get any out of memory errors, but it goes straight to shutting down.

          Another guy on the Apple forums is having similar issues and when he talked to Apple, they told him to reinstall the OS and not use migration and clean install everything. He did this and it still didn’t help (which I didn’t think it would). I don’t think it’s the OWC RAM, but I will test each stick individually just to be able to tell Apple that isn’t the problem when I contact them.

        • “My new iMac had this problem from the start so I exchanged it for another identical one after a couple of weeks (at first I put it down to automatic software updates but it just kept happening several times every day) – so far I haven’t had the same issue except for one random shut down overnight, I can’t explain why as in theory there shouldn’t be any difference between two identical iMacs running exactly the same OS. ”

          https://discussions.apple.com/thread/250717203?page=90