Hasp + error 1009

hasp + error 1009

License key · Bluescreen when starting PC or SYMPHOLIGHT when Dongle is present · HASP driver installation fails with error message · Error 1009: Cannot open e:cue. The HASP 3.25 key is inserted and the LED is lit. Error message when running EdiusLM.exe: "Error 1009: Cannot open HASP HL drivers". HASP Error 33 means that the HASP license manager is not running, or the dongle driver has been blocked or deleted. 1) Check the status of the HASP license.

Hasp + error 1009 - share your

Troubleshooting HASP, dongle and licensing issues

Below is a flowchart to help identify which category your issue applies to. Troubleshooting sections for each category are below the flowchart.

Section 1 - Troubleshooting HASP errors

You may receive a HASP related error during the Intella installation process. Below you'll find a list of the errors which have been reported to us, together with the solutions for these errors.

Error code 7 (H0007)
"HASP key not found (H0007)"

This error code might be caused by other HASP dongle protected programs. Please close down all HASP related programs (i.e. EnCase, Smart Mount) and reinstall Intella.

Error code 27 (H0027)
"Terminal services detected, cannot run without a dongle (H0027)"
NOTE: See No RDP access or Error H0027

This error code may be triggered because you are trying to use Intella via a remote desktop connection. Intella will only run via a RDP or terminal session with the dongle in place.

Error code 33 (H0033)
"Unable to access HASP SRM Run-Time Environment (H0033)"

HASP Error 33 means that the HASP license manager is not running, or the dongle driver has been blocked or deleted. 

1) Check the status of the HASP license manager service (hasplms) in Windows Task Manager. If it has been stopped for any reason, try starting the service to see if that fixes the issue.

2) If step 1 does not fix the issue, security software such as antivirus or the firewall may be getting in the way,  or they may have removed vital files.

In this case Intella will need to be reinstalled to fix the issue. You will need to turn off your security software and then reinstall Intella as the administrator. Also make sure that the Intella files and the Hasp files are added to the white list of any security software which you are running on the system.

Error code 37 (H0037)
This error code can be caused by other HASP dongle protected programs. Please close down all HASP related programs (i.e. EnCase, Smart Mount) and reinstall Intella.

If this problem persists, open a Command Prompt (as administrator) and run:

<intella-dir>bin\haspdinst.exe -kp -i

and restart Intella.

If problem persists, open a Command Prompt (as administrator) and start the license manager by running:

net start hasplms

Tip: To open a Command Prompt as an administrator, select Start > Accessories - Right click on Command Prompt and select "Run as administrator".

Error code 41 (H0041)
"Your Intella (trial) license has expired (H0041)"

This code is triggered if your trial license is expired. You can only keep on using Intella with a USB dongle.

If you are using a dongle, there can be two reasons why you may receive this error: 

1) The dongle is not being seen by the computer. Make sure it is plugged into the system and follow the troubleshooting steps shown for Error code 33 (H0033) above.

2) You don't have the correct licenses on the dongle for the version of Intella that you are running. If you have downloaded, and installed the latest version of Intella on your system, this is likely the cause. You are running the latest version of the software, but your dongle does not have the latest license. You can update the dongle by running 'Dongle Manager.exe' (which is located in the Intella installation folder), and clicking on the 'Check for updates' button.

Error code 51 (H0051)
"Virtual machine detected, cannot run without a dongle (H0051)"

In order to protect our intellectual property, the evaluation version of Intella WILL NOT run in a virtual machine (VM) environment. A “stand-alone” physical machine is required. This is only true for the evaluation version and Intella P.I. Intella will run in a VM environment using a dongle.

Solution 1. Reconnect the USB dongle to your computer
Solution 2. Install the Intella evaluation version outside a virtual machine

Error codes (E1009) or (E0004)
"Win32 Envelope - Data Loader Initialization Error" or "Cannot find HASP SRM Run-Time Environment DLL"

This error is shown when you are running an older driver for the dongle management system. It can happen when installing an older version of Intella or Connect. Try updating the driver to resolve the issue.

1) Stop Connect and any Intella instances that you may be running on this machine.
2) Visithttps://sentinelcustomer.gemalto.com/sentineldownloads/
3) In the "Featured Downloads" section at the top, choose "Sentinel HASP/LDK - Windows GUI Run-time Installer" version 7.65 (this was the latest version at this writing).
4) Run this installer on your Connect machine.
5) Start Connect.

