ID-card software known issues

List of known issues by ID-software version.

ID-software ver. 3.12 (released 01.02.2016)

  • In Windows operating systems the "Sign digitally" option is missing when you do a right-click on a file that you want to sign. (Fixed in v3.12.2).
  • The "Send container to email" option in DigiDoc 3 Client does not work in Windows 7, if your email client is Mozilla Thunderbird or Microsoft Outlook and the file name or location contains special symbols. The issue occurs because Windows 7 MAPI API does not support UNICODE.
  • ID-card utility multiple card selection does not work in v3.12 (Support is added in v3.12.1).
  • Since v3.12, Windows installer does not close automatically during uninstall Open-EID programs running currently.
  • Since v3.12, Windows installer does not uninstall old root certificates that were installed by older Windows installers.
  • DigiDoc3 client won't resolve folder links under windows, instead adds as files. (Windows)
  • Outlook 2014, "Send container to email" functionality in DigiDoc3 Client does not work from any other folder than the Documents folder. (OS X)
  • DigiDoc3 client removing file extension in file create dialog keeps file without extension (.bdoc; .asice). (Linux)
  • On some occasions Windows installer do not delete old 2.x middleware some registry entrys.
  • On some occasions Windows installer cannot not delete (access denied error) some registry entries "HKEY_CURRENT_USER\Software\Microsoft\Internet Explorer\Approved Extensions" and install will fail. Workaround is to delete mentioned registry key.
  • HiDPI windows (high resolutions 4K and Retina) are to small. (Windows)
  • Because of the QT library error, DigiDoc3 Client and the ID card utility stop working, if you computer has one of the video cards from this webpage installed. To solve the problem, 1st remove eID software your computer and then install the 32-bit version which is available here.
  • The Chrome signing plugin (token signing) may cause issues with opening PDf files in the browser. Fixed on 15th of April, when was released chrome token signing v0.0.21.

ID-software ver. 3.11.1 (released 09.09.2015)

  • DigiDoc3 client won't resolve folder links under windows, instead adds as files.
  • DigiDoc3 client removing file extension in file create dialog keeps file without extension (.bdoc; .ddoc). (Linux)
  • Outlook 2014, "Send container to email" functionality in DigiDoc3 Client does not work from any other folder than the Documents folder. (OS X)
  • DigiDoc3 client sending a container to email from DigiDoc3, while using Thunderbird email client, will fail if the file name contains special symbols that are not included in Windows-1252 codepage. (Windows)
  • HiDPI windows (high resolutions 4K and Retina) are to small. (Windows)
  • TSL over https behind proxy gives error on TSL update on some proxy solutions.

ID-software ver. 3.11.0 (released 14.03.2015)

  • DigiDoc3 Client fails verifying digital signatures validity under Linux and Mac OS X op. systems if signature format is DIGIDOC-XML 1.1. Error message is ERROR 35 (USER) Notary signature mismatch. DIGIDOC-XML 1.1 format was being used between 2002-2003. As a solution verify signature validity in DigiDoc Check portal.

ID-software ver. 3.10.3 (released 15.04.2015)

  • The ENABLENPAPI=OFF key does not work when upgrading from 3.10.2 to 3.10.3 in which case the Windows installer cannot be run quietly (if Chrome is running). This does not affect a clean install or upgrading from an earlier version.

ID-software ver. 3.10.2 (released 06.04.2015)

  • The Windows installer cannot be run quietly (if Chrome is running).

ID-software ver. 3.10 (released 05.03.2015)

  • Signing with Mobiil-ID in DigiDoc3 client is not possible if digital signature format is set to ASiC-E.
  • For Mac OS X Outlook 2014 users the "Send container to email"  functionality in DigiDoc3 client only works when the digitally signed document is in Documents folder.
  • In Windows there could be authentication problems with Mozilla Firefox when using specific card readers. Solution is to replace the card reader or update the card reader drivers to Windows WUDF drivers.
  • NPAPI digital signing plugin doesnt work since Google Chrome version 42.

