Silent Install LibreOffice MSI with MST Transform

Deploying LibreOffice silently across multiple Windows systems requires executing the Windows Installer (msiexec.exe) with specific command-line switches. This guide explains how to apply transform files (.mst) to the LibreOffice Windows Installer package (.msi) for a fully unattended installation, detailing the required parameters, syntax, and practical examples.

Silent Installation Command Syntax

To install LibreOffice silently while applying a transform file, use the following command structure in an elevated Command Prompt or deployment script:

msiexec.exe /i "LibreOffice_x.x.x_Win_x64.msi" TRANSFORMS="custom_settings.mst" /qn /norestart

Command Parameter Breakdown

• msiexec.exe: The Windows Installer executable used to interpret and execute MSI installation packages.
• /i "LibreOffice_x.x.x_Win_x64.msi": Specifies the path to the LibreOffice MSI installer package.
• TRANSFORMS="custom_settings.mst": The property used to specify the path to the transform (.mst) file. Multiple transforms can be separated by semicolons (e.g., TRANSFORMS="file1.mst;file2.mst").
• /qn: Sets the user interface level to “No UI,” running the installer completely silently in the background. (Alternatively, /qb can be used for a basic progress bar with no user interaction).
• /norestart: Prevents the system from rebooting automatically after the installation completes.

Complete Example with Logging

When deploying through enterprise tools such as Microsoft Endpoint Configuration Manager (SCCM), Intune, or Group Policy, it is best practice to include verbose logging to troubleshoot potential issues:

msiexec.exe /i "C:\Deploy\LibreOffice_24.2.0_Win_x64.msi" TRANSFORMS="C:\Deploy\LibreOffice_Config.mst" /qn /norestart /l*v "C:\Deploy\Logs\LibreOffice_Install.log"

• /l*v "path\to\log.txt": Generates a detailed verbose log file containing the entire installation process and transform application results.

Execution Requirements

• Administrative Privileges: The command must be run from an elevated Command Prompt or executed under the SYSTEM context via deployment software.
• File Paths: If paths contain spaces, enclose the full path in quotation marks.
• Relative Paths: If the .mst file resides in the same directory as the script and .msi, you can specify just the file name, though absolute paths are recommended for reliability.