How to Install or Remove Nefarius Drivers and Tools

Nefarius Project Documentation covers several independent projects, and each one has its own install or removal path rather than a single universal procedure. Use the project-specific guide listed below: DsHidMini, BthPS3, HidHide, ViGEm, and Shibari have dedicated installation material, while AirBender, FireShock, ScpToolkit residue, and ViGEm have removal or cleanup material. Before starting, confirm which project you actually need, because these tools target different problems (USB input device emulation, Bluetooth PS3 controller support, device hiding, virtual gamepads, and so on).

Find the right guide first

The documentation is organized by project, not by task. If you are unsure which project applies to your setup, check the project's "About" page before touching any installer.

Installing: what the guides expect

Installation pages generally assume you already know which project you want and have the matching hardware or software prerequisite in place. The steps differ per project, so follow the specific page rather than a generic sequence.

• DsHidMini splits installation by major version (V2 and V3). Pick the version matching your setup before following the install steps, since the modes and configuration differ between them.
• BthPS3 uses a "Shibari Edition" installation guide, which ties into the separate Shibari project.
• HidHide has a simple setup guide for normal use and a separate manual installation page specifically for ARM64 systems. If you are on ARM64, use the manual path.
• ViGEm has a combined "How to Install/Remove" page, and also carries an End of Life Statement — check that before starting a new deployment.

Each install page is paired with configuration material (for example, DsHidMini's DS4 Mode User Guide or XInput Mode Explained, and BthPS3's Driver Configuration Utility Explained). Installation and configuration are treated as separate stages, so expect to finish installing before adjusting behavior.

Removing: use the project's own cleanup path

Removal is not one procedure either. Some projects ship a removal guide, and some only document manual residue cleanup.

• AirBender and FireShock each have a dedicated Removal Guide.
• ViGEm documents removal on the same page as installation.
• ScpToolkit does not have a standard uninstaller path in the documentation; instead there is a "Manual removal of ScpToolkit residue" page for leftover files.
• HidHide has a FAQ entry for "Fixing an improper removal of HidHide," which is the page to check if a normal removal left the system in a bad state.

If a removal goes wrong, look for the project's FAQ or troubleshooting entry before deleting files by hand — HidHide's improper-removal fix is the clearest example of this being documented.

Common points to verify

• Confirm the project and, where relevant, the major version (DsHidMini V2 vs V3) before installing.
• Check platform-specific notes — HidHide's ARM64 manual installation is the main one called out in the documentation.
• Treat install, configure, and remove as three distinct steps; the docs separate them.
• For ViGEm, read the End of Life Statement before planning a new install.
• If removal fails, use the documented cleanup or FAQ path rather than manual deletion.