Skip to content

Est. 2011·Microsoft Partner ID 7033487·Delivery under 3 min·Support 7 days a week

Your vault is empty.

How-To

Install Office LTSC Professional Plus 2024 with the Office Deployment Tool

6 min read Updated October 5, 2026 Installation Guides

Do it now

Office LTSC Professional Plus 2024 installs with Microsoft’s Office Deployment Tool: one small tool, one settings file. You don’t have to write that file any more – Microsoft’s web tool builds it for you.

  1. Download the Office Deployment Tool and run it. It unpacks setup.exe and a sample configuration.xml into a folder you pick.
  2. Build your settings file at config.office.com: 64-bit, Office LTSC Professional Plus 2024, the update channel, your key under Licensing and activation, then Finish and Export. Prefer Notepad? Copy the ready file under The settings file.
  3. Save it as configuration.xml next to setup.exe.
  4. Open Start, type cmd, right-click Command Prompt, Run as administrator. Go to that folder, for example cd C:\ODT, and run:
Command Prompt, as administrator

setup /configure configuration.xml

Office downloads from Microsoft and installs. With your key in the file, it activates itself.

Open Word and check File > Account. If it shows the product as activated, you’re done.

Your email also has a direct installation image, which installs the apps without the tool. Use this route when you want to choose the applications or the language, when the image won’t run, or when you’re setting up several machines.

Why it works this way

This is a volume product, so there is no consumer installer for it. Microsoft’s tool reads one file that names the product, the language, the architecture and the update channel. For this product two of those are fixed: product ProPlus2024Volume, channel PerpetualVL2024.

Writing that file by hand used to be the only way. Not any more: Microsoft says “we recommend using the Office Customization Tool instead”, which is the config.office.com page in step 2. Same file, built by clicking.

Your key belongs in the file, under PIDKEY. Office then activates during the install and there is nothing to type afterwards. If you would rather not leave a key sitting in a text file, leave it out and type it into Word later.

There is no separate download step in the list above because Microsoft marks it optional: the install command pulls the files from Microsoft as it runs. You only need the download step for offline machines or several PCs from one copy.

“setup is not recognized”

You have this one if the Command Prompt says ‘setup’ is not recognized.

  1. You’re in the wrong folder. cd to the one holding setup.exe.
  2. Run dir and check setup.exe and configuration.xml are both there.
  3. Run the install command again.

The tool exits with an error

You have this one if no Office install screen ever appears.

  1. Check the file says exactly ProPlus2024Volume and PerpetualVL2024. One typo is enough.
  2. Export it again from config.office.com, which spells both for you.
  3. Check the file is named configuration.xml, not configuration.xml.txt.

It fails on a PC that already has Office

You have this one if another Office version is installed and the install ends early.

  1. Architecture has to match the Office already there. Microsoft: mixed architectures aren’t supported, and the install fails.
  2. Installer-based Office from 2007 to 2016 is removed for you by the RemoveMSI line in the file.
  3. Anything newer: uninstall it from Settings first, then run the install again.

Office installed but isn’t activated

You have this one if the apps open with an activation warning.

  1. The key probably wasn’t in the file. In Word: File > Account, Change Product Key, paste the key from your email.
  2. Or put it into PIDKEY and run setup /configure configuration.xml again.
  3. If the key is refused, send us the exact message.

Full reference

The settings file

The shortest file that installs this product in English, 64-bit, with your key. Paste it into Notepad, drop your key in, and save it as configuration.xml next to setup.exe – with “All files” selected, so it doesn’t become a .txt:

configuration.xml

<Configuration>
  <Add OfficeClientEdition="64" Channel="PerpetualVL2024">
    <Product ID="ProPlus2024Volume" PIDKEY="XXXXX-XXXXX-XXXXX-XXXXX-XXXXX">
      <Language ID="en-us" />
    </Product>
  </Add>
  <RemoveMSI />
  <Display Level="Full" AcceptEULA="TRUE" />
</Configuration>

That file holds your key in plain text. Delete it once Office is in, or leave PIDKEY out and type the key into Word instead.

What each line does

Part What it does
OfficeClientEdition 32-bit or 64-bit. One per file, and it must match any Office already installed.
Channel Which servicing channel to install from. This product uses PerpetualVL2024.
Product ID ProPlus2024Volume, Microsoft’s ID for Office LTSC Professional Plus 2024.
PIDKEY Your product key, so the install activates itself.
Language ID The install language. Add a line per extra language.
RemoveMSI Uninstalls installer-based Office, Visio and Project from 2007 to 2016 first.
Display Full shows the normal install screen; None installs silently. AcceptEULA="TRUE" skips the licence dialog.

The two commands

Command What it does
setup /configure configuration.xml Installs Office as the file says, downloading from Microsoft as it goes
setup /download configuration.xml Only downloads the files, for offline installs or several PCs from one copy

For several machines: run the download once into a folder, add SourcePath to the file pointing at it, then run the configure command on each PC.

Microsoft’s own sample

From Microsoft’s Office LTSC 2024 deployment guide, for comparison. It installs from a network share, adds proofing tools and hides the install screen:

Microsoft’s sample

<Configuration>
  <Add OfficeClientEdition="64" Channel="PerpetualVL2024" SourcePath="\\Server\Share">
    <Product ID="ProPlus2024Volume" PIDKEY="#####-#####-#####-#####-#####">
      <Language ID="en-us" />
    </Product>
    <Product ID="ProofingTools">
      <Language ID="de-de" />
      <Language ID="es-es" />
    </Product>
  </Add>
  <RemoveMSI />
  <Display Level="None" AcceptEULA="TRUE" />
</Configuration>

Support dates

Office LTSC 2024 gets updates until 9 October 2029. There is no extended phase, and the apps keep working afterwards.

Questions people ask

Do I have to write the XML myself?

No. config.office.com builds it in the browser, key included. The ready file above is there if you prefer Notepad.

Can I install the 32-bit version?

Yes: pick 32-bit in the web tool, or OfficeClientEdition="32" in the file. It has to match any Office already on the PC.

Will it remove my old Office?

Installer-based Office from 2007 to 2016, yes. Anything newer has to go from Settings first.

Where does the key go if I leave it out of the file?

Into Word, under File > Account and Change Product Key.

Was this article helpful?

Your feedback helps us improve our documentation.

Related articles

How-To Install Windows 10 IoT Enterprise LTSC 2021 and Activate Your Key How-To Install Windows Enterprise LTSC and Activate Your Key How-To Install Windows 11 IoT Enterprise LTSC 2024 and Activate Your Key
← Back to Knowledge Base