You have a valid DSC on a USB token, a Business User account on the MCA21 V3 portal, and a form due this week. You click Associate DSC and get “Failed to establish connection to the server. Kindly restart the emsigner”, or the certificate dropdown stays empty. Searching for emSigner for MCA turns up GST fixes, V2-era instructions and installers from unknown sites.

None of it applies if you only want to check a company or a director. WeeDoo’s company search and director search need no DSC, no emSigner and no MCA account.

What emSigner for MCA Is, and Why V3 Also Wants emBridge

emSigner is a Windows utility from eMudhra. It runs in the background on a localhost port and lets a web page talk to the DSC token in your USB port. MCA21 V2 used it for DSC registration (“role check”); the GST portal still uses its own build.

V3 changed the tooling, and guides contradict each other. MCA’s DSC Association FAQ (March 2023) says to ensure “Emsigner and Embridge are installed in the system” and running before you associate a DSC; ICSI’s registration note also says download both. Practitioner guides written since say V3 signs through emBridge, eMudhra’s newer utility, and emSigner belongs to V2; yet the V3 error users reported in 2023 still names emSigner. ICSI’s March 2023 notes list a V3 role check’s software as Windows 10, the latest emBridge from the MCA site, and admin rights. Our reading: install both, run both as administrator, and expect emBridge to open the token.

Neither utility signs the form itself. On V3 you fill the form in the browser, submit, download it as a PDF, affix the DSC in Adobe Acrobat Reader using the certificate on your token, and upload it. The utilities matter for one screen: Associate DSC.

Prerequisites Before You Download Anything

• Windows 10 or later. eMudhra’s emBridge guide also lists Windows 7 SP2 and 8.1; ICSI’s V3 notes say Windows 10 or above. emBridge has Mac and Linux builds, but emSigner is Windows-only and MCA and ICSI instructions assume Windows.
• Admin rights. Installer and utility both need “Run as administrator”.
• The driver for your token brand (ePass, ProxKey, Watchdata, eMudhra), installed before the token goes in. A generic driver fails silently: an empty certificate list, no error.
• A valid Class 3 DSC issued to the same PAN as your V3 account; Class 2 has not been issued since 1 January 2021. Our DSC guide for MCA filings covers getting one.
• A Business User account. Registered Users cannot associate a DSC on V3. Upgrade first; see our MCA V3 login guide.
• Chrome, up to date. ICSI says to associate from Chrome; Edge usually works, though one vendor guide calls it unstable. Firefox and IE are unreliable.
• Free localhost ports. emBridge listens on 26769 and 26770; the MCA emSigner build used 2015 or 8080. Antivirus or a firewall that blocks localhost traffic blocks signing.
• Java: only for emSigner. eMudhra states emBridge is independent of Java. The MCA emSigner build needed a 32-bit JRE (1.6 to 1.8 in MCA’s V2 FAQ), so if you install it as MCA’s FAQ says, have one.

Where the Download Sits and How to Install

Download from the MCA portal or eMudhra, not from a search result. Guides describe two routes: the Associate DSC page, where answering “No” to “utility installed?” shows a download link at the bottom; or embridge.emudhra.com, which eMudhra’s own guide names as the emBridge source. The link label varies; look for “DSC utility” or “signing utility”.

1. Uninstall any existing emSigner and emBridge from Control Panel. Stale copies commonly cause “utility not running” errors.
2. Install the token driver for your brand, then reboot.
3. Download the utility package from the MCA portal and extract it if it is a ZIP.
4. Right-click the emBridge installer, Run as administrator, accept the defaults, Finish. Same for the emSigner .msi if included.
5. Shut down fully (not restart), start up, and before anything else launch emSigner, then emBridge, both as administrator (one CS’s 2023 fix).
6. Test emBridge: open https://localhost.emudhra.com:26769 in Chrome. If a page loads, emBridge is up; if not, restart the emBridge service in services.msc and check the hosts file maps localhost.emudhra.com to 127.0.0.1.
7. Insert the token, then log in to V3.

Associate the DSC on V3 Before Your First Filing

Everyone who signs a V3 form must associate their DSC on V3 first, even if it was registered on V2. It is one step per certificate, repeated on renewal since the new certificate has a new serial.

1. If the token is new, change its PIN once in the token manager. MCA’s FAQ lists this as a prerequisite for first-time association.
2. Log in as a Business User. Open MCA Services, then FO Services (MCA’s FAQ calls it “FO LLP Service”), then Associate DSC, and click Associate DSC on the right.
3. Pick your token from the first dropdown; the certificate holder’s name appears for you to confirm.
4. Enter the token PIN in the Password field and click Register.
5. Wait for the “Congratulations” message. Without it the DSC is not associated.

