Technical Anshu
Tutorials Blog
🔐 DSC Token Problem

DSC Token Not Detected Fix Install the Driver and Middleware

You plug in your DSC token, open the signing tool — and the certificate list is empty. The token light may even be glowing. Nine times out of ten, the token is fine; Windows simply has no driver to talk to it.

✍️ Technical Anshu🪟 Windows 10 / 11⏱️ 7 minute read
🎥 Watch the full video — see the DSC setup working live, including the token and PIN steps

Every DSC token needs two pieces of software before any program can use it: a device driver and the token maker's middleware (the token manager utility). Without them, Windows sees an unknown USB device and signing tools show no certificate found. This guide fixes the detection problem in the right order — driver first, then verification, then the signing tool.

What Windows shows when the driver is missing
🔌 USB Token device — plugged in, light onPower OK
❓ Certificate list in signing tool — emptyNot detected
🖥️ Device Manager — token under Other devices with a yellow markDriver missing
☝️ The token has power but Windows cannot read the certificate — the classic missing-driver picture
1

Check the Token in Device Manager First

This tells you in ten seconds whether the problem is the driver or something else.

  1. Plug the token directly into a PC USB port — avoid hubs and front-panel ports for this test
  2. Press Windows + R, type devmgmt.msc and press Enter
  3. Look under Smart card readers and Other devices for your token
  4. A yellow warning mark, or the token sitting under Other devices, confirms the driver is not installed
2

Install the Driver and Middleware for Your Token Brand

Each token brand — for example ePass, ProxKey, HyperPKI or Feitian based tokens — ships its own manager software. Use only your own brand's package.

  1. Note the brand printed on your token or its packaging
  2. Download the matching token manager / middleware from that brand's official website or from your Certifying Authority's download page
  3. Run the installer as administrator and complete it fully
  4. Restart the PC after installation — middleware services often start only after a reboot
  5. Plug the token back in and open the token manager utility — your certificate details should now be visible there
3

Confirm the Certificate Reaches Windows

Signing tools read certificates through Windows, so verify at the Windows level before blaming any tool.

  1. Press Windows + R, type certmgr.msc and press Enter
  2. Open Personal → Certificates
  3. Your DSC certificate should appear with your name and the issuing authority
  4. If it shows in the token manager but not here, reinstall the middleware and restart once more
4

Then Open the Signing Tool or Portal

Order matters: token first, program second.

  1. Keep the token plugged in before starting the signing tool or opening the portal page
  2. Refresh the certificate list inside the tool if it has a refresh option
  3. Select your certificate and try signing one test PDF before a full batch
5

Still Not Detected — The Remaining Checks

Work through these before concluding the token is dead.

  1. Try a different USB port and, if possible, a different PC — this separates a token fault from a PC fault
  2. Check that no old middleware from a previous, different-brand token is conflicting; uninstall the unused one
  3. Temporarily check whether your antivirus is blocking the token service, then re-enable protection
  4. If the token is not detected on two PCs with the correct driver, contact your Certifying Authority or reseller — the token itself may be damaged
🔴 Honest note: download token drivers only from the token maker's or your Certifying Authority's official site. Driver packs from random download sites are a common way malware reaches exactly the PCs that hold signing tokens.

🎥 See the Complete DSC Signing Setup in the Video

Token plugged in, certificate selected, PIN entered — the working setup, demonstrated from start to finish.

▶️ Watch Full Video
❓ Frequently Asked Questions

My token light is on but the certificate list is empty. Is the token broken?

Usually not. The light only proves the USB port is giving power. An empty certificate list almost always means the brand's driver or middleware is missing or was never restarted after install. Install it, reboot, and check certmgr.msc before assuming hardware failure.

Can I use one brand's driver for another brand's token?

No. Middleware is brand-specific — an ePass token needs its own manager, a ProxKey token needs its own, and so on. The wrong package will install quietly and still leave the token undetected.

The certificate shows in the token manager but not in my signing tool. Why?

The tool reads certificates through the Windows store or the token's PKCS#11 library. Reinstalling the middleware, restarting the PC, and plugging the token in before opening the tool resolves most of these cases.

This guide is based on the Technical Anshu bulk PDF signing with DSC video • Stuck on any step? Ask in the video comments — help is available there 🙏