Cannot deploy Office LTSC Professional Plus 2024

Hello @Dominic

Welcome to Microsoft Q&A!

Thank you for your patience, and taking the time to elaborate on your concerns.

This scenario combines Office LTSC 2024 deployment via ODT, enforced WDAC policies, and a corrupted Visio install that blocks setup with error codes 30198‑25 / 0‑2039.

Recommended Resolution Path.

1. WDAC Enforcement

Confirm that setup.exe from the Office Deployment Tool is Microsoft‑signed and permitted by your WDAC policy.

If blocked, add a rule to allow the ODT binary or run from an elevated prompt in a trusted path.

2. Remove Corrupted Visio Remnants

Use the Microsoft Support and Recovery Assistant (SaRA) or the Office Scrub Tool to forcibly remove Visio remnants.

Alternatively, create an uninstall XML and run:

cmd

setup.exe /uninstall VisioPro /config uninstall.xml

This strips out corrupted Visio components before installing LTSC 2024.

3. Clean Install Configuration

Place your office2024.xml (or configuration.xml) in the same folder as setup.exe.

Example minimal config for LTSC 2024:

xml

<Configuration>
  <Add OfficeClientEdition="64" Channel="PerpetualVL2024">
    <Product ID="ProPlus2024Volume">
      <Language ID="en-us" />
    </Product>
  </Add>
  <Display Level="None" AcceptEULA="TRUE" />
  <Property Name="AUTOACTIVATE" Value="1" />
</Configuration>

Run elevated:

cmd

setup.exe /configure office2024.xml

4. Error Code Meaning

• 30198‑25 → corrupted existing Office/Visio install.
• 0‑2039 → blocked/unable to access required files (often WDAC or permissions).
• Both are resolved by cleaning old remnants and ensuring ODT is permitted.

In Summary: To unblock ODT and deploy Office LTSC 2024:

• Permit setup.exe under WDAC.

Use SaRA or an uninstall XML to scrub corrupted Visio remnants.

Run ODT elevated with a clean office2024.xml.

Error codes confirm corruption + WDAC enforcement, not a licensing issue.

I hope this helps to better understand the diagnostic options available and the risks involved.

If this information was helpful, please click Accept Answer.

Thank you for choosing Microsoft Q&A.