Section 2 - Troubleshooting dongle not being detected issues

You may experience an issue where the dongle has been working fine, but then is suddenly not detected by Intella. You may get the HASP key not found (H0007) error when this happens.

There are several causes for this issue. The first steps to take are to check whether there is a hardware issue:

1) Make sure that the dongle is plugged into the computer properly. If you are using a USB hub, try plugging the dongle directly into the computer.

2) Disconnect the dongle, pause a few seconds, then reconnect it again. If the LED lights up, the application should be able to access the dongle. You may need to wait a few seconds for the dongle to be completely installed by the operating system.

3) Check if the USB port is functioning correctly. Disconnect all other USB devices from their respective ports and connect the HASP dongle to a different USB port. You can also try using a different USB device in the port which the dongle was not accessible to verify that the port is actually working.

If you are still experience problems with the dongle not being detected and it is not a hardware issue, it may be a software issue. One of the most common causes for a dongle not being detected is when the dongle driver has been blocked or deleted. As mention above with Error Code 33 (H0033), this is usually because of security software such as antivirus software/firewall getting in the way or removing vital files. You may be able to uninstall and reinstall the HASP driver to solve your problem by following these steps:

1) Temporarily disable any security software you have running on the system.

2) Open a Command Prompt (as administrator)

3) Change the bin directory of the Intella installation directory for Intella (e.g. type cd c:\Program Files\Vound\Intella\bin)

4) Once in the bin directory, run the following commands:

(i)   haspdinst -kp               (this stops the HASP service)

(ii)  haspdinst -r                 (this removes HASP)

(iii) haspdinst –purge          (this removes HASP completely)

(iv) haspdinst –I                 (this reinstalls HASP and starts the HASP service)

5) Add C:\WINDOWS\system32\hasplms.exe in the Exception list of the antivirus and firewall applications, for example:

After you have done the steps above, you can check whether your dongle is detected by your system by following the steps below on the computer with the dongle plugged in:

1) Open a web browser.

2) Copy and paste or type http://localhost:1947/_int_/devices.htmlinto the URL field. The page that opens is called the Sentinel Admin Control Center or SACC. Note that no internet connection is needed as the SACC is local to your computer.

3) In the second row of the main screen you should see a picture of the dongle (a red, green or purple USB dongle, not the line showing the @ symbol in a key). Note: The Key ID is the serial number of your dongle.

If you see your dongle then Intella should work. If you do not have the SACC, or you do not see your dongle, you will need to reinstall Intella as a full administrator on the system.

It is also possible that something has changed in your environment such as the deployment of security software, group policies etc. Check with your IT team to see whether a change that they have made is causing the issue.

Section 3 - Dongle not showing or updating to the latest version

Vound uses a 3 number licensing system for its products. For example, for release 2.0.1, the 2 refers to the major release, the 0 refers to the feature release and the 1 refers to the minor update release.

Dongle licensing is applied at the major release, and feature release levels, which means that you don't have to update your dongle for minor releases. For example, if my dongle is licensed for version 2.0, I will be able to run all versions that start with 2.0 such as version 2.0.0 and 2.0.1 etc.

Provided that your Maintenance Agreement (MA) is up to date, most dongle updates can be done automatically using the Dongle Manager program which is installed when Intella is installed. Dongle Manager has an option to 'check for updates', and will update the dongle if updates are available. 

Information on using Dongle Manager to automatically update your dongle, and manually updating your dongle can be found at this link: https://vound.kayako.com/article/202-license-dongle-activation

If you can't see the latest version on your dongle after using Dongle Manager to check for updates, then the latest version is not loaded on the dongle. There are a number of reasons why an update will fail. These include:

1) Your MA has expired. Contact your Representative or the Sales team to renew your MA.

2) Your MA is current but you can't update to a major release (e.g. from 1.9 to 2.0). For major releases, you need to have at least 60 days of MA left to receive a major update. Contact your Representative or the Sales team to extend your MA.

3) Your dongle is full and the new license can't be installed. This happens occasionally with our older purple dongles (not the green or red dongles) as they have limited space and they can become full. We see this with customers who have been with Vound for some time and have many older versions of Intella on their dongle. This is not a big issue as the dongle can be cleared, and the new version (along with a few earlier versions for backwards compatibility) can be loaded onto the dongle. You will need to submit a support ticket as this involves manually updating the dongle.

