Posts

Post not yet marked as solved
6 Replies
There should be something about additional updates to install, and you can view more and then select macOS Big Sur Beta 3 which is a smaller download at ~4GB.
Post not yet marked as solved
2 Replies
Good news everyone! I solved the issue. You're going to want to boot in to Recovery mode to fix this one. Not sure why the file is being locked when you're logged in, but roughly follow these steps to resolve:Launch Terminal in Recovery.diskutil apfs unlock "Macintosh HD - Data"cd /Then you'll want to cd in to Volumes then Macintosh HD - Data, and progress until you get to your User folder which includes this Archive. You can then remove the directory using rm. Perform this at your own risk! Make sure you know your way around Terminal. I'm sure Apple will fix this soon.
Post not yet marked as solved
2 Replies
Final update: Installed Catalina Beta, which allows Recovery to boot again. My guess is there's a versioning issue somewhere when downgrading to Mojave in certain instances. I don't believe my Mac mini experienced this, but I went back to Mojave on Beta 2 instead of 3. Seems my Recovery was expecting Catalina but found Mojave installed instead?All is "fixed" now though.
Post not yet marked as solved
2 Replies
I've now tried the latest Mojave beta as well to no avail. I saw someone on MacRumors speaking of a similar problem. Perhaps the system is looking for Catalina compatible Recovery, which doesn't exist anymore?
Post not yet marked as solved
75 Replies
From KrisJa at MacRumors"If you are currently on Beta 2, 'softwareupdated' will install a bunch of packages to /Library/Updates/041-81733.In this location there is 041-81733.en_GB.plist which has a line:<bridge-version build-version="17.16.10496.5.4" build-group="0"/>This fails to install for reasons mentioned earlier in this thread.HOWEVER, if you re-install the Developer Beta Profile, it will instead download a larger set of packages to /Library/Updates/041-81731.041-81731.en_GB.plist has an internal reference to build number 19A501i which is more recent than Beta2 which is 19A487iThe download finished and I am greeted with a functional installer Window...EDIT: it is now installing just fine. Moral of the story: re-install the profile"Can confirm this worked on my 2018 Mac mini. Just had it error out on me at the last 15 seconds though...
Post not yet marked as solved
75 Replies
2015 doesn't have a T security chip. Perhaps they bundled a old bridgeOS version by accident when they deployed the update? Not sure how they missed this one if versioning is indeed the issue.
Post not yet marked as solved
75 Replies
T2 chip specific then?
Post not yet marked as solved
75 Replies
It appears there might be a typo in the update...Minimum bridgeOS version requirement set: 17.16.10496.5.4,0Update bundle package component's bridge version (17.16.10466.5.18,0) doesn't satisfy minimum requirement (17.16.10496.5.4,0)It looks like they may have meant to put minimum version at 17.16.10466.5.4,0 but someone typed 96 instead of 66? Just a guess!
Post not yet marked as solved
75 Replies
It also downloads everything for me and then fails to actually install it. Appears several on MacRumors are reporting this as well.
Post not yet marked as solved
7 Replies
Any workaround you can suggest? This issue is making my system nearly unusable.
Post not yet marked as solved
2 Replies
I’m experiencing the same issues as you’ve mentioned. I’ve filed a bug report as well. Very frustrating.