ID-software ver. 3.9 SP1 (released 08.10.2014)

  • ID-card software installation fails on Windows Server 2012 and Windows 8. For successful installation Windows 8 users can update op. system to Windows 8.1. Fixed-ID software version 3.10.
  • Minidriver does not support SHA-384 and SHA-512 hash algorithms in case of Digi-ID cards.
  • DigiDoc3 client. In case of OSX platform, some of the buttons appear in English even if the chosen language is Estonian or Russian.
  • DigiDoc3 crypto. In case of OSX platform, some of the buttons appear in English even if the chosen language is Estonian or Russian.
  • DigiDoc3 crypto. The temporary DDOC container that is used internally by DigiDoc3 crypto to encapsulate the encrypted data files cannot be parsed with JDigiDoc and CDigiDoc libraries after decryption as the DDOC container’s <DataFile> element's Size attribute contains the size value in kilobytes with suffix " KB" (the value should be in bytes with no suffix).
  • Latvian and Lithuanian CA certificates are included in the Estonian DigiDoc3 Client's packaging for Linux platform.

ID-software ver 3.9 (released 01.07.2014)

  • DigiDoc3 crypto cant decrypt documents, that have been encrypted with SK DigiDoc Client version 2.7. This problem will be solved in ID-software version 3.9.1.
  • Electronic usage of ID-card does not work in terminals using RDP and minidriver version 3.8. DigiDoc3 client does not recognize the document in the card reader and users can experience "Smart card is not fully personalised" error during authentication. This problem will be solved in ID-software version 3.9.1.
  • Google Chrome 64bit does not support digital signing in e-services due to the lack of working signing plugin. Support will be added in ID-software version 3.9.

ID-software ver. 3.8 (released 10.12.2013)

  • For ID-card authentication to work in Ubuntu using Chrome or Chromium browsers its needed to install lbnss3-tools package. The package can be installed with following terminal command:

sudo apt-get install libnss3-tools

Now launch the web browser once and close it. After closing insert another terminal command:

modutil -dbdir sql:$HOME/.pki/nssdb -add opensc-pkcs11 -libfile -mechanisms FRIENDLY

The last activity is necessary for every user account.

NB! Digital signing with ID-card does not work in Linux distributions from Google Chrome version M35. The support from ID-software side will be added in version 3.9 but additional changes are also required by e-services that are providing digital signing. Additional technical information can be found at ID-software ver. 3.9 will be released in June 2014.

  • ID-software programs (DigiDoc3 client/crypto and ID-card utility) can't be launched if the computer has an older video card that does not support Qt5. Usually these computers have Windows XP and in the same time authenticating and digital signing in web browsers work just fine. Solution is to use older version of ID-software. 
  • In certain cases Dell and HP computers display "Please insert a smart card ... Unknown Card" error while entering e-services and DigiDoc3 client cant find an ID-card. Solution can be found here.
  • When using Mail program in Mac OS X the "Send container to email" functionality does not work in DigiDoc3 client and crypto.
  • Windows Server 2008 R2 RDP servers are unable to use Minidriver after software installation or update and thus ID-card does not work.  Solution can be found here.
  • Under Ubuntu 12.04 all SK certificates are not installed and authentication to some e-services does not work (LHV, PERH). Solution is to add certificates manually. 
  • ID-software installation will remove OpenSC library under Mac OS X.
  • Under Mac OS X Safari does not support PIN-pad card readers, with other browsers the PIN code is asked twice. 
  • Signing BDOC containers under Mac OS X with Mobile-ID does not work propely when the file name contains dotted letters (öäüõ). An invalid singature will be added unless the container already had signatures (for example from signing with ID-card or under other operating system) 

