Runtime error 217 can also arise from a corrupted AutoData registry hive, usually HKEY_CURRENT_USER\Software\AutoData.
Step 1: Export (backup) the registry key
Step 2: Delete the key
Step 3: Launch AutoData. A clean registry hive will be recreated. You will lose your last view settings or recent VINs, but the error will vanish.
Step 4: If that works, restore your settings by merging the .reg file—but do so only after confirming stability. autodata runtime error 217 at 00580d29 windows 10 full
Data Execution Prevention (DEP) is a Windows security feature that sometimes flags AutoData’s runtime memory access as malicious.
Step 1: Disable DEP for AutoData.exe
Step 2: Adjust Visual Effects
Step 3: Reboot and test.
This is the most common fix for the specific error code 00580D29.
Runtime Error 217 is often caused by a missing or wrong version of borlndmm.dll (Borland memory manager).
If none of the above works, perform a clean reinstallation with specific compatibility flags.
Step 1: Uninstall AutoData completely.
Step 2: Reinstall using Compatibility Wizard
Step 3: Apply the post-install fix script
Create a batch file (AutoDataFix.bat) with the following content:
@echo off
cd "C:\Program Files (x86)\AutoData"
copy %windir%\SysWOW64\borlndmm.dll .
regsvr32 /s rtl60.bpl
regsvr32 /s vcl60.bpl
icacls "C:\ProgramData\AutoData" /grant Everyone:F /T
echo Fix applied. Launch AutoData now.
pause
Run this batch file as Administrator.
Download and install:
Runtime error 217 is a Delphi/Windows runtime exception that occurs when an application fails to initialize properly — commonly due to corrupted program files, missing or mismatched runtime libraries (Delphi RTL/VCL), permission problems, or interference from antivirus/security tools. The address (00580D29) is the memory location where the exception was raised and can help developers locate the failing module, but for end users it mainly confirms the error occurred during program startup.