In the world of enterprise deployment, few things are as simultaneously mundane and maddening as language packs. You have a global workforce. Half your users need Croatian spellcheck, a quarter need Thai UI elements, and a handful in IT insist on working in Klingon (okay, maybe not that last one). Microsoft provides a solution: the Language Interface Pack (LIP). But for anyone who has tried to deploy LIPs at scale using traditional methods, you’ve hit a wall. Enter the shadowy, controversial, and surprisingly necessary world of the repack.
This isn't a post about piracy. This is a post about the broken logic of volume licensing deployment and the technical archaeology required to fix it. Let’s dive into what an Office 2016 LIP repack actually is, why it exists, and whether you should be terrified or thrilled by it.
Disclaimer: This guide is for educational purposes. Always back up your system and verify the legality of this action in your jurisdiction.
If you have decided to proceed, here is the standard protocol for installing a typical Office 2016 Language Interface Pack Repack (distributed as a .exe or .msi).
Let’s assume you want to add Catalan to your English Office 2016 ProPlus without using a repack.
Step 1: Verify your Office build. Run winver and check File > Account > About Excel. You need build 16.0.4266.1001 or later.
Step 2: Download the official Office Deployment Tool (ODT) from Microsoft.
Step 3: Create a folder C:\OfficeLIP and extract ODT there. office 2016 language interface pack repack
Step 4: Create lip.xml:
<Configuration>
<Add OfficeClientEdition="64" Channel="PerpetualVL2016">
<Product ID="ProPlus2019Volume" PIDKEY="XXXXX-XXXXX-XXXXX-XXXXX-XXXXX">
<Language ID="en-us" />
<Language ID="ca-es" />
</Product>
</Add>
</Configuration>
Step 5: Run as Admin:
setup.exe /configure lip.xml
Step 6: Wait 5-10 minutes. Office will download only the necessary CABs for Catalan (approx 85MB). No repack required.
Result: Clean, signed, updatable, and uninstallable.
A Language Interface Pack is a localized software skin that translates the text of the Office UI (menus, dialog boxes, and help files) into a specific language.
In today’s globalized work environment, the ability to switch your software’s language on the fly is not a luxury—it is a necessity. Whether you are an expat working in a foreign country, a student learning a new language, or an IT administrator managing a multilingual team, Microsoft Office’s native language support is often frustratingly limited.
Enter the Office 2016 Language Interface Pack (LIP), and its lesser-known, community-driven cousin: the Office 2016 Language Interface Pack Repack. The Unspoken Truth About the Office 2016 Language
While official Microsoft LIPs allow you to change the user interface (menus, ribbons, dialog boxes) to a different language, they come with significant drawbacks: regional restrictions, complex deployment, and the requirement for a specific base Office version. This is where the "Repack" version has become a controversial yet popular solution.
In this article, we will dissect everything you need to know about the Office 2016 Language Interface Pack Repack—its technical structure, legal implications, step-by-step installation guide, and whether it is the right choice for your organization or personal use.
A Language Interface Pack (LIP) is a high-quality translation of the Office user interface. Unlike full Language Packs (which change every single bit of text, including Help files and right-click menus), LIPs are lighter. They translate the most common elements of the ribbon, dialog boxes, and commands.
Key characteristics of the official LIP:
Let’s get technical for a moment. When you download x64-lip-croatian.exe from an unofficial source and run it with /?, you won’t get help. But if you open it with 7-Zip, you’ll see the truth.
A typical LIP repack contains:
Office2016_LIP_Croatian_x64.msi
setup.cmd
lip_config.xml
The magic is in setup.cmd:
@echo off REM Check for Office 2016 x64 base install reg query "HKLM\SOFTWARE\Microsoft\Office\16.0\Common\InstallRoot" /v Path | find "x64" || exit /b 1REM Silent install of the repacked MSI msiexec /i "Office2016_LIP_Croatian_x64.msi" /qn /norestart ADDLOCAL=ALL
REM Set Croatian as default UI for new users reg add "HKCU\Software\Microsoft\Office\16.0\Common\LanguageResources" /v UILanguage /t REG_SZ /d 1050 /f
REM Trigger Office Language Preference update "%ProgramFiles%\Microsoft Office\root\Office16\WINWORD.EXE" /regserver
This is elegant. It’s also completely unsupported by Microsoft. If this script fails, you are on your own. No Microsoft Support ticket will help you. Your VAR will stare at you blankly.
In the software world, a "repack" is a modified version of an original installer. For the Office 2016 LIP, a repack typically means: