I was installing AutoCAD Civil 3D 2013, along with Infrastructure Modeler, and decided to try hot swapping  my CUI out from 2012. I had already got all my custom setting added, and thought that while I did expect some problems, I would do things properly through the CUI interface later if needed.

As a result of my brilliance 2013 would not load. It would get to a point and stall.

Backups Still Saving Me

Autodesk Civil 3D 2013We have all of our custom settings and apps in a separate global folder that everyone installs from, making new setups a breeze. The exception is at the CUI’s. We have found that with the very little alterations we make, it’s easier to leave that to be installed in its OEM location:

user\App Data\Roaming\Autodesk\C3D2013\enu\support

Any minor alterations are in a separate CUI file stored with the custom files.

One thing we started doing back when we were all coding and modifying AutoCAD heavily, was to back up the support folder, or even the entire enu structure, so that when (not if) we screwed it up, we could go OEM at a moments notice, with no down time.

So I overwrote the entire roaming support structure with the backup, and started AutoCAD.

No joy. I still hung. I overwrote some other folders with more backups, but to no avail, restarts included.

User Cache Fouled

Autodesk Civil 3D 2013What AutoCAD does is cache various files in a local structure called the User Cache, found in the default installation folder (C:\Program Files\Autodesk\….. It reads from there when looking for many files. In the process of making my settings etc, the bad 2012 file must have been updated to the user cache before I closed AutoCAD last. Upon returning, AutoCAD 2013 would not get past it.

On a hunch, I overwrote the entire user cache support structure with the support backup.

AutoCAD Civil 3D 2013 started right up.

I don’t know if erasing the cache would have caused AutoCAD to re-read the OEM file structures, but that would have been my next step.