Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
Just finished installing on Mid-2010 MacAir and late 2010 27" iMac. Every thing runs great including Word, Excel and Powerpoint from Office 2011. Also installed Safari Tech Preview. Man that thing is fast!! Haven't tried Time Machine yet.

More details:

My machine has an OWC SSD I installed about a year ago which I use as my primary. I left the original HDD installed and (as well as time machine) I clone the ssd to the HDD using Carbon Copy Cloner. Once my machine booted after the install I Ejected the HDD but finder now has a 'ghost' entry in the sidebar for the HDD. Can't seem to get rid it. Any ideas?
 
Last edited:
Will stay away until the stable release. As much as I love playing around with a new OS, I can wait a couple of months.
 
My big question - with eGPU support coming officially in high Sierra, with the new iMac support two eGPUs at once?
 
My 2012/3.4 GHz i7 iMac is using 20 of my 32 GB with just the chrome browser open.......
Did you verify that on your Activity Monitor? I'm curious. Also, This is a Beta of the OS; it is not likely Chrome has updated for HS use at this point, although I can't state that as a fact.
 
I also cannot back up to Time Machine. It sees the volume okay, but as soon as the backup starts, it immediately stops and crashes. Not a deal breaker for me, as I individually archive everything and store most of my data on external drives. Mid 2014 rMBP 15 2.5 i7.
 
  • Like
Reactions: DocoBob
Good thing you're testing betas for me! How is 10.13 performance on your 12" MacBook?

it's buggy, but mostly works. a little sluggish in places, some preferences not keeping. if pb2 is just a little better... it might be worth going for. but, as this forum shows, everyone has a different experience (based on our hardware, our apps, the weather, astrology, magic). really, so many variables that no one can guarantee anything (and it's that unknown quality that makes me want to run betas...) :eek:
 
Can't say that I find my MBA any slower or different after upgrading to HS, but what is this kernel_task that uses 830MB of memory?
 
The updated Photos is awesome. It has excellent new stock features and also seamlessly integrated my Affinity and Pixelmator apps/extensions. After 2-3 days running, I'm pretty happy with HS so far. Other than Time Machine not backing up without crashing, I've had pretty good experiences with my usual workflows.
 
  • Like
Reactions: DocoBob
Here is something big -- I have the beta installed MBP 2013 (trashcan) and the speed of internet is vastly greater. I have cable speed maximum of 200 and with the prior build and betas, never got above 30-50 where my computer is located. Without moving anything, just the new beta, it now consistently measures over 100! This is over many days/times. Amazing improvement. Otherwise, love the new beta.
 
  • Like
Reactions: OperatorJ81
Well, that'll teach me. Got this message and then get a cycle of kernel panics and automatic reboots. Doing a repair now, hopefully that works. If not, I'll be doing a restore.

I experienced the same thing, tried four times then it finally installed just fine (except for all the bugs LOL).
[doublepost=1498937679][/doublepost]
Ok, boot into recovery (CMD+r) and repair, then do a reinstall - NOT converting to APFS
I tried that several times but got the error message that the disk was not repairable. After five or six attempts in recovery mode I selected to reinstall the OS (from inside recovery mode) and after a few more of those attempts it worked and I booted into High Sierra (with APFS).
[doublepost=1498937960][/doublepost]
Broke Time Machine backups for me. Says no disks available but all my other Macs are backing up fine. Removing and readding the disk to Time Machine didn't help.
I experience the same thing, it simply won't access my existing Time Machine backups.
[doublepost=1498938338][/doublepost]
Why are early betas always making the processor run hot?

I've never coded as part of a corporate team so I really don't know how things work in that environment.

Is it because features ordered in by management are slammed in as fast as possible in a high level language then later clean up crew goes back and tightens stuff up in lower level language?
[doublepost=1498798160][/doublepost]

Modern life lol. We've all been there. We feel your pain.

