Once resolved, take these steps to avoid a repeat:
AutoData stores a local copy of the license binding. Deleting this forces the software to re-read the dongle.
Please advise how to reset or update the hardware ID linked to this dongle, or provide a replacement license/reactivation if the dongle is tied to now-changed hardware.
Contact info:
Name: [Your name]
Company: [Your company/shop name]
Phone: [Your number]
Autodata license/account number: [if any]
Attachment: Screenshot of error message
Error Report: Hardware Information Mismatch with Dongle
Error Message: "The hardware information does not match with your dongle. Please contact Autodata."
Description: The system has detected a mismatch between the hardware information and the dongle. This error typically occurs when the dongle, which is a hardware device used for authentication or licensing purposes, does not match the expected hardware configuration of the system.
Possible Causes:
Recommended Actions:
Troubleshooting Steps:
Contact Information:
The hum of the server room was usually a lullaby to Elias, but today, it sounded like a funeral dirge. On his monitor, a single dialogue box glowed with mocking clarity:
"The hardware information does not match with your dongle. Please contact Autodata."
Elias leaned back, his joints popping. He had been a lead diagnostic tech for fifteen years. He knew every bolt on a Land Rover and every sensor in a Tesla, but this little plastic USB stick—his "dongle"—was the gatekeeper to the wiring diagrams he desperately needed. Without it, the three-ton luxury SUV on Lift 4 was just a very expensive paperweight.
"Still locked out?" a voice called from the bay door. It was Sarah, the shop’s youngest mechanic.
"It’s the digital leash," Elias muttered, gesturing at the screen. "I moved the software to the new workstation this morning. Same hard drive, same OS, but the dongle thinks I’m a thief. It sees a new motherboard and decides the 'hardware information' is a mismatch."
He pulled the dongle out. It was a faded blue plastic nub, scratched from years of being tossed into toolboxes. To the software, this piece of plastic was a soul; to Elias, it was a glitchy ghost.
He dialed the support line. He knew the routine: the long hold music, the verification of the shop's license key, and the inevitable explanation that no, he hadn't sold the software on the black market—he just wanted his computer to talk to his tools.
"It’s about security," the voice on the other end of the line eventually said, sounding as tired as Elias felt. "The license binds to the specific hardware profile of the machine. When you swapped the motherboard, the fingerprint changed."
Elias looked out into the shop. Sarah was waiting. The customer was arriving in two hours. The "security" designed to protect the software was currently the only thing stopping a car from being fixed.
"I have the physical key in my hand," Elias said, his voice dropping to a low, steady growl. "I am in the shop. I am the licensed user. Give me the override code."
Minutes ticked by like hours. Code strings were exchanged. Reboots were performed. Finally, the red bar on the screen turned green. The database hummed to life, unfolding the intricate maps of copper and silicon that lived beneath the car's hood.
Elias grabbed the dongle, patted the side of the monitor like a temperamental horse, and headed back to the floor. "We're in," he called out.
The digital gate had opened, but as he plugged the scanner into the car, Elias couldn't help but wonder why the tools he owned sometimes felt like they were the ones owning him.
If you are seeing this error in real life, I can help you troubleshoot the technical side.
If a driver update or USB port change might fix the mismatch?
What specific information you need ready before calling their support line?
This guide addresses the Autodata error: "The hardware information does not match with your dongle, please contact autodata."
This usually happens when the software's security protocols detect a change in your computer's hardware (like a new hard drive or motherboard) or when the virtual dongle (emulator) driver fails. 🛠️ Quick Fix Steps
Try these basic steps first to reset the connection between the software and the security key: Unplug and Replug
: If using a physical USB dongle, move it to a different USB port. Run as Administrator : Right-click the Autodata shortcut and select "Run as Administrator." This is critical for permission-heavy security software. Check Regional Settings : Ensure your Windows "Region" and "Format" are set to English (United States) English (United Kingdom)
. Incorrect regional formats can cause hardware ID mismatches. ⚙️ Advanced Troubleshooting
If the quick fixes don't work, the issue likely lies with the Sentinel Runtime Dongle Emulator 1. Reinstall Sentinel Runtime Drivers Most Autodata versions use Sentinel/SafeNet security. Device Manager (Win + X > Device Manager). "Universal Serial Bus controllers" If you see "SafeNet Sentinel Hardware Key" with a yellow exclamation mark, right-click and select "Uninstall device"
Unplug the dongle, restart your PC, and then plug it back in to let Windows reinstall the driver. 2. Verify Emulator Status (For "No Dongle" Versions)
If you are using a version that uses an emulator (like Autodata 3.45):
is enabled. You should see "Test Mode" text in the bottom-right corner of your desktop. If it is missing, run the command prompt as Admin and type: bcdedit /set testsigning on , then restart. Navigate to your installation folder and look for the "RegSettings" folder. Run the
file that matches your system (x86 for 32-bit, x64 for 64-bit). 3. Check Hardware ID (UID) Mismatch The software is often locked to a specific generated from your hardware. tool found in your installation folder as Administrator.
Compare this number to the one used during your initial activation.
If they differ (due to a hardware upgrade), you may need to request a new license file from your supplier. ⚠️ Warning on Cracked Versions
If you are using a "cracked" or torrented version of Autodata: This error is a common symptom of a failed crack or an antivirus program deleting the emulator file ( AuDaS0.sys Disable Antivirus
temporarily and reinstall the emulator drivers to see if functionality returns.
Be aware that many online "fixes" for this error contain malware or IP loggers. If you'd like, I can help you: Find the specific Sentinel driver download for your Windows version Walk you through disabling Driver Signature Enforcement Provide the commands to manually register the DLL files version of Autodata are you using? FULL AUTODATA 547 Crack FULL [TechTools] - Facebook
To resolve the "hardware information does not match with your dongle" error in Autodata, you typically need to refresh the Sentinel Protection drivers or clear driver conflicts Troubleshooting Steps
Follow these steps in order to re-sync your hardware with the software: Perform a Clean Reinstall of Drivers Unplug the USB dongle from your computer. Control Panel Uninstall a program and remove the Sentinel Protection Installer your computer. Download and install the latest Sentinel Protection Installer (often version 7.6.6 or higher). Restart again, then plug the dongle back into a different USB port to trigger a fresh hardware detection. Verify Device Recognition Device Manager Universal Serial Bus controllers
, ensure you see "SafeNet USB SuperPro" or "Sentinel USB Key".
If it shows an error (yellow exclamation mark), right-click it and select Update Driver Run as Administrator Right-click the Autodata shortcut and select Run as Administrator Once resolved, take these steps to avoid a
. Sometimes permission issues prevent the software from correctly reading the dongle's hardware ID. Check for System File Corruption Command Prompt as an administrator. sfc /scannow
and press Enter. This repairs system files that might be interfering with the USB communication. When to Contact Autodata If the steps above do not work, it usually indicates a hardware ID mismatch on their server or a faulty dongle . You should contact their official Support Team License ID
displayed in the error message to have your hardware profile reset. To help me give you a more specific fix, could you tell me: of Autodata are you using (e.g., 3.45, Online)? operating system (Windows 10, 11, etc.) is the computer running? dongle worked on this specific PC Sentinel USB Key Not Recognized? Here's How to Fix It
Title: Fixing the “Hardware Information Does Not Match Your Dongle” Error in Autodata
Intro Few things are more frustrating for a busy workshop technician than being locked out of your diagnostic software. You plug in your USB dongle, ready to look up a wiring diagram or service schedule, only to be met with the dreaded red error message:
“The hardware information does not match with your dongle. Please contact Autodata.”
Before you panic or assume your dongle is broken, let’s break down what this error actually means and how to fix it.
What Does This Error Mean? Autodata uses a physical USB dongle (hardware lock) as its primary form of copy protection and licensing. The software on your computer stores a unique “fingerprint” of that specific dongle. When you see the “hardware information does not match” message, it means one of two things:
Common Causes
Step-by-Step Troubleshooting (Before You Call Support)
Try these fixes in order. You may solve the problem in under five minutes.
Step 1: The Simple Swap
Step 2: Reinstall the Dongle Driver
Step 3: Check for Autodata Software Updates
When to Contact Autodata Support If the above steps fail, the error message is correct: you must contact Autodata. Do not try to use third-party “cracks” or patches—they will fail and may introduce malware.
Before you call or email, gather this information:
What Autodata Support Will Likely Do:
Prevention for the Future
Final Verdict The “hardware information does not match” error is almost never a disaster. In 80% of cases, it’s a driver or port issue you can fix yourself. For the remaining 20%, Autodata’s support team has seen this hundreds of times and will get you back online quickly.
Don’t let a software glitch stop your workshop. Try the steps above, and when in doubt, contact Autodata directly.
Have you encountered this error before? What fixed it for you? Let us know in the comments below.
Driver Failure: The Sentinel or HASP drivers are outdated or crashed.
USB Port Issues: The port is not providing enough power or is faulty.
Registry Corruption: Leftover files from a previous installation are conflicting.
Hardware Changes: You recently changed your PC's motherboard or CPU.
Emulation Software: Virtual drives or "crack" files are blocking the dongle signal. 🚀 Steps to Fix the Error 1. Re-seat the Hardware Unplug the dongle. Restart your computer. Plug the dongle into a different USB port (avoid USB hubs). Check if the LED light on the dongle is solid red or green. 2. Update Dongle Drivers Go to the Device Manager.
Look for Universal Serial Bus controllers or Sentinel USB Keys. Right-click and select Update Driver.
Alternatively, download the latest Sentinel HASP LDK Runtime from the official Thales/Gemalto website. 3. Clear Environment Variables
Search for "Edit the system environment variables" in Windows. Click Environment Variables. Check for any old entries related to AUTODATA or SENTINEL.
Delete conflicting paths that point to non-existent folders. 4. Check for Emulators Some antivirus programs flag the dongle as a threat.
Disable your firewall briefly to see if the software launches. Uninstall any "Virtual USB" or "USB over Network" software. 📞 When to Contact Autodata
If the steps above don't work, the dongle itself may be defective or de-authorized. You will need to provide them with: Your Customer ID. The Serial Number printed on the side of the USB dongle.
The specific Version Number of the software you are running.
What version of Autodata are you using? (e.g., 3.45, Online version?)
What Operating System is your computer running? (Windows 10, 11, etc.?)
Did this happen after a Windows update or a hardware change?
I can provide more specific driver links or registry paths based on those details!
The error message "The hardware information does not match with your dongle, please contact Autodata" indicates a security verification failure between the Autodata software and the physical USB license key (dongle). This typically occurs due to corrupted driver settings, incorrect software installation, or hardware identification conflicts. Primary Causes
Driver Conflicts: Windows may automatically assign an incorrect driver if the dongle is plugged in before the software is installed.
Corrupted Registry Settings: Mismatched information between the computer's registry and the dongle's unique hardware ID.
Outdated Firmware: The dongle’s internal software or the Sentinel driver may be too old to communicate with your current version of Autodata.
USB Power Issues: Windows may disable the USB port to save power, causing the software to lose the connection to the dongle during operation. Troubleshooting Steps Restart and Reinstall Drivers:
Disconnect the dongle and uninstall any existing Sentinel drivers.
Restart your computer—this is a critical step for modern Windows versions (7/8/10) to clear temporary hardware states.
Reinstall the software or the specific Sentinel driver before reconnecting the dongle.
Run as Administrator: Always right-click the Autodata shortcut and select "Run as Administrator" to ensure the software has sufficient permissions to read the dongle's hardware ID. Contact info: Name: [Your name] Company: [Your company/shop
Adjust Regional Settings: Some versions of Autodata require your computer's Regional Settings to be set to English (United States) to correctly parse license information.
Check USB Power Management: Open Device Manager, locate your USB Root Hubs, and under "Power Management," uncheck "Allow the computer to turn off this device to save power". Official Support
If these steps do not resolve the issue, you should contact the Autodata Support Team directly to verify your license status or replace a faulty dongle. Dongle Error Codes - GRAFIS Software eGbR
The error "The hardware information does not match with your dongle, please contact Autodata" typically occurs when the unique hardware ID (UID) of your computer does not match the one registered in the software's license or registry. Common Causes
Hardware Changes: Installing Autodata on a new computer or upgrading components (like the motherboard or hard drive) on your current system changes the PC's UID.
Improper Driver Installation: If the Sentinel Runtime or Sentinel Driver is missing or improperly installed, the software cannot communicate with the security dongle.
Incorrect License Generation: If you used a keygen to generate a registry file, using the wrong UID (e.g., an 8-digit code for a 32-bit system on a 64-bit machine) will cause a mismatch. Recommended Troubleshooting Steps Reinstall Sentinel Drivers: Close Autodata and unplug your USB dongle.
Uninstall any existing Sentinel drivers through the Control Panel to ensure a clean slate.
Download and install the latest Sentinel Protection Installer. Ensure you run the installer as an Administrator.
Reconnect the dongle and wait for Windows to recognize the hardware. Verify Hardware ID (UID):
Run the "GetUid" utility (often found in a "Keygen" or installation folder) as an Administrator to retrieve your current computer's UID.
Ensure the UID length matches your operating system: typically 8 digits for 32-bit and 10 digits for 64-bit systems. Check Registry Settings:
If you are using a version that requires a .reg file, ensure you have imported the one specifically generated for your current PC's UID.
Ensure your Regional Settings are set to English (United States), as this is often required for the software to read hardware IDs correctly. Contact Support:
If you have a legitimate subscription and have changed hardware, you must contact Autodata support to have your license reset or transferred to the new hardware ID.
For detailed visual walkthroughs, you can refer to troubleshooting guides for Runtime error 217 or Sentinel Key not found on YouTube or Scribd.
The error message "The hardware information does not match with your dongle please contact autodata"
typically indicates a security mismatch between the Autodata software's license and the physical or virtual hardware it is running on. This error is common in older versions of Autodata (like 3.45) that use physical USB security keys (Sentinel keys) or software emulators to prevent unauthorized copying. Causes of the Hardware Mismatch Unique Hardware Binding
: Many software protection systems bind the license to specific computer components, such as the CPU, hard drive, or motherboard ID. If these components change (e.g., after a hardware upgrade or moving the software to a new PC), the "hardware information" no longer matches the registered ID. Faulty Driver Installation : The software relies on specific drivers, such as the Sentinel Protection Installer
, to communicate with the dongle. If these drivers are corrupted, outdated, or missing, the software cannot verify the dongle's authenticity. Emulator Failures
: For those using virtual dongles, the emulator may fail to start or may be blocked by antivirus software. If the emulator doesn't present the correct "virtual hardware" signature, the software will trigger a mismatch error. Regional Settings
: Incorrect system regional settings (e.g., not set to "English (US)") can sometimes cause verification scripts to fail, leading to misinterpretation of hardware data. Potential Fixes and Troubleshooting Run as Administrator
: Ensure you are running the software and any associated emulators with full administrative privileges. Verify Drivers
: Check your Windows Device Manager for "SafeNet Sentinel Hardware Key" or "AuDaS0 Virtual Device". If these are missing or show an exclamation mark, you may need to reinstall the Sentinel drivers Update Hardware ID (UID)
: If you have moved the software to a new computer, you must typically generate a new Unique ID (UID) from that machine and obtain a matching license registry file. Adjust Regional Settings
: Change your computer's "Regional and Language" settings to English (United States) to resolve potential script errors. Disable Antivirus
: Antivirus programs often flag dongle emulators as "potentially unwanted programs" or malware, blocking them from functioning. Temporarily disabling your security software during installation may resolve the conflict. FULL AUTODATA 547 Crack FULL [TechTools] - Facebook
The error message "The hardware information does not match with your dongle please contact Autodata"
typically indicates a synchronization failure between the Autodata software license and the physical (or virtual) security dongle
. This usually happens due to driver corruption, incorrect installation of the sentinel emulator, or regional system settings blocking the validation. Common Causes Driver Failure
: The "SafeNet Sentinel Hardware Key" driver is either missing or incorrectly installed in your Device Manager. Emulator Mismatch
: If using a virtual dongle (common in version 3.45), the "AuDaS0 Virtual Device" may have an exclamation mark or failed to start. Regional Settings
: The software often requires your PC's regional format to be set specifically to English (United States) to correctly parse dongle data. Missing Registration : Critical DLL files like ChilkatCrypt2.dll might not be registered in the Windows system. Recommended Troubleshooting Steps Check Device Manager
: Verify that "SafeNet Sentinel Hardware Key" appears under USB controllers. If using an emulator, look for "AuDaS0 Virtual Device" under System Devices. Adjust Regional Settings Control Panel > Region and ensure the format is set to English (United States) Run as Administrator
: Ensure you are launching the application with administrative privileges, as it needs high-level access to verify hardware keys. Re-register DLLs
: Open a Command Prompt as Administrator and run the command regsvr32 ChilkatCrypt2.dll
within the Autodata installation directory to fix runtime communication errors. Reinstall Sentinel Drivers
: If the hardware key isn't recognized, download and reinstall the latest Sentinel protection drivers from the official support channels
For further help, you can review detailed setup steps in the Autodata 3.45 Installation Guide for manual driver installation? Autodata Runtime error 217 at 004bb10d Windows 10/7/8/XP Autodata Runtime error 217 at 004bb10d Windows 10/7/8/XP Madman Car Sentinel USB Key Not Recognized? Here's How to Fix It
The error message "The hardware information does not match with your dongle, please contact Autodata" typically occurs when the software detects a mismatch between your PC's hardware ID and the license information tied to your physical or emulated security key. This is a common hurdle for users of legacy versions like Autodata 3.45. Common Causes of the Hardware Mismatch Error
Hardware Changes: Installing new RAM, a different motherboard, or even certain USB devices can change your computer's Unique ID (UID), causing the software to think it's on a different machine.
Driver Failure: The Sentinel Protection Installer or driver for the hardware key may be corrupted, outdated, or not running.
Registry Errors: Incomplete or incorrect license registration in the Windows Registry can prevent the software from validating the dongle.
Permissions: Failing to run the installation or emulator as an Administrator can block the system from reading hardware information correctly. Step-by-Step Troubleshooting Guide 1. Re-register the Sentinel Drivers
Often, the connection between the software and the hardware key is simply broken.
Locate the Sentinel System Driver or Sentinel Protection Installer in your installation folder. Recommended Actions:
Run the installer and choose the Repair or Remove and Reinstall option.
Restart your computer immediately after the installation is complete. 2. Update the Hardware ID (UID)
If you have changed your PC's hardware, you likely need to generate a new license file.
Run the UID utility (often named GetUID.exe or similar) as an Administrator.
Note down the 8-digit (32-bit) or 10-digit (64-bit) code that appears.
Use this code with your license generator to create a new .reg file.
Double-click the new registry file to merge it into your system. 3. Configure Regional Settings
Strangely, Autodata is sensitive to regional and language formats. Go to Control Panel > Region. Set your "Format" to English (United States).
In the "Administrative" tab, ensure the "Language for non-Unicode programs" is also set to English (United States). 4. Disable Conflicting Security
Antivirus: Temporarily disable your antivirus software during the installation and activation process, as it may flag the emulator as a false positive.
UAC: Lower your User Account Control settings to "Never Notify" while troubleshooting. 5. Verify Emulator Status
If you are using an emulator, check the Windows Device Manager.
Look for "Universal Serial Bus controllers" or "Sentinel USB Keys".
If you see a yellow exclamation mark, right-click and select Update Driver, then point it to your installation's driver folder. Final Recommendation
If these steps do not resolve the issue, ensure you are using the correct version for your Operating System (x86 for 32-bit or x64 for 64-bit). For modern Windows 10 or 11 systems, running the software in Compatibility Mode for Windows XP (Service Pack 3) can also bypass legacy hardware verification errors.
This error message typically indicates a discrepancy between the security dongle (the physical USB key) and the licensing data or hardware configuration stored by the Autodata software. It is most common after hardware changes (like a motherboard replacement), software updates, or if the dongle driver has become corrupted. Immediate Troubleshooting Steps
Verify the USB Driver: Ensure the dongle is recognized by your system. Open Device Manager and look for "SafeNet USB SuperPro/UltraPro" or "Sentinel SuperPro." If there is a warning symbol, the driver is likely corrupted. Reinstall Dongle Drivers: Unplug the dongle from your computer.
Uninstall the current driver via the Control Panel or the original installation media.
Download and install the latest Sentinel/SafeNet drivers provided by the software vendor. Restart your computer before plugging the dongle back in.
Check Regional Settings: For some older versions (like Autodata 3.45), ensure your computer's Regional Settings are set to English (United States), as a mismatch here can trigger licensing errors.
Run as Administrator: Right-click the Autodata shortcut and select "Run as administrator." Lack of elevated permissions can prevent the software from correctly reading hardware IDs from the dongle. Why This Happens
Hardware Hash Mismatch: Security dongles often create a "fingerprint" of your computer's hardware. If you have replaced a major component like a motherboard or hard drive, the software may no longer recognize the machine as authorized.
Driver Corruption: Windows updates can sometimes disable or corrupt the legacy drivers required for older USB dongles.
Version Mismatch: The dongle may be programmed for a specific version of Autodata that does not match the version currently installed.
If these steps do not resolve the issue, you must contact Autodata support directly to have your dongle re-synchronized or your license reset, as this is a server-side or hardware-level security lock. What does version mismatch mean [duplicate] - Super User
The error message "the hardware information does not match with your dongle please contact autodata" typically occurs when the Autodata software cannot verify the security key (dongle) against the system's current hardware configuration. This can happen after a hardware upgrade, a Windows update, or if the dongle driver has become corrupted. Recommended Troubleshooting Steps
Update or Reinstall Dongle Drivers: Corrupted drivers are a common cause for this error. You can try uninstalling the existing driver and installing the latest version from the Sentinel Customer Support Portal to refresh the connection.
Check Physical Connections: Ensure the dongle is securely plugged into a working USB port. If possible, try a different port or another computer to rule out hardware failure.
Run System File Checker: Corrupted system files can interfere with how hardware is recognized. Open the Command Prompt as an administrator and run sfc /scannow to repair potential issues.
Disable "Core Isolation" (Memory Integrity): In some cases, Windows security features like Memory Integrity can block the dongle driver from functioning properly. Disabling this feature in Windows Security may resolve the mismatch.
Verify Hardware Changes: If you recently changed your computer's RAM, motherboard, or hard drive, Autodata may perceive it as a different machine. In this scenario, the software's license binding often fails. Official Support
Because this error is tied to licensing and physical security hardware, the most reliable solution is to follow the error's advice and contact the Autodata Support Team. They can verify your dongle’s ID and reset the hardware signature associated with your license.
This message typically appears in automotive diagnostic software like AutoData (or similar programs such as TIS, WIS, or other dealer-level systems). It means the software has detected that the hardware ID (e.g., computer’s motherboard serial, hard drive serial, or network adapter MAC address) does not match the one encrypted in the dongle (USB hardware key).
Here’s a helpful report you can use to understand and resolve the issue:
The error "The hardware information does not match with your dongle. Please contact AutoData" is AutoData’s way of protecting its intellectual property. However, it is a nuisance for honest workshop owners.
Do not attempt to crack or bypass the dongle. Not only is it illegal, but counterfeit dongles often contain malware. AutoData also updates its database monthly – a cracked version will have outdated wiring diagrams and torque specs, putting your customers at risk.
If you have spent more than 2 hours troubleshooting, contact AutoData immediately. Their technical support team has seen this error thousands of times and can typically issue a reset file within one business day.
Have you solved this error in a different way? Share your experience in the comments below to help fellow technicians.
Troubleshooting "Hardware Information Does Not Match with Your Dongle" Error: A Comprehensive Guide
Are you encountering the frustrating error message "The hardware information does not match with your dongle. Please contact Autodata" while trying to use your Autodata software? This issue can be a major roadblock, preventing you from accessing the features and functionalities of your Autodata dongle. In this blog post, we will delve into the possible causes of this error and provide a step-by-step guide on how to troubleshoot and resolve the issue.
What is a Dongle?
Before we dive into the troubleshooting process, let's briefly understand what a dongle is. A dongle is a small hardware device that is used to authenticate and validate software usage. In the case of Autodata, the dongle is a crucial component that ensures the software is being used on an authorized device.
Causes of the "Hardware Information Does Not Match with Your Dongle" Error
The "hardware information does not match with your dongle" error typically occurs when there is a mismatch between the hardware configuration of your computer and the information stored on the dongle. This mismatch can be caused by various factors, including:
Troubleshooting Steps
To resolve the "hardware information does not match with your dongle" error, follow these step-by-step troubleshooting steps:
AutoData now offers web-based subscriptions (AutoData Online) that do not use physical dongles. The error "hardware information does not match" does not exist in the cloud version. The trade-off is you need constant internet access.
| If you are... | Action | |---------------|--------| | A legitimate user with changed PC hardware | Contact AutoData for a free re-activation (may require fee if out of support) | | Using a cracked/pirated dongle | This error is common with clones — no support available | | A shop with multiple PCs | You may need a network dongle or floating license instead |