"UNC paths are not supported. Defaulting to Windows directory." after launching the Custom Install deployment .bat file using UNC paths

July 9, 2025 Ken Williams

"UNC paths are not supported. Defaulting to Windows directory." after launching the Custom Install deployment .bat file using UNC paths

Issue:

After creating a Custom Install deployment using UNC paths, when you start the .bat file to install the program, the Command Prompt window shows:

Solution:

Per Autodesk:

Typically, the warning does not prevent the installation from running. Should the install still not run, try these steps:

  1. Download and install ODIS on the target machine(s) from this link.
  2. Edit your batch file so the local Installer.exe is used:
"C:\Program Files\Autodesk\AdODIS\V1\Installer.exe" -i deploy --offline_mode --ui_mode basic -o "...\image\Collection.xml"
Note: Adjust the path to Collection.xml to fit your environment.
  1. Launch the bat file to start the installation. for editing the .bat file to work if it has been moved from another location. 

What I have found:

A. Add @pushd %~dp0 at the top of the script and @popd at the end.  

Example:

chcp 65001

@pushd %~dp0

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

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

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

rem ========== Uninstall Autodesk Civil 3D 2024 - English
rem "\\W10HyperV\Autodesk\C3D2024\image\Installer.exe" -i uninstall -q --manifest "\\W10HyperV\Autodesk\C3D2024\image\CIV3D_2024_en-US\setup.xml" --extension_manifest "\\W10HyperV\Autodesk\C3D2024\image\CIV3D_2024_en-US\setup_ext.xml"

@popd




Notes:

@pushd %~dp0 will change your working directory to the script's location in the new mapped drive.

@popd at the end, to clean up the mapped drive.

About the Author

Ken Williams

Installation Technical Support Specialist<br><br>Ken Williams has over 20 years of experience as a systems administrator helping organizations with installation, configuration, and maintenance. At IMAGINiT, Ken puts his knowledge of Microsoft, SQL, servers, and Autodesk to work ensuring clients are able to stay up-and-running, install their software easily, and maintain their solutions.

Follow on Linkedin More Content by Ken Williams

No Previous Articles

Next Article
Autodesk download and installation options

×

Get Tips Delivered.

Subscribe to Email Updates.

First Name
Last Name
Country
Thank you!
Error - something went wrong!