Microsoft Office 2013 Forum

Has anyone been able to activate the volume license edition of MS Office 2013 in CrossOver 16.0? I've tried the same steps that were successful with MS Office 2010, but after repairing the installation and entering the volume license key the application reports that activation failed. I've verified the registry entries and that the KMS server is available via ping check. Are we restricted to retail or Office 365 subscription editions of MS Office 2013 in the latest release of CrossOver and does anyone have any idea if that will be supported in a future update (along with Visio, Project and Outlook 2013 compatibility)?

I'm having the same problem. The program installs OK on CrossOver 16 and the main components run, but so far, no joy activating the KMS product. As well, I have another Office 2013 version, Professional Pro that I got through a university program. The one involves a link through Microsoft that installs the program, and supposedly has the product key incorporated. Again, it installs and runs OK, but is not activated, and trying to activate it doesn't bring up the key dialogue that I need.

Confirming issue. +1. (tested on v16.2.0)

Side Information:

• same environment, tested Outlook 2010 and KMS activation worked fine

Debian Stretch 9.2, Crossover 16.2.5, Microsoft Office 2013 32 bit VLK. After installation of MSOffice, at Account -> Product Information I introduce the serial number. A message confirm that's OK. After restart, appear a wizard with activation with 2 options: activate over internet or by telephone. Over the internet, the same message "We couldn't contact the server ...", and by telephone it is impossible because "Telephone activation is no longer supported for your product".

I confirm that I have the same problem described above.

Serial number is ok because I used yesterday on MSOffice in Windows.

KMS activation is still not working in 17.0.0.
This is a major pain for the showcase application and I think a 4-star rating for Office 2013/2016 is over-selling.

Any progress on this ? Would WIne 3.3 maybe fix the problem ?

So far if this cannot be used in corporate env , this is not a solution for big companies