ID-software ver. 3.7 (released 22.01.2013), 3.7.1 (released 09.04.13), 3.7.2 (released 22.08.13)

 Known Issues:

  • When upgrading ID-card software to version 3.7 under Mac OS X, all personal settings (signer details, phone number, intro display value, server access certificate) will be resetted.  In order to be able to digitally sign again in DigiDoc3 client it's necessary to reinstall access certificate and recreate all necessary personal settings.
  • DigiDoc3 client does not allow to add or remove signatures to Digidoc containers in old 1.0, 1.1 and 1.2 formats. Sometimes the operation might appear to be successful but when saving the container there will be an error message and the file will not be added as an attachment when trying to send it via email.  
  • Under Windows XP it is possible that when authenticating with Internet Explorer or Chrome the PIN dialogue window will not come to focus and stays behind other windows. The dialogue window is visible on the taskbar and can be raised to focus with ALT+TAB. This issue has been described in our support article and by Microsoft 
  • Digi-ID card usage in Mac OS X is unstable.
  • Atleast TLS 1.0 is required for digital signing through proxy with Mobile-ID.
  • Decrypting using the digital stamp will fail if the crypto token has only the cryptographic certificate. Solution is to transfer a Non-Repudiation certificate with identical CN field as the cryptographic certificate to the crypto token. For instructions contact us on info at sk dot ee