All the big high tech corporations that I worked for in Silicon Valley do the same thing, its essentially standard procedure. The two main causes are the Debug code. There is extra code that helps the developers figure out what the program is doing or not doing, which hopefully helps to pinpoint where the bugs are located. This debug code adds significant work that has to be done, which is why we can see higher CPU use, higher fan speeds and sluggish performance in the early Betas. Of course, sometimes all those issues are directly because of the bugs themselves. Eventually when the bugs appear to be reasonably under control, the developer receives permission to remove the debug code which is why suddenly the next version seems noticeably faster or more responsive.
[doublepost=1498939639][/doublepost]
Got everything working (very speedy 2015 MBP now) except for Time Machine. Have turned TM off/on, rebooted the Mac and the Time Capsule, deleted and reselected the disk, but it still won't work. Says disk "Backup Failed: No disks are available to back up.
The MBP is using APFS.
I'm experiencing the same things, also using APFS, no matter what I have tried, including power cycling the Time Capsule, nothing has helped. It appears to start the backup then fails. I did notice one thing: for the Sierra Beta it did the same exact thing and I never resolved it so I had to start a new backup from scratch. Sierra did not use the name of the Time Capsule (as was preciously normal) but instead simply called it "Data". Now High Sierra does not recognize "Data" because its looking for the actual name of the Time Capsule.
[doublepost=1498939922][/doublepost]
Ok, so finally got HS installed on my 2015 MBP. But it would not convert to APFS during install. Fine, I'll do it later.

Boot into recovery, attempt APFS conversion. No joy. Reboot & repeat. Same thing. Any suggestions? I have a 2015 3.1/16/512 SSD rMBP. Can't seem to find any reason why it's failing.
Since APFS is brand new to us, I cant even fathom a guess, other than to try disc utility from within High Sierra (it has fsck_hfs and the new fsck_apfs) and see if it can sort you out.
[doublepost=1498940101][/doublepost]
It’s the memory consumption that’s killing my early 2011 MacBook Pro. The memory pressure is always high. It’s usable, but not great. Hopefully this will be fixed in the next build. Previous developer builds would just seize up all the time, so they made some improvements at least.
Only 2012 MAcBook Pro the memory pressure is very low, lower than in Sierra. Maybe you should look at each process and see if one of them is eating up all your RAM. I would also check spotlight to see if its re-indexing your drive and using excess RAM in doing so.
 
Should the Time Machine backups work normally in the public beta? "Macintosh HD" is shown in the list of excluded items and it cannot be removed there.
That is so odd, I was wondering why my Time Machine backups would not run on my 2012 MacBook Pro so I just peeked at the excluded items list and see that my SSD is listed there. I wonder if Apple purposely doesn't want the APFS formatted drive to be backup up (for some unknown reason). I'm reporting it asa bug but don't know if I will remove the SSD from the excluded list (I have another backup drive that I will probably use to backup this HS/APFS machine).
[doublepost=1498942777][/doublepost]
Day 2 with the beta... Anyhow, the bug has to do with dock icons showing as generics. Has anybody else experienced this problem? See picture below.

I can only think of two things to try:
First I would quit all apps, delete all Caches in the system and reboot. See if that worked.
Second, if that didn't work, is to reset Launch Services with the following command:
/System/Library/Frameworks/CoreSe\/System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/LaunchServices.framework/Versions/A/Support/lsregister -kill -seed
 
im gonna sit this one out. I got the install loop and had to restore to Sierra. Good features I use the beta so that when my clients download it I am one step ahead of them.
 
Office Mac 2016 works fine if you are on the fast ring for insiders and you update before you go to High Sierra. It's also dependent on whether you upgrade to the new file system. If you don't, you'll be fine.

The question for me is, and I know I will be mocked, but does Office 2011 still work? It currently still does under Sierra and I don't need anything new or pay the Microsoft or Apple monster a tax to make it sill work.

The top secret way that Apple makes a fortune along with other companies is "Planned obsolescence."
They just make it not work on purpose to make more money on upgrades. An operating system that breaks half of your programs is not a good one in my opinion no matter what enhancements it offers. If more people made this known, they wouldn't do it.
[doublepost=1498971891][/doublepost]
From Microsoft directly - https://support.office.com/en-us/ar...h-Sierra-80bbd3cc-2412-4593-988a-1c5607b26b28

