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!

9284fa70-0c8f-4e09-a5f5-5a35fe1e94f5-image.png

Version must match the one of the setup:

5b563b97-d8d0-48bf-87b8-a044ce3df918-image.png

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

ca299a9e-a6bb-41b0-a5e3-392161a11c5a-image.png

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:

76536a12-c4f6-49a8-a068-fa9bdac15f38-image.png

Registry

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:

d17da984-ee9a-45b8-9424-910c63ed8b55-image.png

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

Filesystem

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:

0b150709-e446-4ae3-ae3a-e321a7e4d771-image.png

Updater

The setup delivers an auto-updater which is invoked automatically every day and will check for new versions. It will connect to the URL https://updates.vigem.org/nss/products/vigembus/updates.txt which is reverse-proxied to GitHub and SSL-secured.

The updater binary itself must be signed:

86e85965-e675-4c68-a5df-9a5600a795ad-image.png

Task Scheduler

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

6d30d84c-f7b5-4bb1-b71b-421dab7f74eb-image.png

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:

f4d2d4bb-770b-4ef3-af52-77ad8b5ad0ea-image.png

Post-uninstallation checklist

TBD

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 😎