Microsoft’s Office 2016 crashes like a banshee on Apple’s OS X El Capitan

“If you are a Mac user that relies on Office 2016 apps to get your day-to-day work done then you might want to hold off on upgrading to OS X El Capitan,” Adrian Kingsley-Hughes reports for ZDNet.

“According to an extensive thread on Microsoft’s Office for Mac support forum – combined with firsthand experience of the issue – the problems seem many and varied. Outlook appears to be the main culprit, but Excel and Word are also reported to be problematic for some,” Kingsley-Hughes reports. “For some the apps crash while in use, while for others it is coming out from sleep that causes issues.”

Kingsley-Hughes reports, “Others are finding that as soon as one app from the Office 2016 suite crashes or locks up, the others then follow suit.”

Read more in the full article here.

MacDailyNews Take: Microsoft. As ill-prepared and incompetent as ever.

Meanwhile, Mail, Pages, Numbers, and Keynote are working just fine for us. 100% Microsoft-free is the only way to fly!

SEE ALSO:
Microsoft’s Office 2016 for Mac is wildly unstable on OS X El Capitan – September 30, 2015

30 Comments

    1. I had to take all of my Outlook 2011 Exchange email and move it over to the Apple Mail app. Outlook 2011 crashes every single time I open it. Sometimes it will sync, then crash, sometimes it crashes right on startup, but it crashes every single time since the first El Cap beta. Tried every trick in the book (rebuilding db, moving files out to see what is causing it, etc.) and nothing works. Good news, the Mail app handles my Exchange mail just fine and now all of my email is in one place. Wish I’d moved it earlier 🙂

    2. My company runs Outlook 2011 which, according to our IT folks, doesn’t work well in the El Capitan. I’m afraid I don’t know specifics, so we’ll both need to search for more details.

      1. Some of us have no choice as the company has standardized on Microsoft Office. Oh we are told we can use other options, but there is no support and getting them to work with Exchange servers can be as big a trial as using Office!

  1. El Capitan has a much tighter security model. One item is preventing programs/users from altering /usr. A number of Unix and Unix type programs use /usr for executables, segments, libraries, etc; modifying /usr is no longer allowed.

  2. The *public* beta was out over a month ago. The *developers* beta, which Microsoft would’ve had access to, was available for even longer.

    As one of the largest vendors of *paid* office software for Mac, Microsoft has no excuse for it to be this bad.

  3. Been using Office 2016 on El Capitan for months without crashing. Only problem I have is slowness, slow to load and lag using the apps. I have older hardware from 2009, but they aren’t under powered junk. Mac Pro with 12GB ram, 2.66GHZ and Mac Pro 17″ 2.93Ghz, 8GB, and both have a 500GB SSD.

  4. Apple’s suite is great for light usage. Try doing work full time on a Mac with a normal enterprise. You can’t go Microsoft free. If you’re doing any serious work on documents or have a heavy dependency on your Mail / Calendar, you can’t just use Apple’s suite and mail.

    If you’re a SMB or a home user, all day every day. If you’re in a larger organization good luck.

    Office 2016 is fantastic on 10.10. Outlook is fantastic, outside of WebEx Plugin not supported but that is on Cisco. yes it does crash buy Office 11 is a disaster.

  5. My experience is that complex Excel apps with Macros or large power points that worked fine with Office 2016 under Yosemite now cause near immediate crashes with El Capitan. Similar problems with Word and complex documents. However, Office 2011 still works OK under El Capitan, as far as Excel, PowerPoint, and Word go.

    I hate Outlook on any platform (have to use it at work) and don’t ever use it on my Mac. So, I can’t speak to how it works. BTW, was an early tester of Office 16 on the Mac; was pretty rough at first, but smoothed out with late builds. . But that was on Yosemite… I guess MS never bothered to download any El Captian builds and test them unlike myself (developer, part time).

  6. No problems at all with Excel or Word 2016 (large double-column docxs with multiple various embedded 3rd party graphics). Don’t and have never used Outlook (which seems to be the problem).

  7. No wonder the way they have programmed this shit.

    Look at the content of one of these apps and you see a large number of libraries that will translate OS X calls to Windows APIs which is executed.

    This both makes it much harder to keep compatible with new OS X versions, it makes the apps slower and makes for the bloat these apps have on both OS X and iOS. It potentially makes them more vulnerable too as the Windows code have inherited all the “features” from, well, you know…

  8. I’m not surprised by this at all, but I’m also disgusted by it. Microsoft is one of Apple’s oldest developers yet they didn’t bother to make sure their apps were compatible with El Capitan. It’s clear that QA testing isn’t done at Microsoft, and if it is, the test results didn’t matter to them. Hopefully, they’re working on an update, but since it took them five years to release a new version of Office for the Mac, I’m not going to hold my breath.

Reader Feedback

This site uses Akismet to reduce spam. Learn how your comment data is processed.