Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
As much as I hate Office and M$ as a whole, iWork is no better. M$ knowns they have a "monopoly" in this case, so they don't really care and take their time. What are you going to use instead? Nothing, you'll wait like a puppy. I tried openoffice and Libraoffice, they just aren't the same in terms of functionality. Keynote also has many weird bugs like freezing once changing many times between windows (with CMD+TAB) and this has been like that for years.
 
This may have been mentioned already, but I have been running El Capitan through all the betas, and Office 2016 through all the preview to current.... and while I have run into some bugs along the way, everything is running perfect right now. I use the crap out of it and I haven't had any issue. Wonder what the deal is.
 
I'm using Word 2016 on El Capitan quite a lot these days, dealing with 100-page documents and/or documents filled with images (i.e. the kind of documents you just know are going to be a pain): apart from the occasional crashes, which used to occur on Yosemite as well, the 2016 version still looks and feels way more stable and reliable to me than 2011 ever was. I'm quite surprised at how rarely I've been cursing at Word lately.
 
Dear Microsoft while your working on that office update do you think you can give the apple boy's a hand in fixing the broken "time machine"!
 
Two things:

1. developers can't really start debugging till the GM is released as each BETA build might break a fix that someone spent all day on so it's kinda pointless. Also, I believe the GM was out for like 1.5 week so not much time to fix bugs.

2. Office 2016 was just released a few weeks ago and has it's own bugs that need fixing. I don't think the office team needed a new OS to introduce even more bugs at this point.

Please note that my views and opinions do not officially represent Microsoft. I partake in this forum as I appreciate the community.

1) That maybe true but how many of these bugs are the result of Microsoft's elaborate abstraction for the sake of portability resulting in a tower of cards that can fall over at the slightest change?

2) Office 2016 was released more than a 'few weeks ago' - it has been available on Office 365 subscribers like myself since 9 July 2016 and more importantly they've had 4 years to not only update the code but also move it to 64bit as well.

I might have some sympathy for Microsoft if they were some small organisation trying to keep up with the changes Apple introduces but Microsoft isn't some rinky-dinky organisation consisting of two men and a dog but rather a multibillion dollar company that has little in the way of excuses as to why OS X continues to remain the neglected step child of the Office portfolio of supported platforms.

Edit: I'm lucky in that my requirements of Office isn't that high with me primarily using Pages/Numbers/Keynote. The fact that Office is the 'best of the worst' shouldn't mean that Microsoft sits back satisfied with mediocrity and instead should be aspiring towards 100% feature parity between the Windows and Mac version rather than the Mac version being the cut down half finished version for many years.
 
  • Like
Reactions: julsssark
Wow! I got the most recent Office update when it came out and also upgraded to El Capitan on day one. I've used Word and Outlook extensively since then... Never had a problem.

Read this article at work, didn't think much of it. Came home, woke computer from sleep, Outlook won't open. Finally get it to open. Try to open a Word document, crashed twice, finally opened on the third time.

So, basically, I think Macrumors jinxed me lol.

Hopefully they fix this soon, or I will have to work on my documents on my PC.... Argh...
 
Two things:

1. developers can't really start debugging till the GM is released as each BETA build might break a fix that someone spent all day on so it's kinda pointless. Also, I believe the GM was out for like 1.5 week so not much time to fix bugs.

2. Office 2016 was just released a few weeks ago and has it's own bugs that need fixing. I don't think the office team needed a new OS to introduce even more bugs at this point.

Please note that my views and opinions do not officially represent Microsoft. I partake in this forum as I appreciate the community.

In the case of Outlook 2011 hanging when syncing with Exchange, the article describing the problem was dated five days prior to El Capitan's release, so Microsoft had identified it with the GM, if not earlier. I would have expected their dev team to have at least begun its investigation by then. Even if that weren't possible, it would have been good if Microsoft had done more to publicize the issue before people installed 10.11 - I know that I would have held off.

In any case, it's good to hear that a solution is in sight.
 
Two things:

1. developers can't really start debugging till the GM is released as each BETA build might break a fix that someone spent all day on so it's kinda pointless. Also, I believe the GM was out for like 1.5 week so not much time to fix bugs.

