Skip to content
Software U2F authenticator for Windows
C# C C++
Branch: master
Clone or download
Fetching latest commit…
Cannot retrieve the latest commit at this time.
Type Name Latest commit message Commit time
Failed to load latest commit information.
NativeBridge remove redundant file Jun 22, 2019
SoftU2F.sln setup build Jun 20, 2019
SoftU2F.sln.DotSettings init Jun 17, 2019

SoftU2F-Win is a software U2F authenticator for Windows. It emulates a hardware U2F HID device and performs cryptographic operations using the DPAPI. This tool works with Google Chrome. Running on other browsers hasn't been tested.

We take the security of this project seriously. Report any security vulnerabilities to

Build Status


This app is still under very active development. It may have bugs or doesn't work in some scenarios. Please don't use for production.


  • Disable Driver Signing Enforcement

    To install the driver, you'll need to disable the driver signing enforcement.

    The easiest way to do this is putting you device into Test Mode. Run this in elevated prompt

    $ bcdedit /set TESTSIGNING OFF

    More ways to disable the enforcement


  1. Download the latest driver release at Driver Release

  2. Run the driver-install.ps1 in elevated powershell.


  1. Download
  • If you have latest .NET Core 3.0 SDK/Runtime installed you can download the FDE(Framework dependent executable) at Daemon Release
  • Otherwise you can download the SCD(Self-contained deployment) at Daemon Release
  1. Extrat and Run SoftU2FDaemon.exe


The app runs in the background. When a site loaded in a U2F-compatible browser attempts to register or authenticate with the software token, you'll see a notification asking you to accept or reject the request. You can experiment on Yubico's U2F demo site.







  1. Right Click the Windows logo on you status bar and open Device Manager
  2. Under Human Interface Devices, find SoftU2F Device, right click and select Uninstall Device


  1. Exit App
  2. Delete the folder where you extracted them.

Security considerations

This is a port of

Instead of macOS Keychain, we store data using Windows DPAPI, which is designed by Microsoft Windows to store data data such as passwords, keys, and connection strings.

For more infomation of DPAPI:

A note from Github Team


Announced by Microsoft,

Note Windows 10 for desktop editions (Home, Pro, Enterprise, and Education) and Windows Server 2016 kernel-mode drivers must be signed by the Windows Hardware Dev Center Dashboard, which requires an EV certificate. For details, see Driver Signing Policy.

Windows will only trust the drivers signed by a trusted EV certificate.

At this stage, I'm still trying to get a EV Certificate to sign this driver, so that Disabling driver signature enforcement won't be needed to run this software.

Having a signature won't change any of the behaviour of this software and all the source code is public to everyone to read and contribute.


If you like this project, you can support me to buy a EV certificate, or just a cup of coffee :)

Known app-IDs/facets

Every website using U2F has an app-ID. For example, the app-ID of Yubico's U2F demo page is When the low-level U2F authenticator receives a request to register/authenticate a website, it doesn't receive the friendly app-ID string. Instead, it receives a SHA256 digest of the app-ID. To be able to show a helpful alert message when a website is trying to register/authenticate, a list of app-ID digests is maintained in this repository. You can find the list here. If your company's app-ID is missing from this list, open a pull request to add it.


This project is Unlicensed yet.


Lots of credits to the original work of SoftU2F done by Github team.

You can’t perform that action at this time.