+91-89823-80224 info@webdodtechnologies.in Bhopal & Indore, Madhya Pradesh
Mon-Sat 10am-6pm Call Us Now

DSC Token Not Detected

The token is plugged in, the light may even be on, and the portal still says no certificate found. Nine times out of ten the certificate is fine and something else is in the way.

What is actually happening

A crypto token is not a normal USB drive. Windows can see the hardware while no application can read the certificate inside it, because reading it needs the vendor's driver and a middleware layer sitting between the token and the browser.

So "not detected" almost never means the certificate has died. It usually means one of three things: the driver for your particular token brand is missing or has been broken by a Windows update, the browser is not allowed to talk to the token, or the token is in a USB port that is not delivering properly.

Before you spend money: a token that stops being detected is not a reason to buy a new certificate. Certificates are stored on the token but they are also issued to you — if the token is genuinely dead, the certificate can often be reissued rather than repurchased. Check that before anyone sells you a replacement.

The checks, in the order worth doing them

1

Try a different USB port, directly on the machine

Not through a hub, not through a monitor, not through a docking station. Front-panel ports on desktops are a common culprit. This takes ten seconds and solves a surprising share of cases.

2

Check whether Windows sees the device at all

Open Device Manager and look under smart card readers or universal serial bus controllers with the token plugged in and unplugged. If nothing changes between the two, the problem is hardware or port level, not software.

3

Confirm which token brand you have

ePass, ProxKey, mToken, SafeNet and others each need their own driver, and the wrong vendor's driver will not work. The brand is usually printed on the token body. If it has worn off, we can identify it from a photo.

4

Reinstall the driver from the vendor or your certifying authority

Get it from the token vendor's own site or the certifying authority who issued your certificate. Uninstall the old one first and restart before reinstalling — installing over a broken driver often leaves the broken parts in place.

5

Check whether a Windows update landed recently

Feature updates in particular can break older middleware. If it worked last week and stopped this week, this is the most likely cause and the fix is a current driver rather than anything to do with the certificate.

6

Test the token on another computer

This separates the two possibilities cleanly. Working elsewhere means the problem is your machine. Failing everywhere means the token itself, and that is when it is worth talking about replacement.

Written 5 September 2026. Portals and browsers change; if something here no longer matches what you see, message us and we will tell you what changed.

Common questions

Usually not. The overwhelming majority of these turn out to be driver or browser problems. Even where the token itself has failed, a reissue is often possible rather than a fresh purchase. Ask before you buy.

Only that it is receiving power. The light says nothing about whether the driver is installed or whether an application can read the certificate.

No, and neither can anyone else — that is the point of it. Tokens lock permanently after a set number of wrong attempts, which is why guessing repeatedly is the worst thing to do. Stop after a couple of tries and talk to us about what your options are.

Then the token and driver are fine and it is a browser configuration issue. That is a much easier problem, and usually a quick fix.

Still stuck? Send us the error

We fix these every week and we do not charge for a look. Send a screenshot of the exact error on WhatsApp along with your Windows version and browser. Most of these turn out to be a five-minute fix, and it is worth ruling that out before anyone sells you a new certificate.

Send the error on WhatsApp