USB token not detected: driver fixes for Digital Signature Certificates
A USB token that isn't detected is almost always a driver, middleware or browser problem — not a dead certificate. Work through the checks below in order; most cases clear at step 2 or 3. If the token is physically damaged or the PIN is permanently locked, you need a replacement token and a re-issued certificate.
Short answer
If your USB token is not detected, install the exact driver for your token model (ePass 2003 Auto, ProxKey, HYP2003 or WatchData), run the token manager to confirm the certificate is visible on the device, start the portal's signing utility (emSigner / emBridge / Signer), then restart the browser. If the token manager cannot see the certificate, the token — not the computer — is the problem.
30-second checks before you touch drivers
- Unplug the token, try a different USB port (prefer a direct USB 2.0 port, not a hub or dock).
- Check whether the token's LED lights up when inserted — no light usually means a port or hardware fault.
- Test the token on a second computer. Detected there? The fault is your machine's driver or browser, not the token.
Fix it step by step
1.Install the driver that matches your token model exactly
Generic 'DSC drivers' do not work. Read the model printed on the token body and install that manufacturer's token manager. On Windows, right-click the installer and choose Run as administrator; on macOS, allow the kernel/system extension in System Settings → Privacy & Security after installing.
2.Open the token manager and confirm the certificate is listed
Launch the token tool (ePass2003 Token Manager, ProxKey Token Tool, SafeNet Client). If your name and certificate appear there, the token is healthy and the problem is browser/middleware. If the tool shows an empty token or cannot connect, stop — the certificate needs to be reinstalled or re-issued.
3.Start the portal's signing utility before you open the portal
MCA V3 and GST need emSigner running; Income Tax needs emBridge/emSigner; DGFT needs its own trusted DSC component; ICEGATE needs the Java-based signer. These run in the system tray — start the utility, then refresh the portal tab. 'DSC not detected' on a portal almost always means the utility isn't running.
4.Allow the local signer port in your browser
Signing utilities listen on a localhost port (commonly 1585 or 8080 over https). Visit that address once and accept the self-signed certificate warning, then return to the portal. Chrome and Edge block the utility silently until you do this.
5.Clear conflicting middleware and stale certificates
Two token drivers from different manufacturers frequently fight over the same CSP slot. Uninstall middleware for tokens you no longer use, reboot, then reinstall only your current token's driver. Also remove expired certificates from Windows → Internet Options → Content → Certificates.
6.Rule out the PIN lock
Repeated wrong PIN entries permanently lock most tokens (usually after 5–10 attempts). A locked token cannot be reset by the CA — you need a new token and a fresh certificate issuance. Never guess a PIN more than twice.
Driver by token model
| Token | Typical CA | Driver / manager | Note |
|---|---|---|---|
| ePass 2003 Auto | eMudhra, most CAs | ePass2003-Setup (auto-installs on insert) | Widest compatibility — Windows 10/11, macOS, Linux. |
| ProxKey | Capricorn | ProxKey Token Tool / WD PROXKEY driver | Install as administrator; needs a manual install on Windows 11. |
| HYP2003 | Various | HYP2003 token manager | Older models may not have signed drivers for Windows 11 24H2. |
| WatchData ProxKey | Capricorn, Sify | WatchData PROXKey CSP | Reinstall after major Windows feature updates. |
| Trustkey / Safenet | SafeScrypt, NSDL | SafeNet Authentication Client | Conflicts with other CSPs — remove old middleware first. |
Buying advice and model comparison live in the USB Token for Digital Signature Certificate guide. To order a replacement, see USB Token for Digital Signature Certificate.
Portal-specific "DSC not detected" errors
| Error | Cause | Fix |
|---|---|---|
| "DSC not detected" on MCA V3 | emSigner not running, or browser blocking localhost | Start emSigner from the tray, visit https://127.0.0.1:1585 once and accept the warning, refresh the MCA tab. |
| "Please install emSigner" on the GST portal | Utility installed but not started as administrator | Close it, right-click and Run as administrator, then re-register the DSC in the GST portal. |
| Income Tax portal shows no certificate | PAN in the certificate does not match the logged-in PAN | Verify the certificate's PAN. If it mismatches, the DSC must be re-issued against the correct PAN. |
| DGFT "Token not found" | DGFT trusted signing component missing or blocked | Install the DGFT signing component, allow it through the firewall, and use a Class 3 Organisation certificate for IEC-linked filings. |
| ICEGATE signing fails silently | Java runtime version mismatch | Install the Java version ICEGATE specifies and add the site to the Java exception list. |
Still stuck?
If the token manager cannot see your certificate, the token is locked, or the certificate has expired, you need a replacement rather than a fix. We handle all three from our Nagavara office and remotely across India.
- Digital Signature Certificate Renewal — expired or expiring certificate.
- USB Token for Digital Signature Certificate — locked, lost or damaged token.
- Class 3 Individual Digital Signature Certificate — fresh issuance after a permanent lock.
- Digital Signature Certificate in India — full overview of certificate types and costs.
Frequently asked questions
Updated 2026-08-14 · Vowel Enterprises