4) Pending orders have not been applied to the dongle or have been applied in the wrong order. This can occur if you manually update your dongle using v2c files. Updates can be missed or applied out of order which stops the new license being applied to the dongle. You will need to submit a support ticket so the dongle can be fixed.   

5) You run a product that is not normally use on the type of dongle you have. E.g. you have Intella Professional (which is usually on a standalone dongle) on a network dongle. In these cases we need to create a license at our end before you run Dongle Manager to do the update. You will need to submit a support ticket so the license can be made.   

 We have a video with more information regarding dongles and licensing at this link: https://youtu.be/5cKvxbcGrSY

Section 4 - Other issues related to dongles or HASP

If you have an issue with your dongle or HASP that is not covered in the above three sections, please submit a support ticket via our support site: https://support.vound-software.com/conversation/new

Note that it is extremely rare that a dongle will give trouble. When you receive dongle errors, it is most likely that the HASP software is not installed properly, or the License Manager is not running. The License Manager needs to be running on your system for the dongle to work. You can run some checks on your system to see if the drivers are installed and that the license manager is running.

HASP drivers Installed

Intella is shipped with the latest SafeNet HASP dongles. Intella is also packaged with the SafeNet HASP RTE installer.

When Intella is installed onto the system, the HASP drivers are also installed onto the system. Under 'Universal Serial Bus Controllers' in 'Device Manager' on your system, you should see the following three entries:

If any of these items have a red X or a yellow warning sign, they may not have been installed properly and the drivers should be installed again.

License Manager running

Follow these steps to make sure that the License Manager is running.

1) Open a Command Prompt (Start > All Programs > Accessories > Command Prompt)

2) Enter: sc query hasplms

3) Review the result which should look like this:

WIN32_EXIT_CODE : 0 (0x0)

If you see 4 RUNNING under State then the License Manager is running. 

You can also check the License Manager's status in the Services section of the Windows Task Manager. The status should show that the License Manager is running. 

If the License Manager is not running, try right clicking on the Licence Manager and select 'Start Service'. If the service will not start, check the event log for entries relating to the HASP License Manager service. The event log should give an error message that can be used to help diagnose the issue.

Choose filesor drag and drop files

Drivers Native

Fixing HASP Driver Issue


It was recently discovered that the latest Windows 10 Update breaks the HASP driver software.
To fix this problem please follow these instructions exactly as written:
1. Unplug the key from the machine
2. Uninstall any HASP or Sentinel drivers from the control panel
3. Re-boot the machine (very important)
4. Use the link below to get the latest HASP drivers. Make sure the HASP key is un-plugged from the PC
5. Once the drivers are installed, try plugging in the HASP key, windows will recognize the HASP key and use the drivers just installed, and you should be good to go

Sentinel HASP/LDK Windows GUI Run-time Installer 8.23

Once you click on the circled item, just scroll to the bottom of the 'End User License Agreement' and choose 'I accept' and the download should start.

Thank you.
[ Home]

Troubleshooting HASP USB dongle related issues

Created dateUpdated dateAffects versionFix version



Blancco related license issues might not always be related the software (Blancco 5, Blancco Drive Eraser, Blancco Mobile Device Eraser, Blancco LUN Eraser, Management Console, etc.). The HASP USB dongle can also be the source of the problem. Before contacting the Blancco Technical Support team, do the following:

  1. Try connecting the HASP-key to another machine/USB port
  2. After connecting the HASP-key, the drivers for the key should be automatically installed. Alternatively, you can install the drivers manually
  3. To check if the key is properly detected follow below steps:
    1. Make sure that the HASP-dongle is connected to the machine.
    2. Open a browser and go to the address: http://localhost:1947/
    3. "Sentinel Admin Control Center" page will open.
    4. Click on "Sentinel Keys" on the left panel.
    5. If you can see your HASP-dongle on the list, the key is correctly detected by the machine.

Other issues which may occur:

HASP key not detected (in Windows environment)

The drivers have not been installed properly.

 Drivers can be either downloaded by Windows or installed automatically when setting up Blancco Management Console

  • Download Sentinel HASP/LDK Windows GUI Run-time Installer from manufacturer's web site
  • Make sure that you select a version that is compatible with your operating system
  • DO NOT have the USB dongle connected to the computer
