Where to download (official source only)
SafeNet Authentication Client is published by Thales. Always download it from Thales or from your certificate authority's official download page — never from a random third-party mirror, because tampered middleware can compromise your private keys.
- Thales (the vendor that owns SafeNet) hosts the official SAC installers.
- Indian CAs — eMudhra, Capricorn, Sify, (e)Mudhra, NSDL, Vsign and others publish CA-specific SAC builds for their tokens.
- If your token came from a CA, prefer that CA's recommended SAC version — they certify a specific build against their certificates.
SafeNet Authentication Client version history
SAC has gone through several major versions. Newer Windows builds need newer SAC; very old SAC will not enumerate tokens on Windows 11.
Major SAC versions
| Version | Era | Notes |
|---|---|---|
| SAC 8.3 | Legacy | Older tokens; not recommended on Windows 11 |
| SAC 10.0 | Older | Early Windows 10 support |
| SAC 10.7 | Common | Stable on Windows 10, early Windows 11 |
| SAC 10.8 / 10.8 R-series | Current | Best for Windows 11 23H2/24H2 |
Which version for which Windows
| Windows version | Recommended SAC |
|---|---|
| Windows 7 / 8.1 (legacy) | SAC 10.0 – 10.5 |
| Windows 10 (all builds) | SAC 10.7 or 10.8 |
| Windows 11 (22H2/23H2/24H2) | SAC 10.8 (latest R-build) |
32-bit vs 64-bit — which installer?
Match the installer to your Windows architecture, not your browser. Almost every modern PC runs 64-bit Windows.
- Check your architecture: Settings → System → About → System type.
- 64-bit Windows → install the x64 SAC build.
- 32-bit Windows → install the x86 build (rare on modern machines).
- Note: even on 64-bit Windows, some Indian government portals require 32-bit Java separately — that's a different component from SAC.
Clean installation steps
Most "token not detected after update" problems are caused by two SAC versions fighting each other. A clean install fixes the majority of these.
# Verify the Smart Card service before plugging in the token Get-Service SCardSvr | Select Name, Status, StartType
Step-by-step clean install
- Unplug the eToken.
- Uninstall any existing SafeNet Authentication Client via Settings → Apps.
- Reboot the computer.
- Install the correct SAC version (run as Administrator).
- Reboot again, then plug in the token and confirm it appears in the SAC tools.
What SAC includes (and what it doesn't)
- Included: token drivers, the PKCS#11 module, CSP/KSP for Windows CryptoAPI, the SAC Tools dashboard for PIN change and token info.
- Included: certificate enumeration into the Windows personal store so browsers and Adobe can use the token.
- Not included: your certificate (that's issued by your CA), 32-bit Java for government portals, or browser-specific extensions.
- Not included: the ability to recover a wiped or fully-locked token — that needs CA re-issuance.
Common post-install issues
| Symptom | Fix |
|---|---|
| "No token inserted" with token plugged in | Clean reinstall; use a rear USB port |
| Token detected but no certificate | Confirm certificate is on token via SAC Tools |
| Browser doesn't prompt for certificate | Restart browser; check certmgr.msc |
| SAC service not running | Start SafeNet Authentication Client service |
For IT admins: silent install
SAC ships as an MSI, so it can be deployed silently via SCCM, Intune, or a script. Use standard msiexec switches; consult the Thales admin guide for the property values that control which components install.
msiexec /i SafeNetAuthenticationClient-x64-10.8.msi /qn /norestart
Frequently asked questions
Is SafeNet Authentication Client free?
Yes. SAC is provided free by Thales and by certificate authorities to their token customers. You should never have to pay a third party for the driver itself — only your certificate has a cost. Always download from Thales or your CA, never a random mirror.
Which SAC version do I need for Windows 11?
Use the latest SAC 10.8 R-build for Windows 11 (22H2/23H2/24H2). Older versions like 8.3 or early 10.x often fail to enumerate tokens on Windows 11. If your CA recommends a specific build, use theirs.
Do I install the 32-bit or 64-bit driver?
Match it to your Windows architecture, which is almost always 64-bit on modern PCs (check Settings → System → About). Install x64 SAC on 64-bit Windows. Note that the 32-bit Java some government portals require is a separate component, not part of SAC.
I installed SAC but the token still isn't detected — what now?
Do a clean reinstall: unplug the token, uninstall SAC, reboot, install the correct version as Administrator, reboot, then reconnect using a rear USB port. If it still fails, the token PIN may be locked or the certificate may be missing — that's where a quick remote session helps.
Related guides & services
Token still not detected after installing SAC?
Version conflicts and PIN locks aren't always obvious. Get expert help on a remote session and we'll get your SafeNet eToken recognised and signing again.
Independent consulting engagement — not affiliated with DocuSign, Adobe, Microsoft, or any certificate authority.