Why Apollo needs ViGEmBus for gamepad input
Apollo can stream video without a virtual controller, but gamepad emulation needs a working bus driver.
Apollo is a Windows game-streaming host derived from Sunshine. When a remote client sends controller input, Apollo needs Windows to see a virtual Xbox 360 or DualShock 4 device. ViGEmBus provides the kernel-level bus that lets compatible software create that virtual controller.
Apollo and ViGEmBus are separate projects. Reinstalling Apollo does not prove the bus driver is healthy, and installing ViGEmBus does not prove Apollo has restarted and opened the driver. Diagnose the application, driver and game layers separately.
| Layer | Role | Typical failure |
|---|---|---|
| Apollo | Receives remote controller input | Gamepad support unavailable |
| ViGEmBus | Creates the Windows virtual controller bus | Bus missing, damaged or duplicated |
| Game/controller stack | Uses the virtual pad | No input or duplicate input |

How to install ViGEmBus for Apollo
Use the final official ViGEmBus v1.22.0 asset from the original nefarius GitHub repository. The file is ViGEmBus_1.22.0_x64_x86_arm64.exe, approximately 6.0 MB, and combines the supported installer architectures. The project is retired, so this is the last published release rather than an actively updated driver.
Close Apollo before setup, run the verified installer, and restart Windows after installation. A reboot reloads the kernel driver and clears stale handles held by streaming or controller software.
- 1
Close Apollo and active clients
End streaming sessions and exit Apollo before changing the driver.
- 2
Run the official installer
Open the verified v1.22.0 GitHub asset and confirm the Nefarius publisher.
- 3
Restart Windows
Reload the bus driver in a clean Windows session.
- 4
Start Apollo and reconnect
Launch Apollo after reboot, reconnect the client and test controller input.
Verify that Apollo can use the ViGEmBus driver
Open Device Manager and find Nefarius Virtual Gamepad Emulation Bus. Open Properties and confirm Device status says the device is working properly. This is the strongest check that the kernel bus exists and is operational.
Also check Settings > Apps > Installed apps for the Nefarius driver entry. If the app entry exists but Device Manager has no working bus, the package is registered but the kernel device still needs repair.
- No warning icon appears on the Nefarius bus.
- Device status reports normal operation.
- Apollo started after the latest reboot.
- The remote client is actually sending controller input.

Fix Apollo not detecting ViGEmBus
If Apollo says ViGEmBus is not installed, reboot first and restart Apollo as a normal user. Close DS4Windows, other streaming hosts, mappers and virtual-controller tools so they cannot obscure the test.
If the bus is missing, run the official installer once. If duplicate or old entries remain, uninstall ViGEmBus from Installed apps, reboot, check Device Manager for leftover Nefarius bus entries, and reinstall v1.22.0. Do not remove unrelated HID, Bluetooth, Xbox or physical controller drivers.

Apollo ViGEmBus error matrix
Choose the smallest repair that matches the symptom. Apollo only needs a restart in some cases, while a missing kernel device requires driver repair.
| Symptom | Likely cause | Next step |
|---|---|---|
| Apollo says ViGEmBus is not installed | Driver missing or Apollo started before reload | Reboot, verify Device Manager, restart Apollo |
| Driver listed but gamepad fails | Stale session or tool conflict | Close controller tools and restart Apollo |
| Yellow warning icon | Damaged driver/device state | Uninstall, reboot, reinstall v1.22.0 |
| Two controllers in game | Physical and virtual pads both exposed | Review hiding and mapping settings |
| Installer offers remove/repair | Existing package registered | Use normal repair/removal, reboot, install once |
What not to do when Apollo gamepad support fails
Do not assume a new Apollo build requires an unofficial ViGEmBus fork. Apollo changes independently, while the original ViGEmBus repository is archived. Use the verified final driver unless Apollo's current official notes explicitly require something else.
Do not delete every Nefarius or HID-related device. HidHide, Bluetooth adapters, physical pads and virtual buses have different jobs. Broad deletion can turn one Apollo issue into a larger controller problem.
- Do not use a similarly named EXE from a mirror.
- Do not mix an old MSI with the final EXE.
- Do not skip the reboot between removal and reinstall.
- Do not treat an Apollo web-login problem as a ViGEmBus problem.
Final checklist before testing Apollo again
Test in a controlled order: verify Device Manager, start Apollo, connect the remote client, and launch a game last. This sequence shows which layer fails.
If the virtual controller works in Windows but not in one game, ViGEmBus is probably functioning. Check that game's controller mode, Steam Input, focus and supported controller type before reinstalling the driver again.
- Official ViGEmBus 1.22.0 installed from nefarius/ViGEmBus.
- Windows restarted after installation or removal.
- The Nefarius bus works in Device Manager.
- Apollo restarted after the driver became available.
- Only one intended virtual controller appears during testing.
Apollo and ViGEmBus FAQ
Does Apollo install ViGEmBus automatically?
Apollo packaging may include or reference controller dependencies, but verify the Windows driver independently. This guide uses the final official ViGEmBus 1.22.0 release as the known source.
Why does Apollo say ViGEmBus is not installed after installation?
Apollo may have started before the driver loaded, Windows may need a reboot, or a duplicate/damaged bus may exist. Verify Device Manager, reboot, then restart Apollo.
Can Apollo work without ViGEmBus?
Video streaming can work, but controller input that must appear as a virtual Xbox 360 or DualShock 4 device needs a compatible virtual bus path.
Should I downgrade ViGEmBus for Apollo?
Do not downgrade by default. Use the final official v1.22.0 release unless Apollo's current official documentation explicitly requires another version.
Is this a direct installer link?
Yes. The button points to the verified GitHub release asset from nefarius/ViGEmBus, not a mirror or repackaged installer.
Official sources used
Product and safety facts on this page are checked against first-party material. External sources open in a new tab.
- Apollo official GitHub repository — project source, issue context and official repository media
- ViGEmBus v1.22.0 official release — final release metadata and verified installer asset
- Nefarius ViGEm end-of-life notice — retirement and legacy updater context