When you switch to a new laptop, reinstall Windows or upgrade from Windows 10 to 11, your certificate and smart card reader often stop working. It is not a malfunction — it is a series of configuration steps that must be done in order and tailored to the exact CA that issued your certificate. Without a correct installation, access to the IRMS portal, eGovernment, SEP and signing PDF documents in Adobe Reader becomes practically impossible.
⚠ Common symptoms after a fresh install
The same situations repeat for almost every user who moves to a new machine — the certificate "disappears" even though nothing physically changed:
- •The certificate does not appear in Adobe Reader for signing PDFs
- •The IRMS portal does not offer the certificate when you try to log in
- •The browser reports "certificate unknown" or "untrusted"
- •The card reader is not recognized — a yellow exclamation mark in Device Manager
- •eGovernment shows an authentication error even though the certificate worked just days ago
What the installation process really involves
A full certificate installation on a new machine is not a single click — it requires a series of steps, each of which can be a source of problems if skipped or done incorrectly:
- 1 Card reader drivers (for the MUP eID card) or the appropriate USB token middleware (e.g. SafeNet Authentication Client, Gemalto IDPrime, etc. — depending on the token manufacturer) — different devices require different drivers.
- 2 The issuer's root and intermediate certificates imported into the Windows "Trusted Root Certification Authorities" store. Without them the system treats your certificate as untrusted.
- 3 Application configuration — Adobe Reader, the browser and the IRMS client must be set to use the Windows Certificate Store, otherwise the certificate "exists" but the application can't see it.
⚡ Silent problems that appear in practice
Behind every seemingly simple installation lies a whole set of nuances the user often doesn't notice, and which are the typical reasons why "nothing works" even though all the steps were formally completed:
- •The root certificate imported into the wrong Windows store — e.g. Personal instead of Trusted Root
- •Leftovers from a previous installation (drivers, middleware) conflict with the new version
- •Adobe Reader is not configured to use the Windows Certificate Store — so it doesn't see the certificate
- •Different issuers require different procedures — Pošta CG, MUP, Core IT and Crnogorski Telekom each have their own specifics
- •The Java version or browser configuration blocks the certificate on a specific portal
Without knowing where to look for the cause, the same problem can last for days — and ultimately delay deadlines for submitting filings and documents.
Why you need systematic technical support
Installing a digital identity on a new machine is a job where experience makes the difference between 30 minutes and three days. We specialize in exactly that — we work with all CAs in Montenegro and know the specifics of each (Pošta CG, MUP, Core IT, Crnogorski Telekom). We configure the whole system so that the certificate works on all the portals you use.
Remotely via AnyDesk, usually in 20–40 minutes. Diagnosis is free; you pay only when we confirm the problem is solvable. No wasting time searching through instructions on your own that are often out of date.