VB.NET or C# using the AutoCAD .NET API. These are native 64-bit, faster, and supported in every modern version of AutoCAD (2020–2025). But for keeping legacy equipment or tools running today ? The VBA module is your lifeline.

This module is specifically for 64-bit versions of AutoCAD 2013. It will not work on 32-bit installations of AutoCAD 2013 (if you are still running an older OS) nor on newer versions like 2016 or 2024 without their respective modules.

Historically, VBA (Visual Basic for Applications) was bundled directly with AutoCAD. However, with the release of AutoCAD 2013, Autodesk shifted to a 64-bit only model. Because VBA (originally a 32-bit component) required a massive re-architecture to run in-process with a 64-bit host, Autodesk removed it from the default installation.

Declare PtrSafe Function FindWindow Lib "user32" Alias "FindWindowA" (ByVal lpClassName As String, ByVal lpWindowName As String) As LongPtr Use conditional compilation to maintain a single codebase for both bit-versions:

Right-click the installer and select Run as Administrator . This ensures the registry keys are written correctly for your 64-bit environment.

If you have been clinging to a library of VBA macros written for AutoCAD 2010 or 2012, upgrading to AutoCAD 2013 likely gave you a headache. When Autodesk made the jump to a true 64-bit application architecture with AutoCAD 2013, many users discovered that their VBA routines simply stopped working.

In 32-bit VBA, handles and pointers fit into 32 bits (Long). In 64-bit, they require 64 bits (LongLong or LongPtr).

To support legacy automation, Autodesk released the as a free, standalone download. This module allows 64-bit AutoCAD to load and execute VBA projects ( .dvb files).