Autodesk Self-Extract Error: Autodesk Download Manager has stopped working

We recently got an interesting case when trying to extract a Browser Downloaded file.  The error is noted below:

Autodesk Download Manager has stopped working.

What is odd about this error message is that you are NOT using the Autodesk Download Manager. You are actually extracting the browser downloaded file.

We have been able to confirm that the error happens to all Autodesk software in the following scenario:

1.  Use a browser downloaded file to install our software.

2.  Software must be on a network drive.

\\computer-A\2014\Autodesk\FILENAME_##bit_dlm.sfx.exe

3.  Run the .exe from the network location and extract the file to a different network drive location.

\\computer-B\2014\Autodesk\Deploy

              

3.  Click OK and it will crash.

The workaround is to extract the files locally (C:\Autodesk or D:\Autodesk) or use Windows Remote Desktop to run the extraction and deploy it on the "data" server.

The development team is has been alerted of this issue because this has worked perfectly in the 2013 install framework.

Epilogue

A workaround to this problem is to use mapped drives [S:\Deploy] instead of using a UNC path [\\TOR2UA13809X0\Deploy].

Reference

http://upandready.typepad.com/up_and_ready/2012/11/laws-dont-delete-your-original-deployment-files.html

http://upandready.typepad.com/up_and_ready/2013/08/installing-autodesk-suites-updates-and-saving-drive-space.html

Comments

[Wah]

This it put in layman's terms. As mention above in the Epilogue,the Autodesk self extracts with long path names. When I ran it over a Local Area Network I got files missing in the installation folder as sadly LAN protocols can not deal with long file names, and path names that long in the Autodesk Self Extract causes errors. One easy way is to run the .sfx (Auodsk Self Extract) locally on the same physical disk drive that your making the installation. That is put the .sfx in your local drive C: (for most cases) and click to extract.

[Wah]

Sorry I wasn't clear on my earlier post. Any drive that is Mapped out as a drive letter, even if it is your local folder located on the 'same' physical drive on your PC can cause a problem. For example you may have a Virtual Machine that is Map out to your folder in C:\Downloads as a drive X: and you also got a folder C:\MyAutodeskInstalls which is not mapped out. Extracting from X: to C:\MyAutodeskInstalls will still cause a problem I found. So void any drive letters that are Mapped out.

[aliceten]

You can use Long Path Tool as well, it works good.