Navigation

    ViGEm Forums

    • Register
    • Login
    • Search
    • Recent
    • Tags
    • Popular
    • Twitter
    • GitHub
    • Discord

    [OBSOLETE] Nuking ViGEm completely (thorough removal)

    Guides and Documentation
    2
    3
    10866
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • F
      Forceflow last edited by nefarius

      I found myself in a position where I had to get rid of every trace of ViGEm on a Windows 10 system, after having installed it using the PowerShell commands here. Possibly, installing and removing Parsec also leaves some of these files around.

      Uninstaller (newer versions of ViGEm)

      Run the uninstaller from the programs and features windows menu, then proceed to the driver service removal below.

      PowerShell (old versions of ViGEm)

      In an elevated PowerShell window:

      Get-ViGEmBusDevice | Remove-ViGEmBusDevice
      

      All your ViGEm devices should now be gone - check in device manager just to be sure.

      Now, to get rid of all the Powershell tools we've used to install ViGEm, use these commands in an elevated PowerShell console:

      Remove-Module ViGEmManagementModule
      Unregister-PSRepository -Name "nuget.vigem.org"
      

      If you get the error that the module is in use, make sure you close all other PowerShell windows.

      Remove driver service

      Now, to remove the remaining driver service - which is inactive and not loaded with the kernel, but still, if you want to totally get rid of all traces, use this in a Windows elevated prompt (as admin):

      sc delete ViGEmbus
      

      Now the driver service is removed and you can remove C:\Windows\System32\Drivers\ViGEmbus.sys yourself.

      This should remove all ViGEm traces from your system, and get rid of the tooling in PowerShell. Be warned: Oculus software comes with its own ViGEm driver files (prefixed by Oculus_). Don't remove them!

      1 Reply Last reply Reply Quote 0
      • nefarius
        nefarius last edited by

        Just to confirm: it is indeed safe to remove the ViGEMBus.sys binary by hand once the service is removed. Just don't try that with any other drivers on your system 😉 or it might be backup restore time 😬

        1 Reply Last reply Reply Quote 0
        • F
          Forceflow last edited by

          Updated the original post, now ViGEm has a nice installer.

          1 Reply Last reply Reply Quote 1
          • First post
            Last post