2. Office 2016 was just released a few weeks ago and has it's own bugs that need fixing. I don't think the office team needed a new OS to introduce even more bugs at this point.

Please note that my views and opinions do not officially represent Microsoft. I partake in this forum as I appreciate the community.

Yeah, except my GM copy of El Capitan is dated 15 Jul. with at least one of my bug reports to Microsoft about this leaving about 2.5 months for Microsoft to get their act together. My copy of Office was updated on 15 Sep. The bug is years old and now they have to fix it.

I understand their problems but more than a few in their culture still do not like Macs.
 
I think that your experience depends on what features you are using. I have been having horrible issues with PowerPoint. It seems to be editing SmartArt items. Crashes almost ever time I work with one, even if it is only repositioning it. I haven't had Excel crash though. So, I think some people may have no issues because they access stable features and others have huge issues because they are using buggy features.
 
Has anyone else noticed that the dump lists more cores than your mac has? My dump showed 4 and the system has only 2. It may be an un-related error...
 
At least I'm not the only one. A couple of minor issues are expected, but a failure in Outlook and Exchange Server. How do you miss that in beta testing? We run everything off of our Exchange server, and having to use Mail and Calendar is just a pain. If no one has said it yet, perhaps El Crapitan would have been a more appropriate name. While your at it, fix the issues with HP printer/scanner drivers.
This has got to be an isolated issue. I have no problem with HP printer with OS X el capitan.
 
Two things:

1. developers can't really start debugging till the GM is released as each BETA build might break a fix that someone spent all day on so it's kinda pointless. Also, I believe the GM was out for like 1.5 week so not much time to fix bugs.

2. Office 2016 was just released a few weeks ago and has it's own bugs that need fixing. I don't think the office team needed a new OS to introduce even more bugs at this point.

Please note that my views and opinions do not officially represent Microsoft. I partake in this forum as I appreciate the community.
Maybe it's apple's fault too. Maybe they should find a way to make all apps compatible.
 
My Excel sheet refused to print on 8.5x11 - kept trying to print to 8.5x14 rear feeder until I opened page settings and set the page format to 8.5x11. Upon printing, the column that had a yellow background instead ended up in a sort of blurry yellow/salmon color, varying between each line of print. Once I got it printed, the app completely locked up. The OS called the spin-whateveritis app to kick in and capture a dump, and Excel itself fired off a send-crash-to-MS dialog, so I did that too. Then I had to force-quit the app. Geeze, MS - I blame sloppy QC for this one.
 
I've have a similar problem but with Apple Mail under El Capitan connecting to an Outlook server. Since the upgrade to El Capitan, I haven't been able to connect to the Outlook Server.

So I wonder if this has something to do with the way El Capitan connects to Outlook servers that's used by both Apple Mail and MS Outlook.
 
Microsoft hasn't exactly knocked itself out in the past trying to remove bugs in Office.

Moreover, they are using the same type of spellchecker they started using in the 1980's - namely a spellchecker that is not context-dependent and check only a word at a time (so 'tot he' is fine when 'to the' is the desired spelling).
Well..these guys don't know any vocabularies.
 
1) That maybe true but how many of these bugs are the result of Microsoft's elaborate abstraction for the sake of portability resulting in a tower of cards that can fall over at the slightest change?

2) Office 2016 was released more than a 'few weeks ago' - it has been available on Office 365 subscribers like myself since 9 July 2016 and more importantly they've had 4 years to not only update the code but also move it to 64bit as well.

I might have some sympathy for Microsoft if they were some small organisation trying to keep up with the changes Apple introduces but Microsoft isn't some rinky-dinky organisation consisting of two men and a dog but rather a multibillion dollar company that has little in the way of excuses as to why OS X continues to remain the neglected step child of the Office portfolio of supported platforms.

Edit: I'm lucky in that my requirements of Office isn't that high with me primarily using Pages/Numbers/Keynote. The fact that Office is the 'best of the worst' shouldn't mean that Microsoft sits back satisfied with mediocrity and instead should be aspiring towards 100% feature parity between the Windows and Mac version rather than the Mac version being the cut down half finished version for many years.
Lol I'm sure a fix will be out in a week or two so chill. Not sure why someone who uses Keynote/numbers would care enough to make a super long post. Guess it's a apple forum so Microsoft bashing is expected.

