If Autodata 345 reports "the hardware information does not match with your dongle", follow these steps to diagnose and fix it:

Yes, sometimes. Counterfeit Autodata dongles (sold on eBay, AliExpress, or Facebook groups for $50–$100) often contain generic HASP chips with cloned data. After a few weeks or months, the dongle’s internal counter or checksum fails, and Error 345 appears permanently.

How to spot a fake:

Genuine Autodata dongles are supplied only through authorized distributors and cost several hundred dollars. If you paid less than $200 for a current version, it is almost certainly counterfeit.


If you have the original installation files and a genuine license.

This is the official method. Autodata includes a license management tool (hidden in the installation folder).

Steps:

  • Reinstall the Sentinel HASP drivers (download the latest HASPUserSetup.exe from SafeNet/Thales).
  • Reboot your PC.
  • Plug in the dongle. Wait for “Driver installing” notification.
  • Re-open Autodata 345. It will detect “New hardware configuration” and ask for your dongle serial number (printed on the dongle sticker) or a license key file provided by Autodata at purchase.
  • If prompted, re-enter the installation key. The software will now re-pair the dongle to the new hardware info.
  • ✅ This works 95% of the time for genuine single-PC licenses.

    Sometimes the error is not a mismatch but a driver failure misreporting as a mismatch.

    Fix:


    Autodata detects virtual environments (VMware, VirtualBox) and often rejects them. If you cloned a hard drive with Autodata installed, both machines will trigger Error 345 because they have duplicate identifiers.


    If the drivers are installed but the error persists, the registry keys linking the software to the dongle may be missing.

    This website uses cookies to improve your experience. We'll assume you're ok with this, but you can opt-out if you wish. Accept Read more

    error: Content is protected !!