Microsoft Office support for macOS 10.13 High Sierra

Apple announced a major new version of macOS 10.13 High Sierra on June 5th, 2017. While the new operating system is not generally available to all users right away, developers and beta testers may have access to beta seeds. Read more to learn about the supportability of running Office for Mac on 10.13 High Sierra.

Office 2016 for Mac
See "What version of Office am I using?" if you don't know what version you're on.

Version of Office

Supportability

15.35 and later

15.34 and earlier

These versions are not supported on 10.13. In some cases, you may not be able to launch the Office apps. For example, users will see the following error message when attempting to launch Outlook 2016 ver. 15.34:

47c04f29-40fb-4453-8c4b-7fc225f1d426.png


If you installed Outlook 2016 ver. 15.34 or earlier, and are not being offered an update to 15.35 or later, download the latest Office 2016 for Mac Suite Installer here.


Office for Mac 2011
Word, Excel, PowerPoint, Outlook and Lync have not been tested on macOS 10.13 High Sierra, and no formal support for this configuration will be provided.

All applications in the Office for Mac 2011 suite are reaching end of support on October 10th, 2017. As a reminder, after that date there will be no new security updates, non-security updates, free or paid assisted support options or technical content updates. Refer to the Microsoft Support Lifecycle for more information.

I personally find it VERY RICH of Apple to EOL versions of Microsoft Office that Microsoft is still supporting! I mean, are funds tight at Apple? This is INSANELY RIDICULOUS!

Seriously, I'm going to stop installing PLANNED OBSOLESCENCE UPGRADE-WARE.

This is like a LEGAL version of WannaCry VIRUS! ALL YOUR PROGRAMS ARE BELONG TO US!
 
Last edited:
The question for me is, and I know I will be mocked, but does Office 2011 still work? It currently still does under Sierra and I don't need anything new or pay the Microsoft or Apple monster a tax to make it sill work.

The top secret way that Apple makes a fortune along with other companies is "Planned obsolescence."
They just make it not work on purpose to make more money on upgrades. An operating system that breaks half of your programs is not a good one in my opinion no matter what enhancements it offers. If more people made this known, they wouldn't do it.
 
I experienced the same thing, tried four times then it finally installed just fine (except for all the bugs LOL).
[doublepost=1498937679][/doublepost]
I tried that several times but got the error message that the disk was not repairable. After five or six attempts in recovery mode I selected to reinstall the OS (from inside recovery mode) and after a few more of those attempts it worked and I booted into High Sierra (with APFS).
[doublepost=1498937960][/doublepost]
I experience the same thing, it simply won't access my existing Time Machine backups.
[doublepost=1498938338][/doublepost]

All the big high tech corporations that I worked for in Silicon Valley do the same thing, its essentially standard procedure. The two main causes are the Debug code. There is extra code that helps the developers figure out what the program is doing or not doing, which hopefully helps to pinpoint where the bugs are located. This debug code adds significant work that has to be done, which is why we can see higher CPU use, higher fan speeds and sluggish performance in the early Betas. Of course, sometimes all those issues are directly because of the bugs themselves. Eventually when the bugs appear to be reasonably under control, the developer receives permission to remove the debug code which is why suddenly the next version seems noticeably faster or more responsive.
[doublepost=1498939639][/doublepost]
I'm experiencing the same things, also using APFS, no matter what I have tried, including power cycling the Time Capsule, nothing has helped. It appears to start the backup then fails. I did notice one thing: for the Sierra Beta it did the same exact thing and I never resolved it so I had to start a new backup from scratch. Sierra did not use the name of the Time Capsule (as was preciously normal) but instead simply called it "Data". Now High Sierra does not recognize "Data" because its looking for the actual name of the Time Capsule.
[doublepost=1498939922][/doublepost]
Since APFS is brand new to us, I cant even fathom a guess, other than to try disc utility from within High Sierra (it has fsck_hfs and the new fsck_apfs) and see if it can sort you out.
[doublepost=1498940101][/doublepost]
Only 2012 MAcBook Pro the memory pressure is very low, lower than in Sierra. Maybe you should look at each process and see if one of them is eating up all your RAM. I would also check spotlight to see if its re-indexing your drive and using excess RAM in doing so.
It’s a fresh install. Spindump seems to be a culprit. A lot of compressed memory too - much more than Sierra. Spotlight has finished indexing.
 
