Custom Installation Deployment Guide for Enterprise Users

Updated for v2026.2 (Windows Editor and Reader)

Last updated: [insert publish date]

Background

From v2025.2.1/v14.0.1 through v2026.1.3/v14.0.6, the EXE was extractable and the ZIP contained MSI + MSP + language files.

Key change: Starting with v2026.2/v14.0.7, the EXE is no longer extractable, and the ZIP now contains MSI + CAB files instead.

Release Tiers (v2026.2 and Later)

Starting with v2026.2, Foxit categorizes releases into two tiers, which determine which installer files are available:

Release tier	Available installers	License type	Version example
Baseline release	ZIP + EXE	Subscription-based or Perpetual-based	v2026.2 (subscription); v14.0.7 (perpetual)
Subsequent release	MSP + ZIP + EXE	Subscription-based or Perpetual-based	v2026.2.1, v2026.3, v2027.x (subscription); v14.0.8, v14.1 (perpetual)

In practice: download the full ZIP package once for a baseline version, then apply lightweight MSP patches for each subsequent release within that same baseline series. You only need a new ZIP when a new baseline is published.

Installer Formats (v2026.2 and Later)ZIP

A compressed archive containing one MSI installer file, multiple CAB archives, and a Transforms folder. The ZIP must be extracted with a decompression tool before installation; all installation operations are then run against the extracted MSI.

FoxitPDFEditor20262_L10N_x64.zip

After extraction, an admin will see something like:

Transforms (folder)
FoxitPDFEditor20262.msi
LangResource.cab
OCRLang.cab
PDFA.cab
PluginModules.cab

Individual users: double-click the extracted MSI to launch installation.

Enterprise admins: all extracted files must reside in a single directory, and deployment still targets the MSI file. Any MST file generated via the Foxit Customization Wizard (FCW) must be placed in that same directory alongside the MSI and CAB/Transforms assets before deploying. Missing any file in the set will cause installation to fail.

EXE

A Microsoft-standard, self-contained installation bundle. Starting with v2026.2, the EXE cannot be extracted — there is no command-line option to retrieve the MSI, MSP, or MST from it. Individual users can double-click the EXE to install; enterprise admins can deploy the EXE as-is, but cannot use it to obtain deployment assets.

MSP

An incremental patch package, compliant with Microsoft MSP standards, used to apply minor version upgrades on top of an already-installed baseline version. Individual users can double-click the MSP to update; enterprise admins can deploy it enterprise-wide. MSP files remain single standalone files under v2026.2 — the ZIP/multi-CAB restructuring applies to the full installer package, not to patches.

Note: MSP patches only work within the same baseline series. They cannot upgrade a system across baseline versions (for example, a v2026.2-baseline install cannot be moved to a future new baseline via MSP) — a new baseline requires the new ZIP package.

Deploying a Baseline Release (ZIP)

This replaces the previous Setup.exe / setup.ini bootstrapper method. Starting with v2026.2, the ZIP package no longer includes Setup.exe or setup.ini — msiexec command-line installation is now the supported path.

Step 1: Extract the ZIP

Download the latest ZIP from the Foxit product catalog and extract it to a single directory. Do not separate the MSI from its CAB files or Transforms folder.

Step 2: Generate a Transform File (MST), if customizing

Use FCW (or another compatible configuration tool) to build customizations:

Import the extracted MSI into FCW
Apply your desired settings
Export the MST file (for example, FoxitPDFEditor.mst)
Save it into the same directory as the MSI, CAB files, and Transforms folder

Step 3: Install via msiexec

Standard silent install with a custom MST:

msiexec /i "FoxitPDFEditor20262.msi" TRANSFORMS="FoxitPDFEditor.mst" /qn

With a language-specific MST from the Transforms folder:

msiexec /i "FoxitPDFEditor20262.msi" TRANSFORMS="FoxitPDFEditor.mst;Transforms\zh.mst" /qn

Without any customization (default settings):

msiexec /i "FoxitPDFEditor20262.msi" /qn

Deploying a Subsequent Release (MSP Patch)

Once a baseline version is installed, subsequent releases within that same baseline series can be delivered either as a ZIP package or an MSP patch file. For existing users, Foxit recommends applying the MSP patch, since it delivers a lightweight incremental update — ZIP packages are intended for fresh installations.

msiexec /p "FoxitPDFEditorUpd20262x.msp" /qn

Check the dedicated patch KB article for the current MSP file name for each released version.