It should also be said that people working in critical environments aren't going to update day 1. Most would wait till 10.11.1 or even later so shame on those who want to be on the bleeding edge but can't handle it.
 
I always recommend people do not upgrade thier OS until about a month after the release. Be it apple or Microsoft , just released software is buggy. Microsoft will patch this shortly though.
 
1) That maybe true but how many of these bugs are the result of Microsoft's elaborate abstraction for the sake of portability resulting in a tower of cards that can fall over at the slightest change?

2) Office 2016 was released more than a 'few weeks ago' - it has been available on Office 365 subscribers like myself since 9 July 2016 and more importantly they've had 4 years to not only update the code but also move it to 64bit as well.

I might have some sympathy for Microsoft if they were some small organisation trying to keep up with the changes Apple introduces but Microsoft isn't some rinky-dinky organisation consisting of two men and a dog but rather a multibillion dollar company that has little in the way of excuses as to why OS X continues to remain the neglected step child of the Office portfolio of supported platforms.

Edit: I'm lucky in that my requirements of Office isn't that high with me primarily using Pages/Numbers/Keynote. The fact that Office is the 'best of the worst' shouldn't mean that Microsoft sits back satisfied with mediocrity and instead should be aspiring towards 100% feature parity between the Windows and Mac version rather than the Mac version being the cut down half finished version for many years.

Stick to pages/numbers/keynote. I suspect no matter what Microsoft does with office, you will have an issue with it. FYI, for a non Rinky-dinky organisation pages/numbers/keynote suck coming from one of the richest companies on the planet.
 
  • Like
Reactions: btrach144



Since OS X El Capitan was released to the public last week, Microsoft Office users have noticed some serious bugs when attempting to use the software. MacRumors has received multiple emails from people having issues with Office 2016, and there are several threads about the problem on our forums.

Word, Excel, Outlook, and PowerPoint are crashing for many Microsoft users who have installed Office 2016, and Office 2011 users are also noticing problems with Outlook.

officeformac2016-800x159.jpg

Microsoft is aware of the problems with its software and has been responding to customer complaints. In a thread on the Microsoft forums, Microsoft Program Manager Faisal Jeelani said the company is working with Apple to resolve the issues, but said there is no timeline for a fix. Microsoft also gave Computerworld a similar statement:Customers who are running Office 2016 are running into a wide variety of problems. Some are seeing only occasional crashes with the software, while others are unable to open any Office 2016 apps at all. Many who use Outlook for email are unable to access their inboxes, and this particular issue affects both Office 2016 and Office 2011.Microsoft's first support replies came shortly after OS X El Capitan was released, which means the company has been working on a fix for several days now, but it is not clear when a patch might be released. Many customers on the Microsoft forums are growing angry with the company because Microsoft had several months to work out crashing issues ahead of OS X El Capitan's release. Crashes and Office 2016 problems were first reported during the beta testing period but remain unresolved.

Update: A Microsoft spokesperson has told MacRumors that a fix is in the works.

Article Link: Microsoft Working on Fix for Office Bugs in OS X El Capitan
It's not just 2016. Outlook 2011 freezes and will not download data from an MS Exchange server. This problem is more than a little annoying for those people forced to use MS Outlook because of a corporate reliance on MS software. I made the mistake of updating to OS X el Capitan and now the only fix Microsoft can offer me is to remove el Capitan and return to Yosemite which is very risky and time consuming. What planet are these people at Microsoft on? They had time to debug their major Office software. Now the only way I can work with my huge mail database is through the notoriously slow web Outlook, until MS in its esteemed wisdom issues a fix. There are not as many Outlook 2016 users as there are 2011 users so imagine how many people are affected and the MS team seems focused on 2016 based on the the three techs I talked to at MS today. A fix is in the works is not the answer. A fix, at least for the large number of Outlook 2011 users should be available immediately, not just "in the works". A fix is needed now, not in a week or a month.
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.