HASP key is physically broken

HASP dongle exterior or connector is damaged (bent/broken)

Red connectivity led does not light up when the dongle is connected

HASP key's battery is deadBlancco HASP Tool is able to detect a dead battery and will not function properly in such case
  • Contact Blancco Technical Support team
  • Take a screenshot of the error message
HASP key's clock is out of sync

Sometimes the internal clock of a HASP drive may corrupt. Blancco HASP Tool reads the HASP dongle's internal HASP clock value.

If the number does not match the current time (or is not even close, for example: 2070010100), then internal HASP clock is corrupted.

Date is displayed in format YYYY-MM-DD-HH

  • Contact Blancco Technical Support team
  • Take a screenshot of the error message

If none of the HASP related issues listed above do not seem to be the problem in your case, contact Blancco's Technical Support team and remember to include the following information when submitting your issue ticket:

  • HASP key number (the number on the key chain).
  • What erasure software are you using? Make sure that you specify which product you are using. 
  • Also make sure that the licenses always need to match the used Blancco product.

How to download and install the HASP driver for the protection key

In case of problems with the software, start by making sure that the most recent driver is correctly installed.


– If the current driver is too old, remove it using the respective “remove_hasp_run_as_admin.bat ” file.
– Install a recent version of the driver.
– If you still get an error message: first run  “purge_hasp_run_as_admin.bat” then “purge2_hasp_run_as_admin.bat”
– If you still get an error message: Use “support_package_1.exe” and send the file to the Support team ([email protected]).

Detailed instructions

Verify the version of your currently installed driver

On the computer/server hosting the protection key, enter (in a recent Internet browser): http://localhost:1947/_int_/ACC_help_index.html

A) If the version of the “Run-time Installer” is lower than 7.80 (for example 6.64):
Your drivers are too old and must be properly removed (!), using the respective (!) “remove_hasp_run_as_admin.bat” file.
– Find the installation files of your analysis software (downloaded or on a CD).
– Open the “Hasp” folder.
– Right-click and run (as administrator) “remove_hasp_run_as_admin.bat”, to remove the old driver.

Important note: If you do not find the installation files, please contact the Support team ([email protected]). Tell them the exact version of your software (“Help” tab, “About”). They will send you the respective “remove_hasp_run_as_admin.bat” file corresponding exactly to that version.

B) The version of the “Run-time Installer” is equal to or higher than 7.80 (for example 7.100):
Your drivers are too old. But you can directly install the new drivers.

Re-install the most recent version of the driver

To do so, go to digitalsurf.com/support/software-updates/, and download “DRIVER DONGLE HASP” (“hasp.zip”).

– Unzip the files.
– Right-click and run (as administrator) “reinstall_hasp_run_as_admin.bat”, to install the driver.

Try cleaning up using “purge” files

– If you still get an error message: first run  “purge_hasp_run_as_admin.bat” then “purge2_hasp_run_as_admin.bat”
– If you still get an error message: Right-click and run (as administrator) “support_package_1.exe” and send the file to the Support team ([email protected]).


Either exit the BDE Administrator (if this is a permanent change) or save your changes to a new configuration file (if this is a temporary change). Saving your changes to a different file name lets you restore your original configuration when necessary.

If you saved your changes to a new configuration file in the previous step, hasp + error 1009, hasp + error 1009 the BDE Administrator.

Default printer error

Error message shows up at the startup of the Pathloss 4.0 program. The program requires that a printer be install in order to function properly. The physical printer does not need to be connected, only the drivers installed and set as default in the Printers folder.

Windows Vista and Windows 7 issues


Some older Pathloss 4.0 CD's will not run on Windows Vista or Windows 7. Newer setup files are available online. http://www.pathloss.com/p4_key_setup.exe for the key disk version (Blue 3.5" floppy disk) and http://www.pathloss.com/p4_hasp_setup.exe for the USB Hasp version (Purple dongle)

Help files

The older help files that are supplied with Pathloss 4.0 will not open on Windows Vista or Windows 7. Support for older gc patcher error empty file files was intentionally left out of Vista and 7. To remedy this Microsoft has Vista and 7 versions of the help program for download. More information is at the following link. http://support.microsoft.com/kb/917607