Skip to content

Instantly share code, notes, and snippets.

  • Star 0 You must be signed in to star a gist
  • Fork 0 You must be signed in to fork a gist
Star You must be signed in to star a gist
What would you like to do?
crack activate office on mac with license file

Activate MS Office 2019/2016 for macOS - Microsoft_Office_2019_VL_Serializer

Office 2019 above


Note that Office2019 DO NOT support activate via simple copy/paste plist license file which is the simplest way to activate Office 2016. Fortunately, you can also use the VL Serializer tool, just install Office 2019 and Serializer, then run Serializer to activate.


Activation Step

  1. DO NOT RUN OFFICE APP AFTER INSTALLED, but just install Office 2019 for macOS

    or install via brew:

    brew cask install microsoft-office
  2. manual download and install Microsoft_Office_2019_VL_Serializer.pkg

  3. run Microsoft_Office_2019_VL_Serializer and it will automatic activate Office 2019

  4. open the office app, completed.


If you alaways been asked for 'Sign in' and still requires activation, please try to remove Office license files on a Mac. Here is the official download link for Microsoft_Office_License_Removal tool. (thanks for @lidroider's comment)

The Serializer.pkg in this gist is signature by Microsoft Corporation Official. To check it, you can see details in this comment

Office 2016 16.11 for macOS VL2 license



Activation Step

  1. install Office2016 for mac with Office Suite Install, but DO NOT RUN OFFICE AFTER INSTALLED

    or install via brew:

    # brew cask install microsoft-office  # this point to Office 2019 now
    # install last office 2016 version below
    brew cask install
  2. copy license file to Preferences

    # md5( = a8f1283303838b4d3bd943775e463239
    cp /Library/Preferences/
    # or download it in library by command line
    curl -sSL -o /Library/Preferences/
  3. run the office app, completed.

View raw

(Sorry about that, but we can’t show files that are this big right now.)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment