Microsoft Office 2011 Mac 64 bit upgrade

Anonymous
2018-04-17T05:17:01+00:00

I purchased Microsoft Office 2011 along with the purchase of my MacBook.  I did an upgrade yesterday only to find that Office 2011 will only run on 32 bit.  The upgrade now requires Microsoft Office to run on 64bit.  I read in many places that Microsoft has no intentions of supporting this upgrade so therefore, I can no longer safely use this software, that I purchased, on my mac.  Microsoft is forcing me to purchase something I have already purchased earlier.  I do not care if there are newer versions of Microsoft Office.  I purchased Office 2011 and Microsoft should still honor that purchase by providing the 64bit upgrade.  I contacted support thru their chat box and was only directed to this site where I can look up or post my own questions.  Really great customer support Microsoft! Thank-you! NOT.  I wish to have a refund or a product key to another Microsoft Office that will run on Mac at 64bit. I'll be holding my breath awaiting even more outstanding customer service.

Microsoft 365 and Office | Install, redeem, activate | For home | Other

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments No comments

132 answers

Sort by: Oldest
  1. Anonymous
    2019-04-16T22:23:03+00:00

    Mac OS Mojave is an upgrade from High Sierra, so apparently High Sierra was 32 bit

    and Mojave is 64 bit.  I can check with Apple, but your message says that my version of Office should work forever.  Thanks for your help, but I'm not certain that is true.

    MacOS has had 64bit support for a long time.

    Support for 64 bit was added on version 10.5 - leopard - 2007. A long time ago but you could run both 32 and 64 bit applications . Mac OS are going to get rid of the 32 bit support soon which is why this is a problem for people like us who bought the 32 bit version of Office.

    Was this answer helpful?

    2 people found this answer helpful.
    0 comments No comments
  2. Jim G 134K Reputation points MVP
    2019-04-17T17:28:22+00:00

    Your license is good forever on your current hardware.

    The real maximum is that your license expires when your hardware wears out or when you ditch your current operating system.

    Was this answer helpful?

    0 comments No comments
  3. Anonymous
    2019-04-26T15:15:02+00:00

    Hi I'm running MacOS Mojave 10.14.4 and Microsoft Office is still working but I always got a lot of warnings.

    Was this answer helpful?

    0 comments No comments
  4. Anonymous
    2019-05-24T17:31:30+00:00

    I understand everything you said in your post.  When I was notified in October 2017 that Office 2011 would no longer be supported, I acquired a copy of Office 2016.

    I had created a complex application in Excel 2011 (lots of macros).  When I started it up in Excel 2016, It would not run properly.  At this point, I don't remember all the things that would not run, but do remember concluding that I could not afford the time or effort to modify the application.  It wasn't just a case of tweaking the code for Excel 2016.  Some commands I had used were no longer valid in 2016 and I would have had to redesign a lot of code.

    I reverted back to Office 2011.

    I knew that, at some point, Apple would no longer allow 32 bit code, and at that point I would have to do whatever was necessary to get my application to run in Excel 2016 (or maybe now Excel 2019).  

    The best thing would be that I will start up my application and everything will work properly.  The worst thing would be that I will have to do a complete redesign of the application.  Having experienced Microsoft upgrades to their products many times in the past, I hope it will be the former, but I am quite confident I will have to do the latter.

    Was this answer helpful?

    0 comments No comments
  5. Jim G 134K Reputation points MVP
    2019-05-25T17:20:07+00:00

    You can post questions about code here in the forum. Be sure to include the version number you're working with and the line or lines of code that are breaking along with the behavior you were hoping for,.

    Was this answer helpful?

    0 comments No comments