When reporting Error 345, provide:
Prevention: To avoid future mismatches, always use the dongle on the same computer unless you purchase a transferable license. For critical systems, consider requesting a "floating license" instead of hardware-locked dongles.
This document is for informational purposes. Always refer to official AutoData documentation or your local distributor for license-specific procedures.
The error "the hardware information does not match with your dongle" in Autodata 3.45 typically occurs because the software's license file is tied to a specific hardware ID (UID) that no longer matches your current system. This common issue happens after hardware upgrades, reinstallations, or if the initial license generation was incorrect. How to Fix the Hardware Mismatch Error
To resolve this, you must re-generate a valid license file using your current PC's hardware ID. 1. Retrieve Your Current Hardware ID (UID) Navigate to your Autodata installation or "Keygen" folder.
Open the folder matching your system type: GetUid-x86 (for 32-bit) or GetUid-x64 (for 64-bit).
Right-click the GetUid executable and select Run as Administrator.
Note your code: A window will appear showing an 8-digit (32-bit) or 10-digit (64-bit) code. This is your unique UID.
Tip: If the code is 6400000000, restart your PC and try again, as this is an invalid ID. 2. Generate a New License File
Find the tool named License_builder.exe or a similar .bat file (often called License example.bat) in your "Keygen" folder.
If using a .bat file, right-click it and select Edit. Replace the existing ID with your new UID and save.
Run the file to generate a new registry file (e.g., license_Autodata.reg). 3. Register and Restart the Emulator When reporting Error 345, provide:
Double-click the newly generated .reg file and click Yes to import the settings into your Windows registry. Restart your computer.
Open the Emulator (often found in C:\ADCDA2\ or through the start menu under "nodongle.biz") and ensure it is running with a "green light" or active status. Troubleshooting Tips Creating Autodata License Guide | PDF | Computers - Scribd
Troubleshooting Autodata 3.45: "The hardware information does not match with your dongle"
If you’re a mechanic or a DIY enthusiast, Autodata 3.45 is a staple in your digital toolbox. However, few things are as frustrating as firing up the software only to be met with the dreaded error: "The hardware information does not match with your dongle."
This error typically triggers a "Protection Error" (often code 0x15), effectively locking you out of the diagnostic data you need. Why is this error happening?
Autodata 3.45 uses a virtual "dongle" (an emulator) to verify the software license. This error appears when the software detects a discrepancy between the unique hardware ID (HWID) registered during installation and the hardware ID currently being reported by your computer. Common culprits include:
System Changes: You recently updated Windows, changed your motherboard, or added new RAM.
Antivirus Interference: Your security software has "quarantined" or deleted the emulator files (like ndas.sys or sentinel.sys).
Registry Corruption: The licensing path in the Windows Registry has been broken.
Compatibility Issues: Running the software on Windows 10 or 11 without the proper administrative overrides. Step-by-Step Fixes 1. Disable Antivirus and Re-install the Emulator
Most modern antivirus programs flag the Autodata crack/emulator as a "Trojan" or "Malware." It’s usually a false positive, but it kills the connection to the dongle. Disable Windows Defender or your third-party antivirus. Prevention: To avoid future mismatches, always use the
Go to your Autodata installation folder and locate the "Hardware ID" or "Reg" folder.
Run the emulator setup (often titled install.bat or ndas_inst.exe) as an Administrator. 2. Synchronize the Hardware ID (HWID)
If your hardware has changed, the software is looking for a "fingerprint" that no longer exists.
Run the GetHWID.exe tool (found in the installation package). Copy the code it generates.
Look for a .reg file in your installation folder (often named License.reg or similar). Right-click and edit it.
Ensure the HWID in the registry file matches the one you just generated. Save and run the .reg file to merge it. 3. Adjust User Account Control (UAC)
Autodata 3.45 was designed for older Windows environments. High security settings can block the dongle emulator from communicating with the OS.
Go to Control Panel > User Accounts > Change User Account Control settings. Slide the bar down to "Never Notify." Restart your PC. 4. Clear the Sentinel Drivers Sometimes the "Sentinel" virtual driver gets stuck. Open Device Manager.
Look for "Universal Serial Bus controllers" or "Non-Plug and Play Drivers."
If you see Sentinel USB Key or Virtual USB MultiKey with a yellow warning triangle, right-click and uninstall it.
Restart and re-run the install.bat from your Autodata folder. Preventing the Error in the Future To stop this from happening again: This document is for informational purposes
Exclusions: Add your Autodata folder (usually C:\ADCDA2) to your Antivirus Exclusions/Whitelist.
Run as Admin: Always right-click the Autodata icon and select "Run as Administrator."
Static Hardware: Avoid running the software from a USB drive or changing major hardware components while the software is active. A Note on Stability
Autodata 3.45 is a legacy version. If you are running it on Windows 10 or 11 (64-bit), the emulator often struggles with "Driver Signature Enforcement." If the steps above don't work, you may need to restart Windows in "Disable Driver Signature Enforcement" mode to allow the virtual dongle to load correctly.
This error rarely appears out of nowhere. It is almost always triggered by a specific change in your system. Below are the most frequent culprits.
Once you fix the "hardware information does not match with your dongle top" error, take these steps to avoid it happening again:
This is an uncomfortable but common reality. Many workshops use cloned or emulated dongles. If you move a cloned dongle from the original machine it was paired with to another PC, the hash stored inside the clone will not match the new hardware – triggering error 345 immediately.
If you formatted your hard drive, upgraded from Windows 7 to Windows 10, or performed a clean OS installation, the registry entries and driver signatures that link your dongle to Autodata are wiped. The software sees a "new" computer and rejects the dongle.
Before you start: Ensure you have administrator access to your PC. Also, locate the original installation CD or setup files for Autodata 3.45.
Keep an old laptop or desktop running Windows 7 or Windows 10 LTSC strictly for Autodata. Disable Windows updates and disconnect it from the internet.