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 Seeds Fourth Beta of macOS High Sierra to Public Beta Testers
- Thread starter MacRumors
- Start date
- Sort by reaction score
How EXACTLY, do you convert the System drive, to APFS?
My 2012 iMac has the OEM 750GB "flash drive:, but even through Beta 4, it still says in Disk Utility,
that it is Mac OS Extended (Journaled)
Thank you
I gave up on this Beta unfortunately. My MacBook (mid 2015 Retina Pro) basically got bricked by the 3rd beta. My MacBook refused to download or run anything, Box/Dropbox/Cloud sync service applications stopped working, and I wound up calling Apple. They couldn't even get my MacBook to properly screen share so I could show them anything. Tried restoring from Time Machine Backups and when it formatted my Hard Drive it formatted it into 4 strange partitions instead of 1 Mac OS journaled. Took me about a week to get everything back up.
I don't understand this. Why do people constantly install BETAS on their primary machines? If you NEED the machine to work, BETAS are not for you.
Orrrrrrr, do what I do. Install the BETA in a virtualized environment. I run High Sierra as a VM via VMWare Fusion on my 2017 MBP just fine. I test what I need/want without borking up my production system.
Yeah. But just for developers. It's up to version 5.4 beta 5 now. Build is 17S1180a.
It appears my MBA 13” has been hosed. I’m at the boot screen and progress bar is all the way complete but it’s not moved in well over an hour and the chassis is warm around the MagSafe connector. I tried rebooting w/ option key to see other volumes but only the main drive. Dunno. First beta since the public program was opened that I’ve had a problem.
This beta has been the only one to be completely bad for me. 2016 mbp won’t open any apps without doing the pinwheel or just closing unexpectedly all together.
Hosed my late 2015 iMac. Should I have loaded the beta? Probably not but since all other beta versions have been ok in the past, why not? Recovered using a USB stick. Guess I'll wait now until the official release...unless I get tempted to run it under Parallels.
You know what would be super helpful? If people would post in this thread (and every other beta version thread) saying they aren't installing the beta.
While High Sierra has been running fairly well, there are a few issues still needing to be sorted. The new FS is very fast for things like copying and moving large files/folders. It needs to be able to update root and other external partitions easily and that isn't the case. It's easy to repartition and create a new FS but there needs to be a way to use older partitions.
The question regarding Server is interesting. It has been mainly working fine for the last couple of betas but I still can't get any web services working -- even though they were working fine using Sierra Server. Error messages fill logs with some pretty basic messages such as wrong number of parameters on launch. I probably could figure out what the problems are and fix them, but I'd rather have Apple make it work natively. The last thing I want to do is spend time fixing it and then finding Apple's "real" fix is broken because of it. Anyway, the problems are several. One is Server Website (default) uses ALL IP addresses on port 80 and Server Website (SSL) uses ALL IP address using port 443. These are not editable.
Web sites created on the server look fine using various IP addresses and various ports, including SSL configurations but trying to access them always causes a time out on the browser. Using other IP addresses does result in the "Welcome to macOS Server" home page -- in error.
I hope this will be resolved prior to Apple giving the green light.
Just Lie with Sierra's Beta my MBP 2015 now can't connect to two external monitors... was working fine till PB4 ... same thing happened for a while with Sierra... ugh
I had a strange experience. The beta was 2.2 GB and downloading. When i came back about one hoor later, the iMac was functional but no update stil version 17315f. The last beta was active and no download again in the updatemenu. Also no mention that it was installed. Was it Pulled back?
———
Update, file did show up and is installing at the moment.
———
Update, file did show up and is installing at the moment.
Last edited:
I had some issues on my Mac Mini, took me several times before it installed, things like this happened:
- Downloaded Update and when it asks me to install it says the file had changed.
- First download was about 1.5 GB and only a 10.13b file without firmware.
- Next one was bigger but also a standalone Updater.
- Then It downloaded about 5 files but still got the Error files had changed.
- Last download did it and had the new Firmware installed.
My 2012 MBP is from the same year, hardware is almost the same and had no problems installing 10.13, the MacMini has been a drama since the initial 10.13 Dev. beta.
Exactly the same thing has happened to me. Left it overnight, still stuck at a complete progress bar. Tried safe mode; didn’t work. Any advice?
Mine is a 15” mid 2012 MacBook Pro retina.
I did this a few times and it is has been stuck with the full progress bar after the login screen over night.
[doublepost=1502294918][/doublepost]Upgraded my Mac 2011 to the new high sierra beta. All seemed to be going well until I started my MacBook app.
Apple today seeded the fourth public beta of an upcoming macOS High Sierra update to public beta testers, two weeks after releasing the third public beta. The fourth public beta of macOS High Sierra is likely identical to the fifth developer beta, which was provided to developers earlier this week.
Beta testers who have signed up for Apple's beta testing program are able to download the fourth macOS High Sierra beta through the Software Update mechanism in the Mac App Store after the proper profile has been installed.
Those who want to be a part of Apple's beta testing program can sign up to participate through the beta testing website, which gives users access to iOS, macOS, and tvOS betas. For instructions on how to install the public beta, check out our how to, and make sure to make a backup before giving the software a try. Don't install the beta on a main machine, because betas are notoriously unstable.
The macOS High Sierra update is designed to improve and refine the existing macOS Sierra operating system. Along with a new, more efficient file system (APFS) designed for modern storage, the update introduces Metal 2, the next-generation version of Apple's Metal graphics API with support for machine learning, external GPUs, and VR content creation.
Subscribe to the MacRumors YouTube channel for more videos.
High Efficiency Video Encoding (HEVC aka H.265) is coming in High Sierra, and many existing apps are being updated. Photos features a new persistent side view and editing tools for Curves, Selective Color, and Live Photos, for example, while Siri gains a more natural voice and support for more music-related commands.
Safari offers a new autoplay blocking feature for videos and Intelligent Tracking Prevention to protect your privacy, and Mail storage is being optimized to take up 35 percent less space. iMessages can now be stored in iCloud, plus there are new iCloud Drive file sharing options and new iCloud storage family plans.
For a full overview of the new features you can expect to see when macOS High Sierra is released in the fall, make sure to check out our macOS High Sierra roundup.
Article Link: Apple Seeds Fourth Beta of macOS High Sierra to Public Beta Testers
First it took 34 seconds to boot compare to previously 18 seconds. Then it started to reboot itself intermittently.
It was so frustrating that I have since had to revert back using my time machine backup. This is going to take 7 1/2 hours for a 1 TB SSD drive.
Last edited:
You have to use command line for now.
https://www.macobserver.com/tips/deep-dive/resize-your-apfs-container/
[doublepost=1502297447][/doublepost]
I don't know why people insist on it. It makes no sense to me either. Either run a VM or make a bootable clone drive to a backup drive and do a clean install of the beta, especially with this being a file system change. Should also have a bootable USB installer handy just in case.
I would never rely solely on a time machine backup to save me from a borked beta. It's just lunacy. Anyone that doesn't already have a contingency plan that includes booting from an external drive shouldn't be installing betas.
See above. You should plan on something going wrong with a beta, or else they are not for you. Installing on a drive that will takes 7.5 hours to restore is a bad idea. You've learned the hard way though, like many others.
Last edited: