This is not GM, it is GM candidate, which still is beta
Got a tip for us?
Let us know
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
Apple Releases macOS High Sierra Golden Master Candidate to Developers and Public Beta Testers
- Thread starter MacRumors
- Start date
- Sort by reaction score
Trump wasn't the president November 1, but January 21 he was. A candidate doesn't change if it becomes the final GM. It's a candidate to become the GM. IF it becomes the GM, the build number doesn't change.
It seems absurd that we cannot plainly see the build number prior to (re)downloading a 5GB image. The App Store may give Apple better control over this process but for the rest of us the UX is just hellish.
Yep, I am not sure if I really want to install this on my main system yet. Tempted, though.
Build number will stay the same but drop the "a" at the end on number
I've tried the public beta download by re-enrolling, didn't work.. it downloaded an earlier build.
I've now logged in to my works developer account and tried downloading it from there, it's opened MAS but fairly certain it's going to be the wrong build again.
Why don't they just put the f### build number in the title or something.
I've now logged in to my works developer account and tried downloading it from there, it's opened MAS but fairly certain it's going to be the wrong build again.
Why don't they just put the f### build number in the title or something.
I don't know why anyone would have to re-enroll. I simple went to the Apple beta software page, logged in and clicked the link to the High Sierra beta page in the Mac App Store. Downloaded from there and bam....17A362a.
Right click in finder Get info if it was created 9th/10th Sept version 13.0.61 its the correct installer.
I wish I knew if it did...still cannot download. AOL's IM default app sucks and love using Apple's messages instead
Been using High Sierra since the first DP beta, and it's been pretty good so far. The early builds were definitely rough around the edges (to be expected), but the past few builds have been relatively stable. I've noticed a few issues, mainly with iTunes and Photos. When I have iTunes open the computer can slow to a crawl - but not always. I haven't tested it since the 12.7 release of iTunes, so that might help. Photos is just buggy as hell. I have a relatively large photos library (167.7 GB, 18000+ photos and videos, mostly photos), but had few issues under Sierra. There were periods when it would slow down some, but usually when I was importing a bunch of photos while editing existing photos and what not. In High Sierra it can run really slow all the time, in full screen mode I get weird screen artifacts (like a white bar on top, where the toolbar should be - until I mouse over it and the toolbar appears), can crash a lot - typically I get the spinning beach ball of death and have to force quit. I've reported the various issues to Apple, and while Photos has definitely become more stable since DP1, it's still buggy. I'm actually really excited about some of the additional editing features in Photos - will require less use of 3rd party extensions - but at the moment it is rather annoying to use. Hopefully, though, these issues can get ironed out before public release (haven't had a chance to install this GM candidate to test it out).
My biggest cause for concern, however, is APFS. I'm currently running APFS on both my MacBook Pro with dedicated flash storage, and my iMac with a fusion drive. High Sierra automatically updated my MBP to APFS, but did not updated the fusion drive. In fact, I could even manually convert the fusion drive to APFS - I actually wiped my machine completely, recreated the fusion drive and formatted it as APFS (so obviously APFS works with a fusion drive). So far it seems to be running just fine - and there are some obvious benefits to it already. I had a major issue in a recent build that prevented my iMac from booting, I figured I'd have to just restore from a Time Machine backup. Fortunately, because of APFS, Time Machine creates local snapshots on the internal hard drive, and I was able to restore to one of those snapshots prior to the issue I had. It was easy, fast, and actually worked (unlike a similar feature in Windows allowing you to restore the system to a previous point if you're having issues, which rarely works to resolve the issue). With that being said, and speaking of Time Machine backups, external Time Machine backups still need to be formatted as HFS+. It thus appears that at the moment, external Time Machine backups gain no benefit from the new features in APFS (specifically the aforementioned snapshots). I'm sure this will change at some point down the road...but who knows when. Which brings me to my biggest concern about APFS, there's just not a lot out there about it. Apple has published a number of different documents delving into some of the features and specifications about APFS, but there are still a lot of unknowns. The fact that there is no mention of external Time Machine backups in the documents (only local backups are mentioned) and that a lot of API's haven't been published (snapshots, clones, etc) just has me leery, it feels like APFS is still in beta stages. This wouldn't necessarily be an issue, but any machine running just flash (no fusion drive) will be automatically upgraded to APFS, with no option to NOT be upgraded. Hopefully when the final release is available Apple will publish more info on APFS.
My biggest cause for concern, however, is APFS. I'm currently running APFS on both my MacBook Pro with dedicated flash storage, and my iMac with a fusion drive. High Sierra automatically updated my MBP to APFS, but did not updated the fusion drive. In fact, I could even manually convert the fusion drive to APFS - I actually wiped my machine completely, recreated the fusion drive and formatted it as APFS (so obviously APFS works with a fusion drive). So far it seems to be running just fine - and there are some obvious benefits to it already. I had a major issue in a recent build that prevented my iMac from booting, I figured I'd have to just restore from a Time Machine backup. Fortunately, because of APFS, Time Machine creates local snapshots on the internal hard drive, and I was able to restore to one of those snapshots prior to the issue I had. It was easy, fast, and actually worked (unlike a similar feature in Windows allowing you to restore the system to a previous point if you're having issues, which rarely works to resolve the issue). With that being said, and speaking of Time Machine backups, external Time Machine backups still need to be formatted as HFS+. It thus appears that at the moment, external Time Machine backups gain no benefit from the new features in APFS (specifically the aforementioned snapshots). I'm sure this will change at some point down the road...but who knows when. Which brings me to my biggest concern about APFS, there's just not a lot out there about it. Apple has published a number of different documents delving into some of the features and specifications about APFS, but there are still a lot of unknowns. The fact that there is no mention of external Time Machine backups in the documents (only local backups are mentioned) and that a lot of API's haven't been published (snapshots, clones, etc) just has me leery, it feels like APFS is still in beta stages. This wouldn't necessarily be an issue, but any machine running just flash (no fusion drive) will be automatically upgraded to APFS, with no option to NOT be upgraded. Hopefully when the final release is available Apple will publish more info on APFS.
You need the full installer, by installing the access utility again. There is also a link and a Terminal command to get directly to it in the App Store. I would post it, but I don't have time to search at the moment.
Done:
[doublepost=1505416221][/doublepost]
Exactly as you can see in my screenshot.
Done:
[doublepost=1505416221][/doublepost]
Exactly as you can see in my screenshot.
As much as I am also excited for these new innovations especially around the file system, I have to admit that my normally rambunctious early adopter has a little bit of pause given the fact that we are talking about filesystem changes. We’re not just talking about things that do or don’t work and you can move around them, we’re talking about overall data integrity and the most fundamental aspect of how information is stored on your machine.
I found that to be able to download this GM, I had to remove the old "Install macOS High Sierra.app" first from the Applications folder. Here's the link to the installer on the app store: macappstore://itunes.apple.com/us/app/macos-10-13-seed-1/id1209167288?ls=1&mt=12
I haven't seen real numbers for disk performance yet, Any hard performance improvements verified on platter performance?
Guys just a thought here but can macOS possibly support a true tone experience? I mean, is it hardware dependent?
Thank you, I dug into the files and found SystemVersion.plist which contained the following string:
Code:
<key>ProductBuildVersion</key>
<string>17A362a</string>
The ambient light sensor built into Macs can detect the level of light, but not the tone of light. Therefore True Tone wouldn't be possible.
GM candidate indicates that they are not 100% confident that it will be the GM.
Personally, I’m waiting until they do declare a build as actual GM. I don’t want to take a risk when filesystems are involved. Grateful to those that have been testing and filing bugs, of course!