Hi @Brave_personality6131 Thanks for the details, that helps narrow it down.
Since your other signer works fine with the same A3 token and the Digital ID shows as valid in Acrobat, that suggests the certificate and token itself are fine, and the problem more likely sits in Acrobat's signature cache files or a conflict with the token middleware after the Windows 11 25H2 update.
A few specific things to try: First, delete Acrobat's signature cache files. Corrupted cache files are a common cause of crashes right at this point in the signing process:
Press Windows + R, type %appdata%, and hit Enter. This should open C:\Users\[YourUsername]\AppData\Roaming
Navigate From that Roaming folder, manually click into:
Adobe- then
Acrobat - then
DC - then look for
Security
Delete these files: acrobat_fss_signature_initials acrobat_fss_signature_initialsi acrobat_fss_signature_initialsk Then try signing again, recreating the signature if needed.
Second, reinstall the middleware/driver for your A3 token (the token manufacturer's software, not Acrobat itself). Sometimes the Windows 25H2 update affects how the token middleware integrates with the Windows CSP.
Third, try running Acrobat as Administrator once, just to check if that resolves it, though it shouldn't be necessary for daily use.
Let us know how it goes.
~Amal
AdChoices