Reusing MST Configurations Across Baseline Upgrades

Existing MST configurations built with FCW are retained when upgrading to v2026.2 or later — admins do not need to recreate them from scratch. If adjustments are needed before deploying a new baseline, open the original MST in FCW and load the MSI extracted from the new version's ZIP package; FCW will import the preserved configuration so it can be edited further and re-exported.

Cross-Package Upgrade Behavior

Users who installed from a ZIP-extracted MSI can upgrade by installing the next release's EXE directly, and users who originally installed via EXE can upgrade using the next release's ZIP-extracted MSI — cross-package upgrades are supported.

The one restriction: you cannot use the EXE and ZIP of the exact same release against each other as an overwrite install. Attempting this will prompt that the same version is already installed.

Deploying v2026.1.3 and Earlier Releases (v2025.2.1–v2026.1.3 / v14.0.1–v14.0.6)

These versions use the previous EXE-based packaging model, where the EXE installer supports command-line extraction and the ZIP is a pre-extracted convenience copy of the same contents.

Step 1: Get the installer files

Either extract the EXE directly, or download the pre-extracted ZIP package (same result, your choice):

FoxitPDFEditor.exe /extract

Step 2: Generate a Transform File (MST), if customizing

Import FoxitPDFEditor.msi into FCW (or another compatible configuration tool)
Apply your desired settings
Export the MST file (for example, FoxitPDFEditor.mst)
Save it into the same folder as the installer files

Step 3: Deploy

You can install either through the Setup.exe bootstrapper or directly via msiexec.

Option A — Setup.exe bootstrapper (recommended for this version range):

Open setup.ini and confirm the CmdLine references your MST, for example:

CmdLine=TRANSFORMS="FoxitPDFEditor.mst" /qn

Then run Setup.exe or deploy the whole folder as-is.

Option B — msiexec command line:

msiexec /i "FoxitPDFEditor.msi" TRANSFORMS="FoxitPDFEditor.mst" /qn

msiexec /p "FoxitPDFEditorUpd202521.msp" /qn

What Changes for Admins Currently on the v2025.2.1–v2026.1.3 Workflow

If your current deployment scripts or SCCM/Intune/FCW packages were built around extracting the EXE with /extract, or around the Setup.exe/setup.ini bootstrapper, both of those will stop working once you move to a v2026.2-or-later baseline release. Before upgrading your deployment pipeline:

Repoint any automation that calls the EXE's /extract switch to instead download and extract the ZIP package.
Remove any reference to Setup.exe or setup.ini in your deployment scripts; replace with the msiexec commands above.
Confirm your existing MST files still apply correctly by testing against the new baseline's extracted MSI (see MST reuse section above).
Update any internal documentation or runbooks that reference the old file layout or bootstrapper flow.

Frequently Asked QuestionsWhich versions does this packaging model apply to?

v2026.2 and all subsequent releases, and v14.0.7 and later for perpetual licenses. Versions before v2026.2/v14.0.7 are unaffected and follow the deployment method described above for v2026.1.3 and earlier releases.

Can I deploy using just the MSI extracted from the ZIP, without the CAB files?

No. The MSI, all CAB files, and the Transforms folder must remain together in the same directory. Missing any of these will cause the installation to fail.

What are the limits on MSP patches?

MSP patches only support minor and maintenance upgrades within the same baseline version series, for both subscription and perpetual licensing. They cannot be used to jump to a new baseline version — that requires the new ZIP package.

How do I apply a custom MST during enterprise deployment?

Generate the MST using FCW against the extracted MSI, place it in the same folder as the MSI, CAB files, and Transforms folder, and run your deployment against the MSI (see the msiexec examples above).

Can I still extract the EXE installer to get the MSI, like in previous versions?

No. Starting with v2026.2, EXE no longer supports command-line extraction. The ZIP package is the only supported way to obtain a standalone MSI for deployment.

If I installed via ZIP, can I upgrade using the next release's EXE, or vice versa?

Yes, cross-package upgrades are supported in both directions. The only unsupported case is using the EXE and ZIP of the exact same release against each other, which will report that the version is already installed.

Do I need to rebuild my MST customizations after upgrading to a new baseline?

No. Existing MST configurations carry over. If you want to adjust them, reopen the original MST in FCW and load the new baseline's extracted MSI to import your prior settings for further editing.

How can we help?

Custom Installation Deployment Guide for Enterprise Users

Provides a guide for enterprise administrators on customizing the installation and deployment of Foxit PDF Editor.