(32-bit) the following driver files will be installed in the. C: Windows system32 drivers directory. Sentinel.sys (Sentinel parallel driver) and. Sntnlusb.sys (Sentinel USB driver). For Windows XP (64-bit), Server 2003 (64-bit) and Vista (64-bit) the following driver file will be installed in the C: Windows system32 drivers directory. SafeNet eToken 5110, supported by SafeNet Authentication Client, is an easy to use, two-factor USB authenticator with smart card technology securing remote and network access with advanced certificate-based applications like pre-boot authentication PBA and digital signatures. Gemalto is now part of the Thales Group, find out more. We have an application (called Insight) that uses a safenet license dongle. When we install the application on a physical server and stick the USB key in it works fine, but when we install it on a VM and use the AnywhereUSB to connect, the USB safenet dongle appears in device manager and everything looks good but the applicaiton claims it can't.
- Safenet China Usb Devices Driver Updater
- Safenet China Usb Devices Driver Windows 7
- Safenet China Usb Devices Driver Win 7
- Safenet China Usb Devices Drivers
What's New*?
Safenet China Usb Devices Driver Updater
The most recent version of the Safenet Authentication Client is now available and can be downloaded directly from our website as follows:
Which GlobalSign products require SafeNet drivers?
GlobalSign's PDF Signing and EV Code Signing Certificates are installed on USB tokens and require drivers to operate.
Download links for various operating systems can be found below.
Windows Version Support
| SafeNet Version | Windows XP | Windows Vista | Windows 7 | Windows 8 | Windows 10 |
|---|---|---|---|---|---|
| 10.8-R2 | ✗ | ✗ | ✓ | ✓ | ✓ |
| 10.8 | ✗ | ✗ | ✓ | ✓ | ✓ |
| 10.7 | ✗ | ✗ | ✓ | ✓ | ✓ |
| 10.6 | ✗ | ✗ | ✓ | ✓ | ✓ |
| 10.4 | ✗ | ✗ | ✓ | ✓ | ✓ |
| 9.0 | ✓ | ✓ | ✓ | ✓ | ✗ |
Downloads
Current Drivers:
Windows: 10, 8 & 7
64-bit
GlobalSign SAC Win x64 v10.8-R2
32-bit
GlobalSign SAC Win x32 v10.8-R2
Windows: 10, 8 & 7
64-bit
GlobalSign SAC Win x64 v10.8
32-bit
GlobalSign SAC Win x32 v10.8
Windows: 10, 8 & 7
64-bit
GlobalSign SAC Win x64 v10.7
32-bit
GlobalSign SAC Win x32 v10.7
Safenet China Usb Devices Driver Windows 7
Windows: 10, 8 & 7
64-bit
GlobalSign SAC Win x64 v10.6
32-bit
GlobalSign SAC Win x32 v10.6
Windows: 10, 8 & 7
64-bit
GlobalSign SAC Win x64 v10.4
32-bit
GlobalSign SAC Win x32 v10.4
Legacy Drivers:
Windows: XP & Vista
64-bit
GlobalSign SAC Win x64 v9.0
32-bit
GlobalSign SAC Win x32 v9.0
Linux Version Support
| SafeNet Version | Linux RPM (Red Hat Package Manager) | Linux Debian |
|---|---|---|
| 10.7 | ✓ | ✓ |
Downloads
Current Drivers:
Linux RPM (Red Hat Package Manager)
64-bit
GlobalSign SAC Linux x64 v10.7
32-bit
GlobalSign SAC Linux x32 v10.7
Linux Debian
64-bit
GlobalSign SAC Linux x64 v10.7
32-bit
GlobalSign SAC Linux x32 v10.7
Mac Version Support
| SafeNet Version | OS X 10.09 | OS X 10.10 | OS X 10.11 | OS X 10.12 | OS Catalina |
|---|---|---|---|---|---|
| 10.2 | ✗ | ✗ | ✗ | ✗ | ✓ |
| 10.0 | ✓ | ✓ | ✓ | ✓ | ✗ |
Downloads
Mac OS X
GlobalSign SAC MAC v10.0
MAC OS Catalina
Any Issues?
If you are experiencing any of the below issues with the SafeNet Driver, please refer to the workaround section:
- The token is not being recognised.
- Token not present in Adobe.
Workaround:
- Within your Adobe Acrobat Pro DC application.
- Navigate to Preferences > Signatures > Identities & Trusted Certificates > More... >
- Select Digital IDs / PKCS#11 Modules and Tokens > Click Attach Module > Specify the patch of your PKCS#11 file ( /usr/local/lib/libetpkcs11.dylib )
- You will now see that your token is visible, as Adobe will be able to recognise this.
If you need any assistance with this workaround, please feel free to reach out to our Support Team. Additionally, we will be providing an update shortly, with the new release of MacOS SafeNet drivers.
Installation Guides
PDF SIGNING
Download and Install AATL or CDS Certificate
https://support.globalsign.com/customer/en/portal/articles/1999625-download-and-install-aatl-or-cds-certificate
Install Adobe Root CA (BlueBeam Compatibility)
https://support.globalsign.com/customer/en/portal/articles/2002746-install-adobe-root-ca-bluebeam-compatibility-
CODE SIGNING
Download and Install Code Signing Certificate
https://support.globalsign.com/customer/en/portal/articles/2715103-download-and-install-code-signing-certificate
Code Signing in Java (Token Based)
https://support.globalsign.com/customer/en/portal/articles/2722672-code-signing-in-java-token-based-
Code Signing for Windows 7 & 8 (Token Based)
https://support.globalsign.com/customer/en/portal/articles/2720229-code-signing-for-windows-7-and-8-token-based-
Manual installation of USB driver - Sentinel Protection Installer
Updated July 28, 2020
- Terrain 3D
- Terrain Forestry
- RoadEng Civil
- RoadEng Forestry
- Softree Optimal
In case of any problem during the installation of Sentinel Protection Installer on a x64 Windows OS, it's possible to install the USB System Driver manually.
This is applicable for:
- Sentinel Hardware Key (SHK)
- Sentinel SuperPro
- Sentinel UltraPro
Issue
Sentinel Protection Installer cannot install the selected components.
Error Code
'InstallShield Wizard could not install Sentinel Protection Installer 7.6.9.'
Resolution (Work-around)
Manual Installation of USB Driver.
Download the attached package;
1. Download the attached package;
2. Unzip it and copy the package on the target machine at C:Program Files (x86)Common FilesSafeNet Sentinel (you might need to create the folder 'Safenet Sentinel');
3. Plug the Hardware Key (Sentinel SuperPro, Sentinel UltraPro or Sentinel Hardware Key);
4. Windows OS shall start the wizard to recognize the Hardware Key, stop the search on Windows Update
5. Open Device Manager;
6. Locate the Key and right click on it.
Safenet China Usb Devices Driver Win 7
7. Select 'Update Driver Software' and 'Browse my computer for driver software'.
Point the search to the folder Safenet Sentinel above copiedcreated;
Safenet China Usb Devices Drivers
8. Un-plug and re-plug the key;
9. The key shall be recognized properly on Device Manager.