One DSC holds one role, and you associate it from your own login, not a professional’s; a client DSC linked under a CS’s account must be re-associated from the client’s login. The filing that exposes this is DIR-3 KYC, because a director who has never filed meets the association step in deadline week.

emSigner and DSC Signing Errors on V3, With Fixes

Error or symptom	Usual cause and fix
“Please start the emSigner” / “Kindly restart the emsigner” (wording varies)	Not launched, or launched without admin rights. Relaunch as administrator and check the tray icon. If it will not start, another program (often a VPN) may hold port 2015; else uninstall both utilities and reinstall.
“Failed to establish connection to the server”	Browser cannot reach the localhost port. Open the emBridge test address from the install steps above, accept the certificate warning, retry. On an office network add that address to the proxy exceptions.
Certificate not visible in the dropdown	Token driver missing or generic. Install the brand driver, try another USB port, restart emBridge, refresh. The token should show clean in Device Manager.
Browser blocks the popup or the localhost call	In Chrome or Edge site settings for mca.gov.in allow pop-ups and insecure content; disable ad-blockers; test in incognito.
PAN mismatch / screen freezes with no message	For a freeze, MCA’s FAQ says change the token PIN, refresh and retry. Otherwise the PAN in the DSC differs from the V3 profile, or you are under the wrong role; compare the certificate subject in certmgr.msc with your profile. A wrong PAN in the DSC means a re-issued DSC, not an edit.
Expired DSC / “Invalid certificate”	Validity has ended; no grace period. Renew, associate the new certificate, check the PC clock.
“DSC is not registered with the Director DIN”	Associated under a Registered User, or before the director role was added. Add the role with the DIN, change the hint question and DSC PIN, associate again from Chrome. Per MCA’s April 2026 advisory, if it still fails raise a service complaint quoting the SRN.
“Customer already exist” (e7002) / “DSC already registered with another user”	Already linked to your own ID (try uploading a form) or to another V3 ID (associate from the correct login, which deactivates the old link).
“Digital Signature Verification failed. Please affix a valid DSC” on upload	Usually the PDF was opened or signed in the wrong tool. Open the downloaded form with Acrobat Reader DC (right-click, Open with), sign there, validate each signature, upload. ICSI told MCA in September 2025 this error also hit correctly signed forms; if it persists, raise a ticket.
Form rejected for size after signing	Acrobat embeds revocation data. Edit, Preferences, Signatures, More, untick “Include signature’s revocation status”, download the form again, re-sign.

If a form still fails at the portal end, keep the screenshots and challan; after ICSI’s September 2025 representation on V3 glitches, MCA extended annual filings to 31 January 2026 without additional fee. Our ROC filing due dates and penalties guide lists what each missed deadline costs.

MCA emSigner vs GST emSigner

Many emSigner conflicts on a CA’s laptop come from having the GST and MCA builds installed together.

Aspect	GST emSigner, then MCA V3 utilities
Download	GST: gst.gov.in, Register/Update DSC page MCA V3: mca.gov.in, DSC Services / Associate DSC
Version	GST: 2.6, per vendor guides MCA V3: Whatever the portal currently serves; emBridge does the V3 work
Port	GST: 1585 (older builds 1645); the error text also names 2095, 2568, 2868, 4587 MCA V3: emBridge 26769 and 26770; MCA’s V2 FAQ gave emSigner 2015 or 8080. Some vendor blogs say MCA expects 1585; no MCA document we found says so.
Java	GST: Yes, a current JRE MCA V3: Not for emBridge; the emSigner build needs a 32-bit JRE

Can they coexist? Vendor guides say no: uninstall the MCA or TRACES build before installing the GST one, and one guide reports both claiming port 1585. The documented ports differ, but no guide we found confirms clean coexistence. If a “port in use” error appears, uninstall the build you are not using that day.

Frequently Asked Questions

I associated my DSC on V2. Do I have to do it again?

Yes. V2 associations were not carried across. Our V2 to V3 changes guide covers what else moved.

Do I need emSigner for MCA just to look up a company’s directors?

No. Signing utilities exist only to file. Company master data and director details are open without a DSC or MCA account on WeeDoo’s company search.

Set It Up Before Deadline Week

Install the brand driver, then emBridge and emSigner, run both as administrator, associate the DSC from your own Business User login, and confirm the Congratulations message. Do it a week before the form is due. If you only came to check a company or a director, close the installer and search WeeDoo instead.