Oops. I forgot this came out. I haven't touched my MacBook Pro for months, since I built my PC.
 
I'm up to 8 freezes now (I reported it to Apple after the 2nd time). The mouse moves but clicking does nothing. Then I touch a key on the keyboard and that does nothing except freezes the mouse in place. Audio keeps playing in the background for about 30 seconds and then stops.

I've noticed other things too, like playing YouTube videos sometimes the video freezes but the audio keeps playing and eventually the video fast forwards (it literally looks like it's fast forwarding) to catch up with the audio. And sometimes the video just remains frozen the entire time and I have to keep restarting the video to get it to play properly. This is with Safari (I haven't tried YouTube in a different browser).

I have the 2014 Mac Mini (the cheapest one money can buy!).
 
Has anybody managed to get Air Display to work with High Sierra? When I try to connect my Mac Mini to my iPad Pro, it crashes the Mini. Reinstating he Air Display Host and the iPad app didn’t help. (Meanwhile, at least I can use my TV as my sceeen.)
[doublepost=1499015946][/doublepost]
Maybe some helpful info here: https://discussions.apple.com/thread/7467525?start=0&tstart=0
[doublepost=1498835970][/doublepost]

Hardware compatibility list - http://osxdaily.com/2017/06/06/macos-high-sierra-compatibility-list/

Thanks! It was indeed nothing more than a problem with one of my “launch at log in” programs. Turned it off for now.
 
Well, after a few day, I'm absolutly astonished how good this is for a 1st Public Beta. Applications that didn't work already have beta versions that do, and so far it's been almost perfect. A few spinning beach balls (mainly in Safari) and some Apps seem to take a little longer to load, but in general it's much faster than the 10.12.6 beta I was running. Temperatures also seem to be lower, or at least the fan noise is.

Assuming each beta improves things, this is going to be better than Snow Leopard :D
 
I personally find it VERY RICH of Apple to EOL versions of Microsoft Office that Microsoft is still supporting! I mean, are funds tight at Apple? This is INSANELY RIDICULOUS!

Just a few thoughts:
Upon reading the linked Microsoft support article the end of life for that version of Office is October. Microsoft is basically saying they are not going to be investing any considerable resources to ensuring it works for a major OS upgrade that will come out 30 days before it’s EOL.

They’ve probably alerted Apple to the fact it won’t be upgraded for the new OS hence Microsoft showing us what the error will look like. There would probably be more than a few people who wouldn’t figure out what the issue is without such an alert.

While I get the POV it’s planned and well to a degree it probably is on Microsoft’s end but there are examples of this on any device.

An OS is upgraded and the developer has to decide to upgrade the app for exisiting users or make a whole new app.

We seen this with Windows XP to Vista to Windows 7 to Windows 8 and to Windows 10 with some software at least. We seen this most noteably going to iOS 7 where more than just a few developers decided to just make a new version and not update older apps for iOS 7. On Mac companies like Quicken, Parallels, and others at least in the past a new version of their app for every new Mac OS.

I personally think it’s great Microsoft updated 2011 as long as they have.

So OS’s despite the platform are constantly changing and refining how things work and this often requires a developer to maintain an app. I have many favorite apps no longer updated across platforms. Another example is Mac is going 64 bit only next year for apps. Remember how many things broke when windows went 64? Mac’s have been 64Bit for a very long time but still to this day supports those older 32Bit apps which still need some love from time to time to support OS upgrades.

Good news is you have options which u may not like such as parallels where u can run older versions of Mac or windows from your desktop.

Also for those with time machine backup issues unless I’m wrong the developer beta notes time machine does not currently back up High Sierra.
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.