HYP2003 Token Drivers
Drivers for the HYP2003 USB token on Windows, macOS and Linux — in both the FIPS 140-3 and FIPS 140-2 builds — plus the utilities, setup steps and fixes for the things that usually go wrong.
One token, its drivers, and the tools around it
The HYP2003 is a USB crypto token built on smart-card technology. Your Digital Signature Certificate's private key is generated on the token and never leaves it — signing happens inside the device, so the key cannot be copied off it, even by malware on the computer it is plugged into.
It is validated to FIPS 140-3 at Level 3, the standard Certifying Authorities in India now issue new certificates onto. Beyond DSC signing on government portals it supports document and email signing, file encryption and certificate-based login.
NIST CMVP certificate #5255
FIPS 140-3 · Level 3 · Active
Token drivers
Use the build that matches your token. A token supplied for FIPS 140-3 needs the FIPS 140-3 driver; an older HYP2003 bought before the change uses the FIPS 140-2 one. If you are not sure which you have, message us a photo of it.
| Operating system | FIPS 140-3 driver | FIPS 140-2 driver |
|---|---|---|
| WindowsWindows 11, 10, 8.1 and 7 | FIPS 140-3 driverDownload Windows FIPS 140-3 driver | FIPS 140-2 driverDownload Windows FIPS 140-2 driver |
| Linux (64-bit)x86_64 distributions | FIPS 140-3 driverDownload Linux (64-bit) FIPS 140-3 driver | FIPS 140-2 driverDownload Linux (64-bit) FIPS 140-2 driver |
| Linux (32-bit)i386 distributions | FIPS 140-3 driverNot available | FIPS 140-2 driverDownload Linux (32-bit) FIPS 140-2 driver |
| macOS | FIPS 140-3 driverDownload macOS FIPS 140-3 driver | FIPS 140-2 driverDownload macOS FIPS 140-2 driver |
Driver and utility files are published by Chartered Information Systems and download from their server.
Tools for the token
Updaters, format tools, the Windows runtime the driver depends on, and the developer SDKs.
The two format tools ERASE everything on a token, including the certificate. There is no undo, and a certificate destroyed this way has to be re-issued from scratch, with fresh verification and a fresh fee. Talk to us before you run either, especially if the certificate on the token is still valid.
- Download Middleware updater
Middleware updater
Updates the driver files stored inside an existing HYP2003 token.
- Download Format tool — HS serial-number tokens
Format tool — HS serial-number tokensErases the token
Resets an HS-series HYP2003 token (FIPS 140-2 driver) to factory state.
- Download Format tool — FIPS 140-3 tokens
Format tool — FIPS 140-3 tokensErases the token
Resets a FIPS 140-3 HYP2003 token to factory state.
- Download Microsoft Visual C++ 2015 Redistributable
Microsoft Visual C++ 2015 Redistributable
Fixes the missing mfc140u.dll and wpdshext.dll errors some Windows machines show after installing the driver.
- Download HYP2003 SDK
HYP2003 SDK
For developers integrating the token into their own software.
- Download HYP2003 SDK for Android
HYP2003 SDK for Android
For developers using the token over USB OTG on Android.
Installing it, and when it will not work
Installation
- 01Close any open signing applicationClose your browser and any portal session before installing, so the driver isn't loading against an already-open token session.
- 02Run the installerRun the downloaded installer as administrator on Windows, or follow the package prompts on macOS/Linux.
- 03Insert the tokenInsert the HYP2003 token after installation completes, not before — installing with the token already plugged in is a common cause of it not being detected.
- 04Confirm detectionOpen the token management utility installed alongside the driver and confirm the token and certificate are both visible.
If something goes wrong
- Token not detected
- Try a different USB port, preferably directly on the machine rather than through a hub. Confirm the driver installed without error before assuming a hardware fault.
- Driver installation fails
- Confirm you are running the installer as administrator, and that any previous version of the driver has been fully uninstalled first — a partial old install is the most common cause.
- Browser can't see the certificate
- Restart the browser after installing the driver — most browsers cache the available certificate list at launch and won't pick up a newly installed token until restarted.
- Portal or Java-based signing fails
- Some government portals use a Java applet or local signing utility that needs to be restarted after the driver installs. Confirm you're running the portal's currently supported browser version.
Need the token itself rather than the software? It is ordered on its own page.
Buy TokenToken not being detected? Send us a screenshot.
Driver problems are the single most common thing we are called about, and most of them are fixed in minutes. Tell us your operating system and what the portal is saying.