ViGEm Bus Driver Setup test checklist

This article is aimed for the super secret test personell of new ViGEm Bus Driver setup releases 😎

Requested feedback

  • Anything that deviates from the checklist below (basically errors)
  • Exact Operating System edition and version number (use winver command)
  • OS Architecture (64-Bit or 32-Bit)
  • Secure Boot State in msinfo32 command

Post-installation checklist

Presence of driver device

The most important part would be the appearance of the star of the setup: the actual device in Device Manager!


Version must match the one of the setup:


Same for the properties of the actual binary (Provider and Copyright might change in the future):


Programs and Features entry

Names should be typo-free 😅 also version matching, icon expected to be there (not the default blank icon), links displayed in screenshots may be updated in the future:



The setup writes only a few pieces of information to the registry, mainly the version installed for the auto-updater to check against. The following key HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Nefarius Software Solutions e.U.\ViGEm Bus Driver should be created (on 64-Bit OS, without WOW6432Node on 32-Bit OS) with these values:


The included updater is 32-Bit so on 64-Bit Windows it will look in the WOW6432Node virtual key for the version value.


The creation of the path C:\Program Files\Nefarius Software Solutions\ViGEm Bus Driver is expected (same for 64- and 32-Bit). The missing e.U. in the company name is intentional as unfortunately Windows Installer had troubles creating a folder ending with a dot 🤦 The following files and folders must be there:



The setup delivers an auto-updater which is invoked automatically every day and will check for new versions. It will connect to the URL which is reverse-proxied to GitHub and SSL-secured.

The updater binary itself must be signed:


Task Scheduler

The Task Scheduler should host one new additional task named ViGEmBusUpdater configured like so:


Manual testing

The updater by default will remain silent if the local copy is up-to-date. The GUI can be tested by calling it vial PowerShell like so:

& "C:\Program Files\Nefarius Software Solutions\ViGEm Bus Driver\ViGEmBusUpdater.exe" /checknow

Which should report that everything is up to date:


Post-uninstallation checklist


Win10 x64 1803 (17134.706)
Secure boot off
All checks OK

Win10 x64 1809 (17763.437)
Secure Boot On
All Checks OK 👍

Unpinned and locked because, well, done 😎