Autodata 345 The Hardware Information Does Not Match With Your Dongle Top -
Danger: Incorrect registry editing can break Windows. Back up your registry first.
Error 345 sometimes persists because of leftover registry entries. Delete them:
Windows may cut power to the dongle, corrupting the handshake.
If you moved from PC-A to PC-B and kept the same dongle, the hardware mismatch is permanent. You must deactivate the old fingerprint.
For legitimate license holders:
1. Revert to original hardware
If you still have the old hardware (especially the motherboard/drive), put it back in the original PC. The software should work again.
2. Contact AutoData support for license transfer
Most dongle-protected software allows license transfers, often requiring:
3. Reinstall/update dongle drivers
4. Try the dongle on a different USB port
Rarely, USB 3.0 vs 2.0 port changes can affect hardware ID enumeration. Try USB 2.0 ports.
5. Restore from a system image
If you have a full system backup from before the hardware change, restore it to the same machine (if the hardware change was minor like RAM or GPU, it might still work).
Once you fix the "hardware information does not match with your dongle top" error, take these steps to avoid it happening again: Danger: Incorrect registry editing can break Windows
If you want, I can draft a concise email to vendor support with the details filled in—tell me the exact dongle IDs, software/firmware versions, and OS.
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. but you need specialized tools (MProg
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. HASP HL Dumper
Restart and re-run the install.bat from your Autodata folder. Preventing the Error in the Future To stop this from happening again:
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.
Q: Does the "top" in the error mean my dongle is physically damaged? A: Unlikely. "Top" refers to a software-layer certificate or handshake token. Physical damage usually results in "dongle not found" or "USB device not recognized."
Q: Can I move my Autodata 345 dongle to a new computer? A: Officially, yes – but only if you deactivate it on the old system first. In practice, version 3.45 lacks an official transfer wizard. Moving it to different hardware will almost always trigger the 345 error.
Q: Will reinstalling Windows fix the error? A: No – reinstalling Windows will make it worse because you lose the original registry fingerprint. Only reinstall Windows if you have an exact system image backup that includes the working Autodata installation.
Q: Is there a way to edit the dongle’s internal data to match new hardware? A: Yes, but you need specialized tools (MProg, HASP HL Dumper, or Sentinel LDK tools). This is illegal in most jurisdictions and voids any remaining license rights.
The "hardware information does not match with your dongle" error typically indicates that there's a discrepancy between the expected hardware configuration (or a specific identifier related to the hardware) and what the dongle is reporting or is associated with. This could be due to: