Copy link
Remember! T-CAT cards issued before 04/13/2023 lost the status of qualified certificates and were revoked en masse on September 27, 2023 (except for T-CAT operator certificates and idCAT Operator certificates) . For more information, you can consult Change in T-CAT cards.
If you still have one of the old T-CAT (Only T-CAT of the operator), below you can consult the Safesign manual, as well as possible errors that may appear when using it, and the steps to solve them.
If a pop-up window appears requesting a PIN, but the user cannot type it, they may have a card reader built into the keyboard with the PinPad feature.
If this function is activated, it only allows us to enter the PIN using the numeric keypad and sometimes it does not work correctly, preventing us from being able to type the PIN in the pop-up window. 
To disable the PinPad function, we must follow the steps described below:
Home > Type in the search: “Regedit” and select run command > HKEY_LOCAL_MACHINE > SOFTWARE > Wow6432Node > AETEurope BV > SafeSign > 2.0 > Disable PinPadReaders > Edit Value Information > 1 > Accept
Version 3.0.124 does not “remove” the link that is made in Windows of the certificates to the card and that allows them to be used while the card is inserted in the reader when it is removed from the reader. This makes Windows “think” that the card is still inserted and presents the certificate as usable when performing operations that require it (authentication, signatures, etc.). Since Windows does not realize that the card is no longer there, the operation fails without giving any message and blocks navigation or does not return any error controlled by the application in question. This error is attributable to Microsoft's treatment of certificate propagation. You can consult more information about this in point 3.12 (Certificate Propagation) in the product description document.
This is a usability error only, since it will never be possible to sign or perform any signature operation with this “reference” to a certificate that has been installed because access to the private key contained in the card is not really possible. However, since Windows “thinks” that the card is inserted because the card controller is tricking it, the errors that are returned may not be clear to the user.
Finally, the way to solve this error is to manually “unregister” the card certificates by going to the “Remove” option in the Explorer certificate store manager. You must select the certificate you want to unregister and click Remove:
A warning message appears below, to which we must click yes:
The certificates on the card are not deleted even if the card is not removed from the reader. So, there is no need to worry because this method will never delete the certificates inside the card. To work with the certificate again, just put the card back in and they will appear again.
IMPORTANT NOTE : What you should be careful of is not to select a certificate in software format such as idCAT and click Remove because then you would lose the certificate and real private key.