Batch file Installation (or Uninstall) will not run for an Autodesk products using the New Installation Experience

Autodesk Support

Mar 14, 2025

Products and versions covered

Issue:

Unable to run a batch file (.bat file) for Autodesk products using the New Installation Experience (Does my product or update use the Autodesk New Installation Experience or the Classic Installer?) for installing a deployment.

Issue occurs even when using Microsoft Endpoint Configuration Manager (MECM) (and MECM claims deployment is a success)
- MECM was previously known as System Center Configuration Manager (SCCM).
Launching the batch file itself may work and run without issue or fail.
Deployment run from the batch file freezes part way through installation.

Causes:

Deployment pathing conflict.
Too many products included in the deployment image (too large an image).
Server hosting deployment image issue.
Corrupted deployment.
Deployment image .bat file is still calling out the location that the image was downloaded to and not the image itself for installing on a client PC.
Client PC requires reboot.

Solution:

Deployment pathing conflict

The .bat file can use relative pathing (see the examples in the following Solution "Verify pathways of the .bat file in the deployment image").
Do not edit the Collection.xml, it can cause manifest checks or installs to fail.
Editing the Collection.xml file for the <DeploymentImagePath> will not fix a pathing conflict.
- The <DeploymentImagePath> location is only a reference for the download of the image from manage.autodesk.com and not the actual install path on the client PC.
- The <DeploymentImagePath> does not get referenced during the installation process.
If using MECM, if pointed at the .bat file included with the deployment image, the .bat file can use relative pathing (see example the examples in the following Solution "Verify pathways of the .bat file in the deployment image").
- If MECM is set to point to the installer with hand keyed parameters, it can use relative pathing.

Too many products included when creating the deployment (too large an image)

Create a deployment with fewer products included.
Only include one product for testing and use linked dependencies/scripts to prevent timeouts, bandwidth issues, or other failures.

Server hosting deployment image issue

Low bandwidth, latency, or security software may cause installation to freeze partway through installation. This includes local and cloud servers used for hosting the deployment image.

Move deployment image to a client PC.
Run the .bat file locally after editing it for relative pathing as per the examples in the following Solution "Verify pathways of the .bat file in the deployment image".

Corrupted deployment

Create a deployment package.
Run new deployment package through MECM.
Deploy package to a client PC and verify functionality.

Deployment image .bat file is still calling out the location that the image was downloaded to and not the image itself for installing on a client PC

Common causes are:

Incorrect pathways calling out to the server instead of the image downloaded on the local PC.
Not editing the "rem" callouts from the script.
Using a mapped drive location instead of the local PC or server location.

Verify pathways of the .bat file in the deployment image

Example of a copy of the default .bat file for Vault Professional 2022 deployment that would fail to run when the deployment image is copied over to a local client PC:

chcp 65001

rem ========== Install the deployment with basic UI ==========
"%networklocation%\VaultProfessional2022Deployment\image\Installer.exe" -i deploy --offline_mode --ui_mode basic -o "%networklocation%\VaultProfessional2022Deployment\image\Collection.xml" --installer_version "1.25.0.27"

rem ========== Install the deployment silently ==========
rem "%networklocation%\VaultProfessional2022Deployment\image\Installer.exe" -i deploy --offline_mode -q -o "%networklocation%\VaultProfessional2022Deployment\image\Collection.xml" --installer_version "1.25.0.27"

rem ========== Uninstall the individual product ==========

rem ========== Uninstall Autodesk Vault Professional 2022 (Client) - English
rem "%networklocation%\VaultProfessional2022Deployment\image\Installer.exe" -i uninstall -q --manifest "%networklocation%\VaultProfessional2022Deployment\image\PLC0000004_2022_en-US\setup.xml" --extension_manifest "%networklocation%\VaultProfessional2022Deployment\image\PLC0000004_2022_en-US\setup_ext.xml"

Using the .bat file from above, it is now edited for installing Vault Professional 2022 on a local client PC:

chcp 65001

rem ========== Install the deployment with basic UI ==========
".\image\Installer.exe" -i deploy --offline_mode --ui_mode basic -o ".\image\Collection.xml" --installer_version "1.25.0.27"

rem ========== Install the deployment silently ==========
rem ".\image\Installer.exe" -i deploy --offline_mode -q -o ".\image\Collection.xml" --installer_version "1.25.0.27"

rem ========== Uninstall the individual product ==========

rem ========== Uninstall Autodesk Vault Professional 2022 (Client) - English
rem ".\image\Installer.exe" -i uninstall -q --manifest ".\image\PLC0000004_2022_en-US\setup.xml" --extension_manifest ".\image\PLC0000004_2022_en-US\setup_ext.xml"

Example of an edited uninstall.bat for removing Civil 3D 2022 from a local client PC as per Uninstall deployed products with Configuration Manager:

chcp 65001

rem ========== Install the deployment with basic UI ==========
rem .\image\Installer.exe" -i deploy --offline_mode --ui_mode basic -o .\image\Collection.xml" --installer_version "1.25.0.27"

rem ========== Install the deployment silently ==========
rem .\image\Installer.exe" -i deploy --offline_mode -q -o .\image\Collection.xml" --installer_version "1.25.0.27"

rem ========== Uninstall the individual product ==========

rem ========== Uninstall Autodesk Civil 3D 2022 - English
.\image\Installer.exe -i uninstall -q --manifest .\image\CIV3D_2022_en-US\setup.xml --extension_manifest .\image\CIV3D_2022_en-US\setup_ext.xml

Client PC requires reboot

Adding in the flag "REBOOT=ReallySuppress" can avoid seeing the following error message on the client PC: "An operating system restart is pending" installing Autodesk products ". Example of including this flag in the .bat file for a deployment with basic UI enabled:

Products:

All Desktop Products;

Versions:

2021; 2022; 2025; 2023; 2024;

Was this information helpful?

Need help? Ask the Autodesk Assistant!

The Assistant can help you find answers or contact an agent.

Ask the Assistant

What level of support do you have?

Different subscription plans provide distinct categories of support. Find out the level of support for your plan.

View levels of support