Skip to main content

Hardware Information Does Not Match With Your Dongle Best — Autodata 345 The

Post: Autodata 345 — Hardware Info Mismatch with Dongle

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

Symptoms:

If "Test Mode" is not visible in the bottom-right corner of your desktop, the emulator will likely fail with a dongle error. Regional Settings Some versions of Autodata 3.45 require your Regional Settings to be set to English (United States) to avoid runtime and licensing errors. Post: Autodata 345 — Hardware Info Mismatch with

Device Manager Check: Open Device Manager. Under "System Devices," you should see "AuDaS0 Virtual Device" or "Sentinel USB Stub".

Are you running this on Windows 10 or Windows 11, and have you already tried disabling your antivirus to see if it restores the connection? Under "System Devices," you should see "AuDaS0 Virtual

Driver Issues: The dongle might require specific drivers to function properly, and if those drivers are outdated, missing, or incorrectly installed, it could lead to communication issues between the dongle, the software, and your computer's operating system.

...the software sees a “new” computer and refuses to work. Under "System Devices

You should see SafeNet Sentinel Hardware Key. If it has a yellow exclamation mark or is missing, you must reinstall the Sentinel Protection Installer.

Autodata Installation Guide for Windows | PDF | Computing - Scribd