ID-software ver. 3.6 (released 27/06/2012 at

 Known Issues:

  • DigiDoc3 client has a translation error on russian version of digital signature confirmation sheet. Because of that error the signature status is displayed as not valid. Solution would be to use either estonian or english version of the digital signature confirmation sheet. 
  • With proxy configured in DigiDoc3 client the digital signing with Mobile-ID fails. Solution is to not use proxy.
  • When DigiDoc3 client is configured with both IP based validity confirmation access and expired access certificate then the digital signing with Mobile-ID fails. Solution is to remove the expired access certificate.
  • DigiDoc3 client digital signature sheet preview is not displayed when there is no default printer defined. Also the margins are out of proportion if the default printer is a virtual device (for example PDF printer). The default printer should be a hardware device.
  • "Save files to the disk" function in DigiDoc3 client always overwrites the files in the destination folder even if after notification a new file name is defined for the source file. 
  • DigiDoc3 crypto will crash if you try to save, open with a doubleclick or drag'n'drop the source file before encrypting.
  • DigiDoc3 crypto will crash if the addresse is removed before encrypting.
  • DigiDoc3 crypto will show full file path along with file name for opened documents. 
  • In some cases ID-card utility will display birth date with one day difference. Solution is to choose a correct timezone.
  • Under Windows XP when signing with Internet Explorer (or any other solution that uses CSP component) if a wrong PIN is entered then the error text is misleading
  • It is possible to enter wrong PIN code 4 times when authenticating with Firefox web browser
  • Authenticating with Google Chrome web browser can be unstable
  • Under Mac OSX  if you change language in DigiDoc3 client then the language setting doesnt change in ID-card utility
  • In Ubuntu 12.04  the digital signing and access certificate loading with DigiDoc3 client will fail with multiple cards
  • Mac OSX support for visually impaired is limited because there is no QT 4.8accessibility support  for Mac OSX Cocoa API
  • Windows and Linux support for visually impaired is somewhat limited because the QT 4.8 used in ID-card software has less options regarding accessibility


ID-software version 3.5 (released on 10.11.2011)


Known Issues:

  • Linux distributions need libusb component version 1.0.9. Read further instructions and explanation here.
  • DigiDoc3 crypto cant encrypt larger than 200MB file
  • BDOC is not supported for digital signing with Mobile-ID
  • Under Mac OS X the web browsers Safari and Firefox do not inform the user correctly of wrong PIN or when PIN/PUK has been blocked.
  • When ID-card sertificates have expired then ID-card utility will display an error "This document is not valid". This error message is not correct, the correct valid date is written on your ID-card.
  • With Windows and Mac operating systems the ID-card utilty menu "Settings" will display the software update interval incorrectly. Upon software installation the default value is set to once per week, when you change the default value then the visible value will not change but changes are made to the settings.
  • When launching DigiDoc3 client under Mac OS X 10.6 there is a possibilty that files without name and extension are created to the Application folder.
  • When digitally signing in DigiDoc3 client with ID-card and choosing "No" for the server access certificate installation dialogue then the digital signing fails. 
  • Document decrypting can fail when document name contains cyrillic letter. While encrypting documents it is advised to use only latin letters.
  • During ID-card software installation on Windows Server 2003 a CSP component will not be installed. Because of that authentication with Internet Explorer and Chrome web browsers does not work. Software needs to be installed using special parameters which you can find here.

ID software version 3.4 (released on 09.05.2011)


Known issues:

  • Authentication proxy does not work. Proxy without authentication is only supported in DigiDoc3 klient while digitally signing. Proxy without authentication has been tested with Squid software, everything else works "as is"
  • There is no proxy support for automatic server access certificate download. This certificate has to be installed manually if you have proxy.
  • Authentication proxy does not work in ID-card utility.
  • Server access certificate installation fails if user profile has special characters like äöõü (for example c:\users\tõnis). Temporary solution can be found here. This issue will be fixed in version 3.5.
  • After installing new server access certificate Mac OS X users will get an error 92 (Failed to sign document, libdigidoc code: 92, message: PKCS#12 certificate has expired. Please get a new onew from when digitally signing with DigiDoc3 klient. Since this error is caused by timezone differences then temporary solutions is to wait 3 hours and the certificate expiration issue will fix itself. Permanent solution will come with version 3.5.
  • Digi-ID card usage in Mac OS X is unstable.
  • During certificate reneweal under Windows using ID-card utility, the old certificates will not be removed and this can cause some issues. Solution is to remove old certificates manually from certificate store.
  • In Windows when using multiple card readers, only the certificates of the card which was inserted first will be registered. Solution is to insert cards one by one and make sure all necessary certificates have been registered.
  • Under Fedora 14 Firefox 4.x does not work out of the box. Solution is to check from Security Devices if pksc11 module is loaded, if its not it should be added manually.
  • During 3.4 version installation the Generic USB CCID driver will be removed, this causes a situation under Windows XP where card/card reader can not be found and authentication doesnt work. Solution is to manually install card reader drivers or just unplug and replug card reader and let the automatic driver installation to install necessary card reader drivers.
  • If under Windows XP / Vista ID-card utility will stay reading the card and Internet Explorer does not work with ID-card's then read this solution for the issue. This issue is caused by additional wireless netowork managing software.
  • Under Windows the ID-card utility's functionality to configure automatic software updates and automatic software updates do not work correctly.
  • Mac 10.6 Safari digital signing fails on some cases and PIN2 dialog "hangs", solution is to try again. 
  • When inserting wrong PIN during access certificate installation the second and correct PIN wil also get "wrong PIN" error. Solution is to restart DigiDoc3 klient and try again.
  • Certificates serial number given out under certificate authority ESTEID-SK 2011 will not fit correctly on to digital signature confirmation sheet. This will be fixed in version 3.5.
  • When using PinPad readers under Windows, some PIN dialogue texts may be partial or contain symbols.
  • When using PinPad readers under Windows, it may take up to 20-30 seconds before you can enter PIN on the pinpad after PIN dialogue window appears.
  • SPR532 does not work with the default or manufacturer’s drivers in OSX
  • OK3x21 works in Ubuntu/Fedora with the default drivers only when lengths of PINs are 5. OK3x21 does not work at all with the manufacturer’s drivers.
  • The HP P/N ED707AA keyboard does not work properly in the PinPad mode in any operating system. In Ubuntu it works best but in OSX, until the discovered issues are investigated (, for this reader the user should switch off opensc –s for PinPad. It can be used as a conventional reader.
  • The HP P/N BV813AA keyboard (available from early 2011) does not work properly in the PinPad mode in any operating system. It also does not work as a conventional reader in all Linux systems and OSX. Can be used as a conventional reader in Windows systems.
  • The OK3621 PIN change functions do not work with the default drivers in Ubuntu – only with manufacturer’s drivers.
  • When the manufacturer’s driver is installed for OK3x21 reader usage in Ubuntu and OSX, the OK1021 card reader cannot be used with that driver. The OK1021 works well in Ubuntu and OSX with the default driver.

ID-software ver. 3.3 (published 09.02.2011)


Known issues:

  • Digital stamping with crypto token does not work in DigiDoc3 klient. Digital stamping with crypto token can only be used with SK DigiDoc Client, which can be downloaded here.
  • Authentication does not work in Chrome 9.x. This issue is a bug in Chrome and there is also a workaround at
  • In OpenSuse with new ID-card or residence card the SCR3310 card reader only works with manufacturer driver.

ID-software ver. 3.2 (published 19.01.2011)


Known issues:

  • Windows 64 bit users have to remove old ID-card software for Firefox before installing new software.
  • Under Windows 7 and Windows Vista, launching software installation directly from web browser is not possible, software packages should be downloaded and then run.
  • Sometimes file associations for .cdoc and .ddoc files will not be created for DigiDoc client/crypto and they should be manually configured.
  • PIN confirmation window in Internet Explorer and Google Chrome do not display whether they ask for PIN1 or PIN2.  Yellow padlock icon represents PIN1 and envelope PIN2.
  • In some cases automatic certificate registration fails (causes problems for Internet Explorer and Google Chrome when authenticating). Solution is to open ID-card utility and register certificates manually.
  • Software installation fails for domain computers with an error 26352. One possible solution is to remove certificates ESTEID-SK 2007, ESTEID-SK, JUUR-SK  from the certificate store before the installation.
  • Since Symantec antivirus (Norton) works a little bit differently than others it doesn't recognize new Estonian ID-card software. Because of that it will ask for a permission during software installation. We have already informed Symantec and hopefully this will be fixed in their next update. 

ID-software ver. 3.1 (published 29.10.2010)


Known issues:

  • All software errors have not been translated and some might handle incorrectly.
  • When wrong PIN code is inserted while digitally signing in DigiDoc Client, then to re-enable digital signing functionality it is needed to remove card from the reader. 
  • When .ddoc  file has been digitally signed using new software, then SK DigiDoc Client (ver 2.7.9) will display Cyrillic letters in file name and other fields as symbols. There are no problems with opening or verifying files.
  • Mac OS X 10.5 (Leopard) and Safari requires keychain configuration (desired web sites have to be configured as Identity Preferences)  to be able to authenticate to e-services. Instructions can be found here.
  • Digital signing fails in SEB internet bank and company registration portal. Solution can be found here.
  • Ubuntu distros have a problem where Firefox does not close correctly and some processes stay running. This is a system error caused by pcscd service.
  • OpenSuse 64bit - automatic server access certificate download sometimes causes DigiDoc client to crash. Solution is to restartpcscd service and try again.
  • Fedora, openSuse - sometimes ID-card utility fails to read information from the card. Solution is to restart pcscd service and try again.
  • Proxy authentication is not supported in DigiDoc client (this can be changed in DigiDoc client settings).
  • In some cases pcscd service does not automatically start during ID-card software installation. Solution is to start pcscd service manually.
  • Fedora security module SELinux may sometimes stop DigiDoc from starting. Solution is to configure SELinux to allow DigiDoc to run or turn SELinux temporarily off.
  • When using multiple programs simultaneously, that interact with ID-card (for example Firefox, ID-card utility, DigiDoc client etc) then some of those programs may display an error regarding ID-card communication. Solution is to close those programs and when needed also restart pcscd service.








If you didn't find an answer to your question, send it to our team.

  • See instructions
  • Please estimate your ability to use the computer, so that we can provide you with the best guidance


  • Verification failed

How can we improve the article and be more helpful?
Send Close