Update & Upgrade Problems

Fix Office 2021 LTSC Offline Download Getting the Wrong Build

Steve KSteve K Oct 12, 2026 870 views

Question details

The user is attempting to perform an offline deployment download for Office 2021 LTSC using a volume license but the deployment tool retrieves an older build instead of the latest one.

Fix Office 2021 LTSC Offline Download Getting the Wrong Build
Product
Microsoft Office 2021 LTSC
Device & OS
not provided
Scenario
Using the Office Deployment Tool command to download the volume license offline installation files for an enterprise environment.
Observed behavior
The offline download command retrieves an older build version (e.g., 14332.20099) rather than the expected latest version (e.g., 14332.20604).
Before you start

Verify that you are using the most recent version of the Office Deployment Tool (ODT) and ensure that your target directory for the offline files is completely empty before retrying the download.

Solution 1Recommended

Retry the Download as Microsoft Has Resolved the Backend Issue

This issue was identified as a Microsoft deployment service problem that delivered incorrect manifest files. Microsoft has since corrected the server-side configuration.

Because this was an external service issue with Microsoft's content delivery network, the primary solution is to simply run the download command again now that the correct build (14332.20604 or later) has been restored to the volume license channel.

1
Open Command Prompt as Administrator

Click the Start menu, type 'cmd', right-click on 'Command Prompt', and select 'Run as administrator'.

2
Navigate to your deployment folder

Use the 'cd' command to change directories to the folder where your setup.exe and configuration XML file are located (e.g., cd C:\ODT).

3
Execute the offline download command

Type 'setup.exe /download configuration.xml' (replace 'configuration.xml' with your actual filename) and press Enter to initiate the download.

4
Verify the downloaded build

Once the command completes, navigate to the downloaded 'Office\Data' folder and check the version number of the newly downloaded CAB files to ensure it matches the expected build.

Retry the Download as Microsoft Has Resolved the Backend Issue
Issue Resolved: Microsoft has confirmed that the LTSC 2021 deployment service is now pointing to the correct, updated build version.
Free Microsoft Office alternative

Simplify Your Enterprise Deployments with WPS Office

Struggling with complex XML configurations, deployment tools, and server-side update glitches in Microsoft Office? WPS Office offers a powerful, lightweight alternative that simplifies mass deployments while maintaining complete compatibility with standard Office formats.

  1. 1. Download the standard installer: Visit the official WPS website and download the offline installation package directly without needing command-line tools.
  2. 2. Deploy easily across your network: Distribute the lightweight setup file to user machines via your preferred endpoint management software.
  3. 3. Install and start working: Run the installer. Users can immediately start opening and editing existing Microsoft Office documents.
Extremely lightweight offline installer that bypasses complex command-line deployment toolsSeamless format compatibility with Microsoft Word, Excel, and PowerPoint filesFamiliar user interface requiring zero training for employees migrating from OfficeSignificantly reduces local storage and enterprise bandwidth requirements
microsoft office alternative - wps office

Frequently Asked Questions

How do I check which Office build the deployment tool actually downloaded?

Navigate to the folder where you ran the download command. Open the 'Office' folder, then the 'Data' folder. You will see a folder named with a build number (for example, '16.0.14332.20604'). This indicates the exact build version that was downloaded.

Why did Microsoft deliver the wrong build for Office 2021 LTSC?

Occasionally, Microsoft updates the Office Content Delivery Network (CDN) manifests, and caching issues or staggered server rollouts can result in the deployment service temporarily offering a previous build instead of the newest one.

Can I install an older build if the newest one is causing issues?

Yes. You can modify your configuration.xml file by adding the Version attribute to the <Add> tag (e.g., Version="16.0.14332.20099") to force the Office Deployment Tool to download and install a specific, older build.