How to Troubleshoot a SafeNet USB Token Not Detected (JC 0 Token Error in SafeNet) on Windows?

Overview

This article provides troubleshooting steps to resolve issues where a SafeNet USB Token is not detected on a Windows system. It covers remote access limitations, smart card reader driver issues, SafeNet Authentication Client installation problems, and hardware-related checks.
Audience: End users, IT support teams, system administrators.

Scope:

This procedure applies to SafeNet USB Tokens used for authentication, signing, or certificate-based access on Windows systems.

Prerequisites:

Before you begin, ensure you have the following:

• Access to the Windows system where the token is being used
• Administrative privileges to install or update drivers/software
• Latest SafeNet Authentication Client installer (if reinstallation is required)
• USB Token available for physical testing

 

Indicators of the Problem:

• USB Token is not detected by the system
• Certificate is not visible in SafeNet Authentication Client
• USB Token does not appear under Smart Card Readers
• Unable to access or use the certificate for signing

 

Possible Causes:

• USB Token is being used over Windows RDP (not supported)
• Incorrect or missing Smart Card Reader drivers
• Corrupted or misconfigured SafeNet Authentication Client
• Hardware or system-specific issues

 

Solution:
Follow the below methods to resolve the issue:

Method 1: USB Token on a Remote System

1. If you are accessing the system remotely, do not use Windows RDP, as it does not detect certificates stored on USB Tokens.
2. Use remote access tools such as:
• VNC Client
• TeamViewer
• Any USB-redirect capable remote software
3. Connect the USB Token to a different machine and install SafeNet Authentication Client to verify whether the token is detected on another system.

 

Method 2: Verify and Update Smart Card Reader Drivers

The USB Token requires the Microsoft Usbccid Smartcard Reader (WUDF) driver to function correctly.

Steps to update the driver:

1. Press Windows + R, type devmgmt.msc, and press Enter.
2. Expand Smart card readers.
3. Right-click Microsoft Usbccid Smart Card Reader (UMDF2) and select Update driver.
4. Choose Browse my computer for drivers.
5. Select Let me pick from a list of available drivers on my computer.
6. Choose Microsoft Usbccid Smartcard Reader (WUDF).
7. Click Next, then Close once installation is complete.
8. Restart the computer.
9. After reboot, verify that Microsoft Usbccid Smartcard Reader (WUDF) is installed and visible.

 

Method 3: Reinstall SafeNet Authentication Client

1. Uninstall SafeNet Authentication Client from the system.
2. When prompted to Save Configuration, select No or Cancel.
3. Restart the system.
4. Download the latest SafeNet Authentication Client from the official Sectigo link:
   https://www.sectigo.com/knowledge-base/detail/SafeNet-Authentication-Client-Download-for-Sectigo-Certificates-on-eToken/kA03l000000o6kL
5. Install the client and reconnect the USB Token.
6. Check if the token is now detected.

 

Additional Troubleshooting

• Try the USB Token on another machine with SafeNet installed.
• Ensure Windows is fully updated.
• Avoid using USB hubs; connect the token directly to the system.
• Confirm that the token is not physically damaged.

 

If the Issue Persists

If the USB Token is not detected after following all the above steps:

• Test the token on multiple systems
• Collect screenshots of:
• Device Manager (Smart Card Readers)
• SafeNet Authentication Client
• Contact support with the findings

 

 

Related Articles:  How to Enable SafeNet Single Log-on for Document or Code Signing?
SafeNet Authentication Client Download for Sectigo Certificates on eToken
How to Set Up Sectigo Token Using SafeNet for OV/EV Code Signing and Document Signing Certificates?
Sectigo eIDAS Qualified Certificate Installation on SafeNet eToken
VMWare ESXI 6.7 Windows Server 2016 SafeNet Client

Tags: