How to Troubleshoot a SafeNet USB Token Not Detected on Windows?

Knowledge Base SafeNet Authentication Client software

How to Troubleshoot a SafeNet USB Token Not Detected on Windows?

Updated on October 1, 2026

Overview

After following this article, your computer will detect your SafeNet Universal Serial Bus (USB) token, or you will have the information Sectigo Support needs to help you. A detection problem means that the computer or the SafeNet Authentication Client (SAC) does not see the USB token or the certificate stored on it. The article covers how to confirm that you have a detection problem, the symptoms and common causes, fixes for Windows Remote Desktop, smart card drivers, and SAC installation, other checks, fixes for macOS, a warning about initializing the token, and how to contact Sectigo Support.

Check whether you have a detection problem

Use this table to confirm that your USB token issue is a detection problem before you start troubleshooting. Some token issues look like detection problems but have a different fix.

What you see	What to do
Windows does not see the USB token at all. No device or reader appears.	Continue with this article.
The SafeNet Authentication Client (SAC) sees the USB token, but you cannot unlock it or you do not have the token password.	This is not a detection problem. See I can't find my token password email and Token password best practices.
The USB token is locked after incorrect password attempts.	This is not a detection problem. See If your token is lost, locked, or re-initialized.
The USB token works on the local computer but not in a Windows Remote Desktop session.	This is expected behavior. See "Fix: USB token not available in Windows Remote Desktop" in this article.

Symptoms of a USB token detection problem

A SafeNet Universal Serial Bus (USB) token has a detection problem when you see one or more of these symptoms:

Windows does not detect the USB token.

Certificates on the USB token are not visible in the SafeNet Authentication Client (SAC).

No smart card reader appears in Windows Device Manager.

Common causes of a USB token detection problem

A SafeNet Universal Serial Bus (USB) token is usually not detected for one of these reasons:

You are using Windows Remote Desktop.

The smart card driver on the computer is outdated.

The SafeNet Authentication Client (SAC) installation is damaged.

Fix: USB token not available in Windows Remote Desktop

Windows Remote Desktop, also called Remote Desktop Protocol (RDP), does not detect certificates stored on Universal Serial Bus (USB) tokens. This is a limitation of Remote Desktop, not a fault in the USB token. To sign, use one of these options:

Sign on the local computer where the USB token is inserted.

Use a remote access tool that supports USB redirection, such as Virtual Network Computing (VNC) or TeamViewer.

Fix: Update the smart card driver on Windows

An outdated smart card driver can stop Windows from detecting a SafeNet Universal Serial Bus (USB) token. To update the driver:

Open Device Manager.

Locate Microsoft Usbccid Smart Card Reader (WUDF). WUDF stands for Windows User-Mode Driver Framework.

Right-click the smart card reader and select Update driver.

Follow the prompts in the Update Drivers window.

Restart the computer, and then check whether Windows detects the USB token.

Fix: Reinstall the SafeNet Authentication Client on Windows

A damaged SafeNet Authentication Client (SAC) installation can stop Windows from detecting a Universal Serial Bus (USB) token. To reinstall SAC:

Uninstall SAC. When prompted, decline the option to save configuration settings.

Restart the computer.

Download the latest version of SAC from the Sectigo knowledge base.

Install SAC, and then check whether Windows detects the USB token.

Other checks for a USB token not detected on Windows

If Windows still does not detect your SafeNet Universal Serial Bus (USB) token after you update the driver and reinstall the SafeNet Authentication Client (SAC), check the following:

Test the USB token on a different computer. This quickly shows whether the fault is in the USB token or in the computer.

Connect the USB token directly to a USB port, not through a hub, dock, or extension cable.

Confirm that Windows updates are current.

Inspect the USB token for physical damage. Do not use a damaged USB token. Open a support ticket and include photos of the damage.

Fix: USB token not detected on macOS

If macOS does not detect your SafeNet Universal Serial Bus (USB) token:

Confirm that your version of the SafeNet Authentication Client (SAC) supports your macOS version. A SAC version installed before a macOS upgrade often stops working after the upgrade.

Open System Settings, select Privacy & Security, and check for a blocked system extension. If you find one, allow it.

Restart the computer after you install SAC or allow the system extension.

Connect the USB token directly to a USB port, not through a hub or dock.

Important warning: never initialize the USB token

Never select Initialize Token in the SafeNet Authentication Client (SAC). Initializing a Universal Serial Bus (USB) token permanently erases the certificate and the private key. You must then order a new certificate on new hardware, at additional cost. No step in this troubleshooting process requires Initialize Token.

Contacting Sectigo Support about a USB token not detected

If your SafeNet Universal Serial Bus (USB) token is still not detected after you complete the fixes in this article, open a support ticket at Ticket Support & Order Status Checker | Sectigo® Official. Include:

A screenshot of Device Manager on Windows, or System Information on macOS

The SafeNet Authentication Client (SAC) version and its status

Your order number and token serial number

The troubleshooting steps you have already tried

You can also contact Sectigo Support by phone:

United States: +1 (888) 266-6361

International: +1 (703) 581-6361

Knowledge Base