New DSC not working on GST? Install emSigner v3.3
Since 21 September 2026 every new DSC comes on a FIPS 140-3 token, and the GST portal needs emSigner v3.3 to read it. Here is the complete 6-step fix.
- ✓Official GSTN advisory based
- ✓Works for new and old tokens
- ✓Windows step-by-step
- ✓Free remote help
Quick answer
If your DSC was issued, renewed or replaced on or after 21 September 2026, it is on a FIPS 140-3 token. Uninstall your old emSigner, make sure Java 1.8 is installed, then download and install emSigner v3.3 from the GST portal (gst.gov.in → Help → DocSigner / emSigner). Run it as administrator, then sign again on the GST portal.
Why new DSCs fail on the GST portal
From 21 September 2026, the CCA moved India's DSC ecosystem from FIPS 140-2 to FIPS 140-3 certified USB tokens. Every fresh, renewed or replacement DSC issued since then sits on a FIPS 140-3 token.
Older emSigner versions on the GST portal cannot read these new tokens. GSTN therefore released emSigner v3.3 (GSTN advisory dated 19 September 2026). If your new DSC is not showing for selection, or signing fails even though the token driver is installed, an old emSigner is almost always the reason.
New token (FIPS 140-3)
emSigner v3.3 is mandatory
Any DSC issued, renewed or replaced on or after 21 Sep 2026.
Old token (FIPS 140-2)
Keep your current version, or move to v3.3
If it works, no change needed. v3.3 is backward compatible, so upgrading is safe if signing fails.
How the signing chain works
If any link in this chain is broken, the GST portal cannot see your DSC. The steps below check each link in order.
How to fix GST DSC errors with a new token (6 steps)
Follow these in order. Most users are signing again by step 4.
-
1
Check the error on the GST portal
Note the exact message the GST portal shows, for example the DSC not appearing in the list, “Kindly restart the emSigner”, or a failed-signing message. Make sure the USB token is plugged directly into the computer, not through a loose hub.
-
2
Check the token and its FIPS version
Open your token's manager software (for example the HYP2003 token manager, InnaIT or mToken utility). Confirm the token and your certificate both show up and the certificate has not expired. Look for the FIPS field in the token details: it will show FIPS 140-3 or FIPS 140-2. If the token itself is not detected, reinstall the token driver first (see our token not detected guide).
-
3
Pick the right emSigner version
FIPS 140-3 token → emSigner v3.3 is required. Older versions cannot read it. FIPS 140-2 token → if your current setup works, you can leave it; if signing fails, upgrade to v3.3, which also supports older tokens.
-
4
Uninstall the old emSigner and install v3.3
Uninstall the old emSigner from Control Panel → Programs and Features. Make sure Java 1.8 is installed (GSTN asks users on Java 9 or higher to move to Java 1.8 first, see our Java errors guide). Download emSigner v3.3 from the GST portal's DocSigner help page, install it, then right-click and choose Run as administrator. Wait for the confirmation that the service has started.
-
5
Verify the connection chain
Open https://127.0.0.1:1585 once in the same browser and click Advanced → Proceed so the browser trusts emSigner. In Chrome or Edge, if the site asks for permission to reach Apps on device (older versions call it Local network access), choose Allow. If the token and certificate are detected but the portal still cannot reach the DSC, see our emSigner connection error guide.
-
6
Test on the GST portal
Refresh the GST tab, start Register / Update DSC or your return signing, select your certificate, enter the token PIN when asked and complete the process. A renewed or new DSC must be registered on the GST portal again before it can be used for filing.
Quick reference: token vs emSigner version
| Your token | What to install |
|---|---|
| FIPS 140-3 (issued on or after 21 Sep 2026) | emSigner v3.3 — mandatory |
| FIPS 140-2, working normally | No change needed; continue till DSC expiry |
| FIPS 140-2, signing fails or DSC not listed | Upgrade to emSigner v3.3 (backward compatible) |
| Java 9 or higher installed | Switch to Java 1.8 before installing v3.3 |
| Renewed DSC on a new token | Install v3.3, then re-register the DSC on GST |
Still stuck? We will fix it remotely.
Our team connects to your computer, checks the token driver, signer utility and browser settings, and gets your DSC signing again. Remote support is available after office hours too.
Frequently asked questions
Is emSigner v3.3 mandatory for all GST users?+
Only for DSCs on new FIPS 140-3 tokens issued, renewed or replaced on or after 21 September 2026. If your existing DSC on an older token works normally, you can keep your current emSigner version.
Will emSigner v3.3 work with my old FIPS 140-2 token?+
Yes. GSTN has stated that v3.3 is backward compatible, so it supports older tokens that are still within their validity.
Does my old FIPS 140-2 DSC stop working after 21 September 2026?+
No. DSCs already downloaded on FIPS 140-2 tokens on or before 21 September 2026 can be used until they expire. Renewal or fresh issuance will generally need a FIPS 140-3 token.
How do I check if my token is FIPS 140-3?+
Open your token's manager software and look at the token details. The FIPS field shows either FIPS 140-3 or FIPS 140-2. Tokens bought for DSCs issued after 21 September 2026 are FIPS 140-3.
Where do I download emSigner v3.3?+
Only from the official GST portal, gst.gov.in, under Help and the DocSigner / emSigner download page. Avoid third-party download sites.
I installed v3.3 but the DSC still does not appear. What now?+
Check that the token driver is installed and the token manager can see the certificate, that Java 1.8 is installed, that emSigner was started as administrator, and that you opened https://127.0.0.1:1585 once and allowed it. If it still fails, contact us for remote help.
Do I need to re-register my DSC on GST after renewal?+
Yes. A renewed or new DSC has a new certificate, so register it again on the GST portal using Register / Update DSC.
Related guides
Last updated: 13 October 2026. Product and portal names are used only to identify the software involved and belong to their respective owners.