OS X maverick and installed MS Office for mac

Just got a brand new MBP Retina 13". Used Migration assistant to turn all my data over to my new machine --I did not check software as it indicated 25 hours of transfer time !! Data alone was a couple of hours.

Anyhow, I used the opportunity to buy a new license of the MS Suite (2011 for Mac) to move up from the 2008 version. Finally figured the way to get the download link (link provided in email from MS was wrong, great start).

So I'm trying to install the Suite but I constantly get an error message from the Installer with these very clear and telling details available as a report to send MS.

My hypothesis : there is something, some file somewhere left behind from my data transfer (old computer) that impedes the installation process to go thru. But what and where ??

Anyone has an idea ??

Humble help needed.

Thx

F

PS Yes I did restart. No cahnge. Yes I'm kosher, no need to ask. The license is valid.

You will keep Microsoft Office 2011 after upgrading to Mavericks, as it's compatible. However, before upgrading to OS X Mavericks, you should make a backup of your data with Time Machine and check that your applications are compatible > http://www.roaringapps.com

The only thing you have to make sure is that you have got the most recent Microsoft Office 2011 version

I have ms office 2011 and it does NOT work with Mavericks. I get a message saying you cannot open "Microsoft Exel" or (any of the other ms office) because PowerPC applications are no longer supported.

CappleMid wrote:

I get a message saying you cannot open "Microsoft Exel" or (any of the other ms office) because PowerPC applications are no longer supported.

You have got Office 2004 or older, which is PowerPC. Office 2008 and 2011 are Intel apps

There's an intermittent incompatibility between Mavericks and PowerPoint. Keyboard shortcuts occasionally don't work, e.g., nudging a text box with up/down arrows. The box can be grabbed and moved, but the text itself is not de-selected; the cursor remains blinking in the text. Restarting PPT does not fix the problem. Restarting the computer fixes the problem. Apple and MS need to get together and work this out.

So I had Office 2011 - and after upgrading to mavericks it asked me to re-enter the product key. Problem is - I installed 2008 originally, and upgraded to 2011 online. Now it will not accept the 2008 key I have. So I am once again stuck with 2008 😟 Amongst other probelms mavericks has caused.

That was a problem with the upgrades that required the previous install.

There are rumors of a new Office for Mac coming in March. If you really need Office 2011 now, I would get the Office365 subscription service so you automatically get upgraded with the new version is released.

I took delivery on a new Macbook Pro 15" Retina last week and have been busy! After installing a brand new copy of MS Office for Home & Business 2011, PowerPoint and Word would not work at all. I got a message saying "there is a problem and must shut down". Thankfully, running Microsoft Auto Update, It found two "critical" files to download, and this fixed everything. I believe it was a font problem, but the large download - over 200 mb - fixed it. Just goes to show, new doesn't mean actually new!

My short problem list with my new macbook pro:

iMovie freezes (no one at the mac store is able to rectify, and always seem surprised like it's never happened before)

Any program that opens cannot recognize the screen size (again, folks at the macbook store seem surprised even though they reproduced it in their shop. Unresolved.)

Computer crashes, while running iMovie and iPhoto at the same time.

Related to this post: I just this week (because I was nervous) updated to Maverick... all the MS Office programs freeze. Powerpoint presentations quit in the middle of presentations.

Mac quality is going downhill 😟

sjatkins: Did you get any joy on this? I'm in the same boat -- don't have my keys (in storage) and I've installed Maverick -- to the chagrin of Word. It's little but hugely annoying things, like when I try to organize files by Name or by Date Created, nothing happens. I think it actually makes Safari slower, too....

Office for Mac Home and Business 2011 refused to work at all on my brand new MBpro 15" Retina, even after I installed the two updates for it. It crapped out on me again after the Jan. 25 post above. 2 weeks ago I finally called MS Office customer support and turned over remote control of my computer to a girl in the Phillipines. She was terrific, but it took her about an hour to configure the permissions and organize fonts. All is terrific now. Apparently MS Office was not ready for Mavericks.

Corrupted permissions? After 2 hours of use on a brand new machine? No. The tech support person with MS Office said that the fonts in Mavericks are not compatible with the font file in MS Office. My point was that she knew exactly what to do to fix it, and it's a known problem. This was intended for other people who might read this and need to know about it. Please don't try to play armchair general.

You are very welcome. Its nice to have one's efforts appreciated.

Grant

ps: you told me that's whayt she fixed. I have office on 3 machines with mavericks (2) and 10-.6 (1). There is no need to change anything if they are not currupt.

alcotaz wrote:

I personally would not know if it is a "common problem", but the MS Office customer support person said that it is, and what I am reading in these threads confirms it.

Confirms it? These are troubleshooting forums for people experiencing technical issues. A tiny percentage of Mac & Mavericks users. A very tiny percentage. Yet that confirms a universal issue? Oh, and the word of one MS Support employee? And this from someone who

finally called MS Office customer support and turned over remote control of my computer to a girl in the Phillipines?

Sorry, but there is not much creedence nor technical content in what you are posting.

Cheers

Pete

All of mine worked out of the box.

I'm not trying to argue with you, but to point out that if you want to know what the problem actually was, and if we want to conveny useful info to others, we need to be clear about what happened.

First, very few have such a problem. So it cant be a 10.9 bug, or if it is, it has to do with a very rare condition. Its most likely a corruption of some form.

Second, you told us how it was fixed. Its a common issue, and IMNSHO, general maint on OSX

G

OAO