2020-006 Security Update for Mojave & High Sierra + Safari 14.0.1
Security Updates 2020-006 for macOS Mojave 10.14 (18G6042), High Sierra 10.13 (17G14042) & Safari 14.0.1 are now Available.
With the release of macOS Big Sur, Apple also released Security Updates for both macOS Mojave and High Sierra. Catalina was issued a 10.15.7 Supplemental Update to address the same security issues in 2020-006.
NOTE: Apologies for the tardiness of this article, Big Sur and Apple Silicon really took my attention away. I didn’t forget about everyone who asked me when my Security Update article would come out. I will always test the update out first so you don’t have to deal with issues.
You can read more about the 10.15.7 Supplemental update below.
Big Sur 11.0.1 (20B50) Released to block install for 2013-2014 13-inch MacBook Pro Users.
Big Sur 11.0.1 (20B50) was released to block 2013 & 2014 13″ MBPro’s from installing the OS. This move looks to be related to the Big Sur install problems with these models.
UPDATE 12/14/20 – Apple has added the Mac-189A3D4F975D5FFC BoardID back to the newly released macOS Big Sur 11.1 Full installer! It looks like Apple has found and fixed the issue with the installer that was causing problems! This means that you can now download, install and reinstall Big Sur 11.1 on your 2013-14 13″ MacBook Pro again.
UPDATE 11/25/20 – If you attempt to install Big Sur on your 13″ 2013-2014 MBPro, you might get this error.
Installation of macOS could not continue. installation requires downloading important content. That content can’t be downloaded at this time. Try again later.
If you are wondering about the Big Sur Installer issue for the 2013 & 2014 13″ MacBook Pro users, I wrote about the situation earlier this week.
To review, if you have a 2013 or 2014 13″ MacBook Pro and attempted to install macOS Big Sur, it was possible that the installer could brick your Mac.
When I say “brick” I mean that it boots to a black screen and is 100% non responsive. You can’t boot to recovery, USB installers, reset the pram or SMC.
The only option for users is to bring it in for repair. The reports say that Apple is saying that the logic board needs to be replaced at a price over 500$. Even worse some are being told it’s a vintage product and they can’t parts. This is FALSE, Apple will keep stock of parts up to 7 years.
Vintage products are those that have not been sold for more than 5 and less than 7 years ago. Mac, iPhone, iPad, iPod, and Apple TV vintage products continue to receive hardware service from Apple service providers, including Apple Retail Stores, subject to availability of inventory, or as required by law.Apple.com – https://support.apple.com/en-us/HT201624
https://support.apple.com/en-us/HT201624
Hopefully Apple will cover the cost of the repair for free.
The solution for now? Release a new macOS Big Sur Installer that removes both models from the Big Sur compatibility list.
The link below shows the list of Big Sur compatible Macs
If you can’t install macOS Big Sur on certain 13-inch MacBook Pro computers from 2013 and 2014. Follow these steps if you can’t install macOS Big Sur on a MacBook Pro (Retina, 13-inch, Late 2013) or MacBook Pro (Retina, 13-inch, Mid 2014). When you install macOS Big Sur on these Mac models, the installer might say that the update cannot be installed on this computer, or your Mac might start up to a blank screen or circle with a line through it.
Apple.com
The most important part of this article is this line
“or your Mac might start up to a blank screen“
This is exactly what will happen to some users if they install macOS Big Sur on their 2013 or 2014 13″ MacBook Pro.
Let’s look at the other parts of the note.
“the installer might say that the update cannot be installed on this computer“
This is because both models have been removed from the new Big Sur installer compatibility list.
“or your Mac might start up to a blank screen or circle with a line through it“
This might happen if you make a new USB installer of Big Sur 11.0.1 (20B50) and attempt to boot to it.
Removed from the Big Sur Compatible List?
The macOS installer has a file inside called the distribution file. For this release it’s called 001-83532.English.dist.
Compatible Macs for install are listed in this file as BoardID for older devices and DeviceIDs for newer models. The boardID we are looking for is
Mac-189A3D4F975D5FFC
This BoardID is for the MacBookPro11,1 or the 2013 & 2014 13″ MacBook Pro.
I keep a database of all Mac BoardID and DevicesIDs here
You can see the list of supportedBoardIDs – Mac-189A3D4F975D5FFC was removed from 11.0.1 (20B50)
This means that (for now anyway) you will not be able to install macOS Big Sur on your 2013 or 2014 13″ MacBook Pro.
Will Apple fix this issue and add them back later?
Unknown at this time. It’s possible that Apple will fix issue the Big Sur installer is causing to these models. They could then add the models back to the compatibility list later.
macOS Big Sur running list of install / upgrade problems.
This article is a running list of all known macOS Big Sur install / upgrade issues.
macOS Big Sur launched on Thursday November 12th, 2020. As with any launch of a product or software there will be issues. In the case of Big Sur, the problems started almost immediately. Users started to report download issues when trying to get Big Sur.
As the the week went by, more serious issues started showing up. If you are seeing a one of these issues, feel free leave a comment below.
Mr. Macintosh video that goes over some of the known Big Sur Install issues.
macOS Big Sur Install Issues Table of Contents
UPDATED 2/14/21 – List of macOS Big Sur Installation Issues.
1. Big Sur Full Installer.app Download Problems – “Installation Failed Error Occurred while installing the selected updates.”
2. Big Sur progress gets stuck mid installation – Black Screen with Apple Logo stuck or stopped progress bar
3. Big Sur Install failing and bricking some older 13″ MBPro’s – Installation fails and the Mac has a black screen – Will not respond to any startup commands.
4. Big Sur stuck in endless boot loop. – Some users are reporting after a good install the Mac is stuck in an endless boot loop.
5. Slowness after upgrade to Big Sur – Other have reported that their Mac is very slow after upgrading to Big Sur.
6. Reinstalling macOS Big Sur on Apple Silicon –
7. Big Sur Upgrade Error – An error occurred preparing the software update.
8. If you can’t unlock settings in System Preferences Big Sur 11.1
If more trending issues come in, they will be posted here.
1. Big Sur Full Installer.app Download Problems – “Installation Failed Error Occurred while installing the selected updates.”
UPDATE 11/27/20 – I’m still getting a bunch of people reaching out saying that they are still getting the error even after Apple fixed the issue! I have a fix for you via Hyram Hakkenbecker. You can download the full macOS Big Sur installer directly from Apple’s servers via Safari.
2. Big Sur progress gets stuck mid installation – Black Screen with Apple Logo stuck or stopped progress bar
This issue happens halfway through the Big Sup upgrade or install process. The Mac has already rebooted to the installer and is now on the progress bar. The problem is, something has gone wrong on the install and the progress bar gets stuck at a certain percentage and will never move again.
The progress bar looks to gets stuck at around 40% and will never move again. Below is a screen shot from MacRumors forum user plandersen.
Big Sur install Black Screen progress bar stuck.
What should you do if this issue happens to you?
1. First WAIT! Sometimes the install process takes time. If after a few hours pass and the progress bar has not moved go to the next step.
2. At this point, you have no choice but to power down. I know this sounds drastic, but you literally have no other choice. The good news is, this is also the fix. Many users have reported that this fixes the issue for them. After force powering down the Mac will come back up and and will boot right to Big Sur.
Out of all the reports, this one is the most serious. I do not throw around the “Bricking” term much, as it means that the Mac is usually DEAD. In this situation, if this issue happens to your Mac it will be non responsive.
The reports say that the install starts but after the reboot they get a black screen with nothing on it. Even if the user restarts they will still get the black screen. If they attempt to hold down option, Command R, Reset the Pram, SMC… etc nothing works. In this mode the Mac will NOT respond to any startup keyboard commands
Mr. Macintosh video going over the 2013-2014 13″ MacBook Pro Bricking Issue
Mr. Macintosh UPDATE video going over the 2013-2014 13″ MacBook Pro Bricking Issue
Affected Macs known so far.
13″ MacBook Pro from 2013-2014.
What should you do if this issue happens to you?
In my option, this issue is 100% on Apple to fix for users. If an update or upgrade causes a Mac to become unusable they need to fix it at no cost to the user.
Wait until a possible new fix comes in.
Wait for a Service Program that will cover this issue.
Bring your Mac into service. Apple so far is saying that you will need to replace the logic board. If they say it will cost you to fix the issue, ask for escalation. This issue is not your fault. A macOS update or upgrade should not BRICK your Mac!
(WARNING this is a last ditch attempt. Try at your own risk!) Try disconnecting the I/O board.
Reddit user maknell wrote an great write up covering the issue.
Other users have reported that after installing Big Sur, their Mac will be in an endless boot loop.
What should you do if this issue happens to you?
1. Try to boot into safe mode. Does the the Mac boot correctly? If so something installed on your mac is causing this issue. Maybe it’s an 3rd party application that has installed a Kernel Extension or a LaunchDaemon that is causing the issue.
2. Reinstall macOS
5. Slowness after upgrade to Big Sur – Other have reported that their Mac is very slow after upgrading to Big Sur.
I am starting to see a decent amount people say that after updating to macOS Big Sur from macOS Mojave or Catalina has caused a bunch of weird issues including slowness. The slowness is all over the system, including opening apps, Apple Menu and system preferences just taking a long time to load.
What should you do if this issue happens to you?
Wait! It’s possible that spotlight search is currently indexing and can take some time.
If after a while the system is still slow, open up activity monitor and click on the CPU or Memory tabs. Are any apps or processes taking very large amounts of memory or CPU?
If so kill the process then check system performance.
Still having issues after checking everything? Backup your data and perform a fresh install. I have macOS Big Sur running on a bunch of Macs even all the way back to the 2014 model. They all run very well. Almost all of them had a fresh install. This might be the way to go.
6. Reinstall macOS Big Sur on Apple Silicon Mac = An error occurred preparing the update. failed to personalize the software update. Please try again.
If you try to reinstall macOS on your new M1 Apple Silicon Mac you will get an error. The issue requires a 2nd Mac to fix!
7. Big Sur Upgrade Error – An error occurred preparing the software update.
If you attempted to upgrade to macOS Big Sur and you did not have enough free space on your hard drive the upgrade will fail! This will also leave you in an upgrade install loop. Even worse, if you have Filevault encryption enabled you will be locked out of your data!
Mr. Macintosh Deep Dive full report of this issue + full walkthrough and fixes for multiple situations!
8. If you can’t unlock settings in System Preferences Big Sur 11.1
If you can’t unlock settings in System Preferences If System Preferences doesn’t accept a valid administrator password when you click the lock to make changes, try these solutions.
macOS Big Sur 11.0.1 – Installation failed An error occurred while installing the selected updates.
macOS Big Sur was launched at 12:00PM CST. A few hours later, users started to report download problems.
UPDATE 02/20/21 – I’m still getting a bunch of people reaching out saying that they are still getting the error even after Apple fixed the issue! You can download the full macOS Big Sur installer directly from Apple’s servers via Safari.
What this will do is download the entire InstallAssistant.pkg file. Install this package and it will put macOS Big Sur into your /Applications folder!
UPDATE 11/12 7:30PM CST – The download is working in the Software Update pane now. LET THE BIG SUR DOWNLOADING COMMENCE!!!
UPDATE 11/12 7:00PM CST – Some users are reporting that the download is starting to work. installinstallmacos.py is working for me but I’m still getting the error in the Software Update pane.
If you were able to download the full Big Sur installer before this issue happened, then you are one of the only people with a full installer right now! Maybe you can burn it to a Dual Layer DVD and sell it on ebay haha! (will have to be a blu-ray disc as a DL dvd is only 8.5GB and the Big Sur Installer is 12.2GB LOL)
This is the error you will get on Big Sur when trying to download macOS Big Sur.
My videos explaining the issue is below.
Mr. Macintosh video explaining the macOS Big Sur download issue Update #1
Mr. Macintosh video explaining the macOS Big Sur download issue.
Apple Server issues.
Apple did report a server side issue for macOS Software Updates.
That section was marked as resolved though at 3:30 CST. The problem is, the download is still not working.
The issue is with one file
After digging in, the issue is with one file installassistant.pkg
If you use installinstallmacos.py to attempt to download macOS Big Sur 11.0.1 (20B29)
curl: (22) The requested URL returned error: 403 Forbidden
Could not replicate http://swcdn.apple.com/content/downloads/50/49/001-79699-A_93OMDU5KFG/dkjnjkq9eax1n2wpf8rik5agns2z43ikqu/InstallAssistant.pkg: Command '[u'/usr/bin/curl', u'-fL', u'--create-dirs', u'-o', u'./content/downloads/50/49/001-79699-A_93OMDU5KFG/dkjnjkq9eax1n2wpf8rik5agns2z43ikqu/InstallAssistant.pkg', u'--compressed', 'http://swcdn.apple.com/content/downloads/50/49/001-79699-A_93OMDU5KFG/dkjnjkq9eax1n2wpf8rik5agns2z43ikqu/InstallAssistant.pkg']' returned non-zero exit status 22
We do not have access to download InstallAssistant.pkg and get a 403 Forbidden Error.
Once this issue is fixed, I will will let everyone know.
Once access to this file is restored, we should be able to download Big Sur again. I will keep you updated.
macOS Big Sur 11.0.1 RC2 Full Installer.app error = “An Error occurred installing macOS”
When you attempt to install or upgrade on a T2 Mac, you will get the error “The bridgeOS update doesn’t satisfy the given minimum version requirement.”
UPDATE 11/12/20 – This article is for yesterday’s Big Sur BETA install problem. If you are having problems downloading the new Big Sur update or full installer I have a new article on the issue. It’s for the Installation failed an error occurred while installing the selected updates error.
Almost immediately after macOS Big Sur 11.0.1 (20B28) was released, I started to see reports of install issues. This was only happening on T2 Macs that need a BridgeOS update. A BridgeOS update is included and required with almost every combo, delta and full installer upgrade or install. Below is the 11.0.1 RC2 Install error.
The error message that you will get if you try to upgrade a T2 Catalina or Big Sur Mac to 11.0.1 RC2
An error occurred installing macOS. You can try again to complete the installation.
Mr. Macintosh video that goes over the issue.
The problem is the new production Software Update Catalog URL does not have the needed BridgeOS update yet.
The problem comes down to the installer looking to the new production SUS url. Apple just made the production SUS catalog available. The new URL is
The production URL does NOT include the required BridgeOS update needed for the Big Sur RC2 installer to continue.
The BridgeOS error from install.log
This is the error that you will get.
/var/log/install.log
bridgeOS update prepare complete
2020-11-11 01:49:05-06 osinstallersetupd[5967]: bridgeOS update prepare failed: Error Domain=BOSErrorDomain Code=110 "The bridgeOS update doesn't satisfy the given minimum version requirement." UserInfo={bridgeVersion=17.16.16610.0.0,0, minimumVersion=18.16.12561.0.0,0, catalogURL=https://swscan.apple.com/content/catalogs/others/index-11-10.15-10.14-10.13-10.12-10.11-10.10-10.9-mountainlion-lion-snowleopard-leopard.merged-1.sucatalog, NSLocalizedDescription=The bridgeOS update doesn't satisfy the given minimum version requirement.}
2020-11-11 01:49:05-06 osinstallersetupd[5967]: Operation queue failed with error: Error Domain=com.apple.OSInstallerSetup.error Code=602 "An error occurred installing macOS." UserInfo={NSLocalizedRecoverySuggestion=You can try again to complete the installation., NSLocalizedDescription=An error occurred installing macOS., NSUnderlyingError=0x7fde25b85770 {Error Domain=BOSErrorDomain Code=110 "The bridgeOS update doesn't satisfy the given minimum version requirement." UserInfo={bridgeVersion=17.16.16610.0.0,0, minimumVersion=18.16.12561.0.0,0, catalogURL=https://swscan.apple.com/content/catalogs/others/index-11-10.15-10.14-10.13-10.12-10.11-10.10-10.9-mountainlion-lion-snowleopard-leopard.merged-1.sucatalog, NSLocalizedDescription=The bridgeOS update doesn't satisfy the given minimum version requirement.}}}
2020-11-11 01:49:05-06 InstallAssistant[5928]: Stopped operation queue with Error Domain=com.apple.OSInstallerSetup.error Code=602 "An error occurred installing macOS." UserInfo={NSUnderlyingError=0x7fd70cf90da0 {Error Domain=BOSErrorDomain Code=110 "The bridgeOS update doesn't satisfy the given minimum version requirement." UserInfo={bridgeVersion=17.16.16610.0.0,0, minimumVersion=18.16.12561.0.0,0, catalogURL=https://swscan.apple.com/content/catalogs/others/index-11-10.15-10.14-10.13-10.12-10.11-10.10-10.9-mountainlion-lion-snowleopard-leopard.merged-1.sucatalog, NSLocalizedDescription=The bridgeOS update doesn't satisfy the given minimum version requirement.}}, NSLocalizedRecoverySuggestion=You can try again to complete the installation., NSLocalizedDescription=An error occurred installing macOS.}
Notice this line
“The bridgeOS update doesn’t satisfy the given minimum version requirement.” UserInfo={bridgeVersion=17.16.16610.0.0,0, minimumVersion=18.16.12561.0.0,0, catalogURL=https://swscan.apple.com/content/catalogs/others/index-11-10.15-10.14-10.13-10.12-10.11-10.10-10.9-mountainlion-lion-snowleopard-leopard.merged-1.sucatalog“
You can use sudo nvram -p to view all the nvram settings.
NOTE! When you are done with the upgrade, don’t forget to remove the value!
sudo nvram -d IASUCatalogURL
MacAdmins at work!
It’s amazing to see MacAdmins working together to solve an issue. Yesterday afternoon a bunch of Admins including @golby, @eholtam, @owen, @dave.shepp, @macmule, @matt_h and @deets jumped in to help figure this out and pass on the information to others.
Apple has just released the macOS Mojave 10.14.6 “Supplemental Update” which is a fixed version of Safari 14.0
The macOS Mojave 10.14.6 Supplemental Update is Live! It includes a fixed version of Safari 14.0. The update also address the problems of the previous release. Security Update 2020-005 was also re-released.
Apple has just released a Mojave Supplemental Update that address all the problems that the previous Safari 14.0 and 2020-005 Security Updates! This news comes one day after Apple pulled both software updates from the software update catalog.
You can find a full summary of the issue in the link below.
UPDATE 10/08 11:30PM – Safari 14.0.1 Seed 2 was just released today. Mr. Macintosh reader Joe wrote in to let me know that after he installed Seed 2 over Seed 1 all of his problems went away! This will be a perfect fix for anyone who installed Safari 14.0.1 Seed 1 and were still having problems (since the Supplemental Update was not compatible with 14.0.1).
UPDATE 10/03 3:00PM– I’ve added a direct download link to the safari 14.0 package from the software update service in section 16 below. Apple has also added back the Mojave 2020-005 Security Update back to Apple.com downloads. The security update link is also in section 16 below.
UPDATE: 10/02 3:00PM – NOTE: Apple still has an old link to the Supplemental Update from 9/26/19 up on the the Apple downloads site. This is NOT the update you need. Apple has not released a stand alone download for this update yet. The update is only available from software update.
UPDATE: 20/02 10:30AM – I’ve added section 5 to make sure you know that the Supplemental Update will install Safar 14.0. This is important to understand in case you needed to remain on Safari 12 or 13. Some users are asking me what they should so if they installed Safari 14.0.1 Beta. I’m looking into that now.
You can also check out my new update deep dive video below.
Mojave Supplemental Update (Safari 14) Mr. Macintosh Video
Table of Contents
1. Name of the Update?
2. Details of the macOS Mojave Supplemental Update
3. I’ve tested this update and confirmed that it fixes most issues!
5. The Supplemental update will install Safari 14.0!
6. Inside the macOS 10.14.6 Supplemental Update
7. Which update does your Mac need?
8. Did you ONLY install – Safari 14.0?
9. Did you ONLY install – 2020-005 Security Update?
10. Did you install BOTH Safari 14.0 & Security Update 2020-005?
11. Did you not install either of the updates?
12. Not seeing the 2020-005 Security Update?
13. I ran softwareupdate --ignore "Security Update xx" now what?
14. Did you install Safari Beta 14.0.1 ?
15. Did I cover all the situations that you could be in?
16. 10.14.6 Supplemental Update Links
17. Security Content of macOS 10.14.6 Supplemental Update
18. Final Thoughts
19. Thank You
1. Name of the Update?
Apple calls this update “macOS 10.14.6 Supplemental Update” Which is a bit confusing. In this particular case, the naming might make sense. Even though the update only includes a fixed Safari pkg, it also includes fixes that repair previous install OS level issues.
softwareupdate -l shows the name. It’s technically called Safari14.0MojaveAuto-10.14.6
NOTE!!! The update also includes a required restart. (Normal Safari Updates do not require a restart.)
2. Details of the macOS Mojave Supplemental Update
Along with the new Supplemental Safari Update, the Mojave 2020-005 Security update was re-released back into the software update catalog.
5. The Supplemental update will install Safari 14.0!
I need to make this clear, If you do not want Safari 14.0 don’t install the new macOS Supplemental update! I’ve heard from a few users who need to remain on the old version. Only update when you are ready to make the jump to Safari 14.0
6. Inside the macOS 10.14.6 Supplemental Update
So if this is not a normal supplemental update, what is it?
This is what’s inside of the macOS 10.14.6 Supplemental Update (FIxed Safari 14.0)
As you can see, this update only has the fixed version of Safari 14.0 inside! NOTE: this update has a REQUIRED RESTART!
What does a normal supplemental update look like?
This is what’s included in a full Supplemental Update. This is the 10.14.6 Supplemental Update #2
As you can see a normal “Supplemental Update” includes a bunch of stuff. I just wanted to clear up any confusion that you might have. (I was confused when I first saw the update.)
7. Which update does your Mac need?
We have multiple scenarios to work with here. I have used a test Mac to go over the many situations that a user might be in so you are not left wondering what to do!
1. Did you install ONLY install – Safari 14.0?
2. Did you install ONLY install – 2020-005 Security Update?
3. Did you install BOTH Safari 14.0 & Security Update 2020-005?
4. Did you not install either of the updates?
Below is a screenshot of what About This Mac > System Report > Installations will look like.
System Report – This is what it would look like after installing both problematic updates then installing both fixed updates.
8. Did you only install – Safari 14.0?
Let’s say that you installed Safari 14.0 a few days ago but heard the news about all the problems that the 2020-005 security update was causing.
Your Safari Version is = 14.0 (14610.1.28.1.9)
You will see the following in Software update.
This is what you will see if you only installed the old version of Safari 14.0
The following will happen in this scenario.
Fixed version of Safari Supplemental Update + fixes update will be installed
The Re-Released version of Mojave 2020-005 Security Update will install
Reboot
You are now fully up to date with no issues!
Mojave will be on the same Build Version 10.14.6 (18G6032)
Safari version is UPDATED – 14.0 (14610.1.28.1.10)
You are good to go!
9. Did you only install – 2020-005 Security Update?
Let’s say you need flash and you didn’t want to install Safari 14.0. But you did see the Security Update 2020-005 and installed it. In this situation, you would still be fine (maybe) even if you installed the old version of Safari 14.0. The problem would only happen if you installed Safari 14.0 first then the 2020-005 update.
What would you see in software update?
You only need to install the Supplemental Update (Safari 14.0 Fixed) and will be good to go!
In this case you would only see the fixed Safari 14.0 Supplemental Update.
Once installed you are good to go!
10. Did you install BOTH Safari 14.0 & Security Update 2020-005?
Let’s say that you had automatic updates set and you got both updates. Your system is in a broken state.
What would you see in software update?
What you would see in SU if you previously installed both problematic updates.
The following will happen in this scenario.
Fixed version of Safari Supplemental Update + fixes update will be installed
Reboot
You are now fully up to date with no issues!
Mojave will be on the same Build Version 10.14.6 (18G6032)
Safari version is UPDATED – 14.0 (14610.1.28.1.10)
You should be fixed!!!
11. Did you not install either of the updates?
Let’s say that you heard of the news of the problematic updates and were able to save your Mac.
What would you see in software update?
This is what you would see on a mac with 10.14.6 (18G6020) and Below.
You would see both updates
The following will happen in this scenario.
Fixed version of Safari Supplemental Update + fixes update will be installed
The Re-Released version of Mojave 2020-005 Security Update will install
Reboot
You are now fully up to date with no issues!
Mojave will be Build Version 10.14.6 (18G6032)
Safari version now – 14.0 (14610.1.28.1.10)
You are good to go!
12. Not seeing the 2020-005 Security Update?
You might have either installed the update or ignored it by running
If you would like to install the re-released version of the 2020-005 Security Update, all you need to do is run this command.
sudo softwareupdate --reset-ignored
The security update will now show up in software update for you to install.
14. Did you install Safari Beta 14.0.1 ?
I am testing this situation out now.
Yikes, looks like the Supplemental Update does not show up if you have installed Safari Beta 14.0.1. The installer will let you install the Supplemental Update over the top of the 14.0.1 Beta, but does not actually install.
15. Did I cover all the situations that you could be in?
Did you have an install scenario that I missed. I attempted to cover and test them all. Let me know!
16. 10.14.6 Supplemental Update Links
Apple has not released a standalone installer or pkg for the supplemental Update. I’ve included direct links from the Software Update Service below. Apple has added the Mojave 2020-005 Security Update back to the Apple.com downloads page.
It was really cool to see this little blog mentioned. 🙂
With that said, I think Apple handled this pretty good. They might have taken a bit to pull the update, but they came out with a fix only one day later!
Hopefully we can get a closer eye on update quality moving forward.
19. Thank You
I wanted to thank all of my Mr. Macintosh readers, Twitter followers, YouTube Subscribers and those who emailed me. You have shared so many of your thank-you notes, comments, tips and fix stories. I really appreciated reading them all, I created this blog for you! I am finally at a point in my life where I can take all of the knowledge that I’ve learned along the way and share it with you.
Catalina 10.15.7 Update = accountsd using 400% CPU if using iCloud
Catalina 10.15.7 Update is causing problems with the accountsd process. The issue only seems to happen if you use iCloud Drive, Mail, Calendar or Internet Accounts.
Something is wrong with the iCloud sync process. Users are saying that after they installed the 10.15.7 update, the accountsd process runs up to 400%+ in Activity Monitor. When the issue starts, it slows the Mac down to a crawl. This causes the Mac to quickly drain the battery, heat up and kick the CPU fans into high gear. Another process that could be acting up is suggestd.
UPDATE 9/29 10:00AM – I’ve added 2 new fixes in the workarounds section below. One kills the cm.apple.iCloudHelper process and recreates the .sqlite database. The other was to remove Find My Mac then re enable it.
This comes after I reported major problems with the macOS Mojave 2020-005 Security Update that came out on the same day. Apple has pulled both the Safari 14.0 and Mojave 2020-005 Security Updates.
If you use iCloud – Drive, Mail & Calander and you have installed the 10.15.7 update, you might have problems. Finder will be sluggish and general system speed is slow. If you open up Activity Monitor and then select the CPU tab, you might see accountsd taking up a huge amount of CPU. It might be running at over 400%, you can see what that looks like in the screenshot below.
accountsd taking up over 400% CPU
2. Affected macOS Build Versions
This issue affects the following macOS Build Versions.
macOS Catalina 10.15.7 Update(19H2) – Released on September 24th, 2020
macOS Catalina 10.15.6 and below, as I noticed a few reports from 10.15.6 around the 25th. For 10.15.6 users, sometimes just updating to 10.15.7 fixes the issue for them.
No reports so far of this happening on macOS Mojave 10.14 or High Sierra 10.13.
Looks like a variant of this issue goes all the way back to the Catalina 10.15.1 Update. But most reports disappeared until it came back after installing 10.15.7.
3. Affected Mac Hardware
Past problems would only happen with certain hardware models. Not this time, if you installed the Catalina 10.15.7 Update on a compatible Mac you might have problems. As I noted in the Affected macOS Build Versions above, the issue could be affecting 10.15.6 and below users.
4. What is the accountsd process?
From Apple
Help users access and manage their external accounts from within your app, without requiring them to enter login credentials. The Accounts framework provides access to user accounts stored in the Accounts database, which is managed by the system. An account stores the login credentials of a particular service, such as Twitter, and you use those credentials to authenticate with the service. When you integrate the Accounts framework into your app, you don’t need to store account logins yourself. Instead, the user grants your app access to use their account login credentials, bypassing the need to type their username and password. If no account for a particular service exists in the user’s Accounts database, you can let them create and save an account from within your app.
The first reports came in on Friday, one day after Apple released the Catalina 10.17.5 Update.
accountsd process is eating 500% cpu and making macbook pro 15,1 useless after Catalina 10.15.7 update. Even if you force this process to quit it comes back at ~500% CPU and make lots os apps to hang.
More reports started to roll in on the Apple Discussion Forums.
Same here, upgraded to 10.15.7 and CPU usage spikes. Seems that the processes ‘accountds’/ ‘commerce’ are responsible for this and killing the process ‘commerce’ is a only a temp ‘solution’ for minutes and then same problem appears again. Tried also SMC reset without success!!!
I just updated to Catalina last month. Everything was running smooth and fine under 10.15.6. I did the 10.15.7 update yesterday first through the normal way –> system preferences – Software update and then the trouble with the accountsd-process has also begun.
Additionally, boot time is slower, logging in is slower and when doing so I’m met with a blank desktop which needs 7-8 seconds before icons finally appear. Everything feels sluggish, and applications also take more than twice as long to start up.
After reading multiple reports I felt that it was time me to take a closer look.
6. I’m trying to replicate this issue now.
When issues like this have come up in the past, I might not be able to reproduce them. I have to go purely on user reports, which at times can be tough. I want to make sure the reporting is very accurate.
The test Mac was setup with the exact settings that most of the users have reported.
1. Install 10.15.6
2. Set Up iCloud Drive, Mail and Cal
3. Install 10.15.6 Update > 10.15.7
4. Test settings.
I’ve been unable to reproduce this issue. I had the article ready for this weekend but did not have enough solid reports of the issue. Now enough reports have come in to solidify the issue as a problem for users.
7. Workarounds / Fixes
This list of workarounds will start from the very simple to more advanced.
You do NOT have to follow the list until the end, just stop when one of the solutions fixes the issue for you (starting from #1).
1.Reboot! Yes multiple users have mentioned that a simple reboot fixes the issue.
2. Cycle Wifi off then back on. (I said we were starting out simple.. )
3.Sign out of iCloud then reboot.
4.Sign back into iCloud – For some users they are able to sign back in and not have any issues. If you sign back in and are still having issues keep going down the list.
5.Are you on 10.15.6 with this issue? Install the 10.15.7 Update.
6.Disable iCloud Drive Options > Internet Accounts > iCloud > Options Button > unselect all options – Restart
6. Disable iCloud options – Internet Accounts > iCloud Uncheck all – Photos, Mail Contacts, Calendars, Reminders, Safari, Find My Mac, Notes & Keychain – Reboot – If you get any popup messages asking if you want to keep the items on your Mac. Make sure you select “Keep on This Mac” if you need to save your keychain passwords for example. After this if the problem goes away you can attempt to re enable them.
7. Sign out of all System Preferences > Internet Accounts > added email addresses. This includes any IMAP, POP, Gmail, Yahoo. Office365 o365 or Exchange accounts. Reboot – Then see if the issue comes back. If not then attempt to re add the email accounts.
Below are medium skill level fixes
7. Delete local Mail store & preferences – Disable iCloud Mail Sync – then delete /Users/yourhomefolderhere/Library/mail & /Users/yourhomefolderhere/Library/containers/com.apple.mail – Enable iCloud Mail Sync.
8.Delete Local Items Keychain folder (BACKUP ANY PASSWORDS FIRST) – Users/yourhomefolderhere/Library/Keychains – It will be the blue folder with the UUID looking numbers. Delete this folder and immediately reboot.
9.Reset iCloud settings when you can’t sign out.
If you run this command it will do the following.
1. Kill the com.appleiCloudHelper process
2. Move your iCloud .sqlite database to a new backup folder
3. kill accountsd process
4. reboot
Open the terminal.app, then cut and paste the command below.
Below are more advanced level fixes that hope you don’t have to do.
9. Do you have time machine backups? Restore from your last good backup.
10. Reinstall (Not Erase) macOS Catalina 10.15.7 – This workaround will reinstall macOS Catalina 10.15.7 and you will be able to keep all your files and applications. All you need to do is download the Catalina Full installer from the App Store and reinstall. You can also do this by booting to recovery. Restart your mac and hold down Command R. This will boot you to recovery, just select Install macOS Catalina.
If you need any help with any of the above workarounds let me know in the comments.
Update Automatic Snapshots
Automatic Update Snapshots was introduced as a feature in macOS High Sierra. You can read about them below. This was one of the best features that Apple has ever added to macOS. Sadly this will not help you in this situation as they only work for 10.13 and 10.14 Security Updates. Apple disabled this option in 10.15 Catalina Combo Updates.
After updating macOS to 10.15.7, `accountsd` is using almost 600% CPU, for over an hour now. Using Safari for more than 30 seconds makes it hang, I have to force quit it. pic.twitter.com/yf7DXlFH44
@Apple Since today's update macOS Catalina 10.15.7. MacBook Pro 2019, i9 – 16 GB Ram. Fan is on constantly, system slow, battery % goes down with mac plugged to the electricity, accountsd 500% CPU: pic.twitter.com/a42ReehP6a
After updating MacOS 10.15.7, accountsd's CPU utilization spiked to almost 500%. I tried rebooting several times, but it didn't fix the problem. As accountsd is icloud sync process, I signed out from iCloud and re-signed in. And then, everything got back to normal. v(´-ω-｀)v
