DSC token not detected? Full fix guide (Chrome, Windows, Mac)

You plug in the token, open the portal, and… nothing. "Token not detected" is the single most common DSC problem — and it is almost always fixable in a couple of minutes. Work through these steps in order; most people are signing again by step 3. This applies to ePass2003, HYP2003, Watchdata ProxKey and mToken on any government portal.

The 60-second fix (try this first)

1. Install the correct driver for your token — mToken, HYP2003 or ProxKey — then restart the PC.
2. Unplug and replug the token. Try a different USB port — use a rear port on a desktop, and avoid USB hubs.
3. Fully close the browser (every window, and check the system tray), then reopen it and load the portal. The token is read when the browser starts.

Still not detected? Keep going.

Fix on Windows

• Open Device Manager → Smart card readers and confirm the token appears with no yellow warning triangle. If it has a warning, reinstall the driver.
• Check Services → the Smart Card service is Running (set it to Automatic).
• If you recently used a different token brand, uninstall its old driver — two token drivers can conflict.
• Reboot after installing or removing any driver.

Fix in Chrome / Edge / Firefox

• Close all browser windows before reconnecting the token — a background instance stops it being detected.
• For portals that use a signing helper (emSigner, WebSocket signer, or a Java applet), make sure that helper is installed and running, and allow it if the browser blocks it.
• On older utilities, add the portal to the Java exception site list and enable Java.
• Try an incognito/private window to rule out an extension interfering.

Fix on macOS

• Install the Mac driver for your token (mToken, HYP2003, ProxKey).
• If macOS blocked the installer, allow it under System Settings → Privacy & Security, then reconnect the token.
• Use a direct USB-C/USB-A port or a powered adapter — unpowered dongles can fail to enumerate the token.
• Fully quit and reopen the browser (Cmd+Q), not just close the window.

Still not detected?

If none of the above works, the issue is usually one of these: the driver did not install cleanly (uninstall and reinstall it), the USB port/cable is faulty (test another PC), or the token itself is damaged or locked. If the token is physically dead or permanently blocked, the certificate must be re-issued on a new token.

Frequently asked questions