Apple today seeded the first beta of an upcoming macOS Sierra update to developers, just a day after releasing the new operating system to the public.
macOS Sierra Beta 10.12.1 is available for download through the Apple Developer Center and through the Software update mechanism in the Mac App Store.
/article-new/2016/06/macossierraroundup-800x463.jpg?lossy)
It is not clear what improvements the first update to macOS Sierra will bring, but it's likely to include bug fixes and performance improvements for issues that have been encountered between the time between the beta testing period and release.
We'll update this post with any new features that are found in macOS Sierra 10.12.1.
Top Rated Comments
(View all)I never install a .0 release, including 10.12.1.0 ...
I install them all. Somehow I survive.Siri is non-functional on my 2014 5k iMac. (It can't find the iMac's internal microphone.) So I hope Apple gets that straightened out. After all, it's Sierra's most-touted feature.
First the headphone jack on the iPhone, now the microphone on iMacs ..... Apple are in a courage overdrive.I am running the official retail version of Sierra (I was part of the developer beta programme). I since changed my SYSTEM PREFERENCES -> APP STORE -> and changed "your system is set to receive pre-release..." to NO.
For some reason disabling the "pre-release updates" setting in the App Store system preference isn't working. You can solve this by opening terminal and entering:Since then that option no longer appears in the APP store.
However, in my updates the BETA for 10.12.1 is showing which is exactly what I do NOT want.
How can I disable this given I've already done the above.
sudo defaults delete /Library/Preferences/com.apple.SoftwareUpdate CatalogURL
Enter your password when prompted.
This will set Software Update back to using the standard non-beta catalog.
Interesting, only a day after release, curious to see what this will bring to the table...
They will have been working on 10.12.1 for at least a month, probably much longer, so it is not that surprising. There comes a time when it become too risky to add certain fixes to the 10.12.0 build and you're better off saving them for the first major update.