We find ourselves in the exact same situation, since May this year (2022) when we renewed our EV Code Signing certificate. Ever since we renewed and started using the new USB token, the problem appeared. Beforehand (previous two renewals) it was working fine - instead of the dreaded "There was a problem with the Digital Certificate. The VBA Project could not be signed. The signature will be discarded." error we would get a popup window from "SafeNet Authentication Client" asking us to input the token password. If the correct password was provided, the VBA Editor would sign and save the project.
After the issue first appeared in May this year (2022), when renewing with the provider we had been successfully using during the previous two years (Sectigo), we have since (this September) purchased a new EV Code Signing certificate from DigiCert. Unfortunately, the behavior is exactly the same. I have a suspicion that the issue may NOT be with the CA (Sectigo/DigiCert), but rather with the manufacturer/supplier they both use for the USB hardware tokens - it used to be "Gemalto" before May this year (when VBA signing worked) and now it is "Thales".
The change in USB hardware token manufacturer/supplier can also be seen in the branding of the "SafeNet Authentication Client" software - it used to be "Gemalto" in earlier versions, while it now reads "Thales". In the next few days, I will log our issues and findings with DigiCert technical support, asking them to investigate further and raise this with Thales, if necessary. I will share any progress and hopefully a successful resolution here.
