Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
Did you sneeze all over the screen? That is a gross looking screen! Disgusting!
Better to light a candle...

Easiest way to fix this is, on Amazon, buy
(a) lens cleaner or something similar
(b) a microfiber cloth (sure you can use tissues, but there is a reason your glasses case includes a microfiber cloth)

then go wild squirting lens cleaner and rubbing with your cloth
 
  • Like
Reactions: Captain Trips
My 2019 MBP16 was still getting KPs on wake from deep sleep, unplugged, as of the time I traded it in to Apple.
But it could have been a similar situation where it was resolved in 10.15.5 and came back in 11.0.
I pretty much used an eGPU 100% of the time (other than checking after every update if the issue still occurred) as a result. Once 10.15.5 was out, I never hooked up my eGPU again! I repurposed that GPU so now I can't use it for Big Sur :(
 
if you have another Mac, I recommend making a bootable USB installer. Nuke the entire volume and start fresh.
I ended up using another Mac but with the DFU mode + Apple Configurator 2 method. The restoration process did a certain "nuke" together with feeding the M1 Air a new install. This time the install seems 100% fresh and I could proceed to setup the Air like normal.

Previously when trying to wipe and install via recovery mode, I made certain in Disk Utility I was "nuking" the whole boot volume SSD container before installing. I don't know how the Apple Silicon Macs handle the recovery partition, but it seems at least the user account names are pertained and thus ended up conflicting in the create admin account step.

So yes, perhaps doing a USB bootable install would have solved the issue, but I am past the point to verify now. Thanks for the suggestion either way.
 
  • Like
Reactions: Captain Trips
Minor bug introduced: I have an icon on the menu bar to quickly connect or disconnect a VPN. After connecting, the option to disconnect now doesn’t show. Instead it says something like VPN not configured. The disconnect option does show up in network settings.
 
I had no issues with unlocking my Mac with my Apple Watch before the 11.1 update. Now it won't work lol and this was one of the issues it was supposed to fix. I tried unchecking the box and re-checking the box. No avail. Not sure if it is macOS or watchOS.
You probably already tried this, but if not... Shutdown Mac, phone and watch. Boot phone, boot watch and wait for it to connect to phone, boot Mac and try again. If that doesn't work, try signing out of iCloud on Mac and then sign back in.
 
  • Like
Reactions: Captain Trips
The only thing I noticed between this update and the initial release a month ago, it is slightly slower, not by much. Is anybody noticed any difference performance-wise? Apple needs to trim the fat off their OS. Yes I do have a fusion drive, I only got this back 27" iMac back in July, bumped it up from 32 GB to 64 GB. I will change it when I see this drive shows signs of failing and will get a SSD.

Definitely upgrade to an SSD when it makes sense for you to do and if you feel comfortable with the upgrade.

I have upgraded 3 Intel Macs over the last year and the increase in performance was noticeable:
  • 2009 MacBook (white case). Also upgrade from 2 GB to 6 GB memory.
  • 2010 MacBook Pro 17". Only upgraded SSD (already maxed out o memory)
  • 2014 Mac mini. Only upgraded SSD since memory for this model is not user upgradable (it has 4 GB)
 
Minor bug introduced: I have an icon on the menu bar to quickly connect or disconnect a VPN. After connecting, the option to disconnect now doesn’t show. Instead it says something like VPN not configured. The disconnect option does show up in network settings.

Have you tried recreating the icon? I know, you shouldn't have to do that, but it might be worth trying (if you haven't tried this already).
 
I had to download from the App Store to get the update on my 2017 iMac. My late-2013 MBP downloaded and installed it from System Preferences.
 
How about Spatial audio for the AirPods PRO?
Yes, I posted a question here, because it seems odd to me, too:

 
Question: This version number is a departure from history. Aren't tenth decimal places usually for the yearly revisions?

10.1-10.15 etc then the hundredth spot for patches? Is Apple going to move to yearly number releases now? 11, 12 13 etc?
Yup!
 

I ended up having to abort the install process. My MacBook Pro would no longer fully boot. It would get stuck at a solid gray screen. Reinstalling from the recovery partition produced the same result.

At this point I had the presence of mind to make a SuperDuper clone of my internal 2 TB drive (luckily having a 2 TB spinning disk mechanism at hand). About 17 h later, there were problems with the system volume, but I felt reassured that the data volume had been duplicated successfully.

From a call to AppleCare I concluded that a complete wipe of my computer’s internal drive was the only viable approach. I subsequently installed Big Sur from a thumb drive installer I had just made. Next was to restore the previously installed applications and user home folders using Migration Assitant. Migration Assistant did not recognize the backup as a valid source, because of the incorrectly copied system volume. I then decided to try to install a new copy of Big Sur on the backup drive, which took forever, especially the “less than one minute remaining” portion. My patience bore fruit, as with the newly installed OS on the backup drive, which still booted to gray screen, the drive became a valid source for Migration Assistant. Thank God!

Migration Assistant then still took another 15 h to copy everything back. I am now writing this on my happily restored MacBook Pro. I had been out of commission for over 40 h. I thought, I’d document this, in case it helps someone in a similar situation finding his way to this post somehow.
 
Last edited:
  • Like
Reactions: Shawzborne
Tried the update

Seemed to install ok, came back to life but gave me a message about needing to rebuild system extensions so reboot required
  • Tried this
  • Screen went black
  • One or more of the external non-SSD disks was hammering away for a while
  • They now seem to have gone to sleep
  • Still have black screen 10 minutes later
Anyone else seen this? If so does it eventually come back to life?
[Edit: This is on an M1 Mini]
[Edit 2 - posting this brought it back to life...😀]
 
Last edited:
My Mac is finally fast (i9 MBP 16). Whatever they fixed, it's fixed massive lag I had. I had actually gotten used to it so feels like a new computer now.
 
Tried the update

Seemed to install ok, came back to life but gave me a message about needing to rebuild system extensions so reboot required
  • Tried this
  • Screen went black
  • One or more of the external non-SSD disks was hammering away for a while
  • They now seem to have gone to sleep
  • Still have black screen 10 minutes later
Anyone else seen this? If so does it eventually come back to life?
[Edit: This is on an M1 Mini]
[Edit 2 - posting this brought it back to life...😀]

I was tired today, so I just let it do its thing.

Things that happened:
- Progress bar, stuck at 10%
- Screen black
- Progress bar again, stuck
- Screen black
- Restart, black screen
- Crazy graphics glitch, black screen
- Progress bar (not moving)
- Computer gets hot, fans get noisy
- Not moving progress bar
- Progress bar jumps near end
- Reboot and it works after about 20 minutes.

Smooth? Not really. But it did work.
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.