Installer Package Adjustment for Foxit PDF Editor (Windows) – v2026.2.0 and v14.0.7 or Later

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+ language files instead.

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

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, or you are performing a fresh installation.

Foxit provides three installer formats for Foxit PDF Editor for Windows:

• Use the ZIP package when you require an MSI and its deployment resources
• Use the EXE package for a selfcontained installation
• Use the MSP patch to apply an incremental update to an installed baseline version

See the ZIP, EXE, and MSP sections below for details.

ZIP

ZIP installer package is 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.

ZIP package name example: FoxitPDFEditor20262_L10N_x64.zip

After extracting the ZIP file, users will find:

Note: For subsequent releases (e.g., v2026.2.1), the MSI Package installer name will reflect the version (e.g., FoxitPDFEditor202621.msi).

• Individual users: The ZIP package no longer includes Setup.exe and setup.ini. Please double click the extracted MSI file directly to launch the installation. The full set of extracted files — the MSI, all CAB files, and the Transforms folder — must remain together in the same directory. Missing any asset will cause installation failures.

• Enterprise admins: All extracted files must reside within a single directory. Deployment operations still target the MSI file,See the Custom Installation Deployment Guide for detailed deployment instructions.Any MST file generated via the Foxit Customization Wizard (FCW) must be placed in the same directory alongside the MSI and all other extracted CAB/Transforms assets prior to deployment.Missing any file in the set will cause installation to fail.

An EXE installer package is a Microsoft-standard self-contained installation bundle that encapsulates all required installation files; its contents cannot be extracted separately.

• Individual users: Double-click the EXE directly to complete the installation.
• Enterprise admins: Deploy the EXE package in enterprise environments as-is.
• Key change: Starting with v2026.2.0 and v14.0.7, the EXE installer no longer supports command-line extraction (the /extract switch has been removed). The EXE is now a fully self-contained bundle and cannot be used to retrieve the MSI, MSP, or MST. The ZIP package is the only supported way to obtain a MSI for enterprise deployment.

An incremental patch package, compliant with Microsoft MSP standards, used to apply minor version upgrades on top of an already-installed baseline version. Each MSP remains a single file in v2026.2.0 and later — the ZIP/multi-CAB restructuring applies to the full installer package, not to patches.

• Individual users: Double-click on the MSP file to apply incremental version updates.
• Enterprise admins: Deploy MSPs enterprise-wide to roll out version upgrades within the same baseline version series.See the Custom Installation Deployment Guide for detailed deployment instructions.
• Note: MSP patches only work within the same baseline series. They cannot upgrade a system across baseline versions (for example, a v2026.2.0-baseline install cannot be moved to a future new baseline via MSP) — a new baseline requires the new ZIP package.

A: Starting with v2026.2.0 and all subsequent releases (subscription), and v14.0.7 and later (perpetual). All versions before v2026.2.0 and v14.0.7 remain unchanged.

A: No. Starting with v2026.2.0 and v14.0.7, 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.

A: No. Starting with v2026.2.0 and v14.0.7, the EXE no longer supports command-line extraction. The ZIP package is the only supported way to obtain an MSI for deployment.

A: MSP patches only support minor and maintenance upgrades within the same baseline version series. They cannot be used to upgrade across different baseline versions. This applies to both subscription and perpetual license products.

A: 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 using msiexec.

A: 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.

A: 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.

Custom Installation Deployment Guide for Enterprise Users

How to Patch Update Foxit PDF Editor/Reader for Windows