Win10 x64 1809 (17763.437)
Secure Boot On
All Checks OK
Posts made by Daltz333
RE: Computer can't go to sleep while Shibari is running
Shibari is legacy software, meaning it currently is receiving no updates. However, a better standalone driver is currently in the works and should solve this issue. Sorry that you have to deal with it in the meantime
RE: Bluetooth disconnects after 1-2 hours of playing
What Bluetooth dongle do you use? Also Airbender is known to be unstable, and a much better successor is in-development.
x360ce to ViGEm
VDX is a ViGEm Feeder Application designed to create a System-Wide XBox360 or DualShock 4 Gamepad.
- Windows 7 is the minimum OS version. Don't expect anything lower to be able to work
- This guide assumes you use the "legacy" (currently still stable) version 3.x of x360ce!
- Setup ViGEm Bus Driver if you haven't already
- Download and Install
Microsoft Visual C++ Redistributable for Visual Studio 2017
- Download and Install all of x360ce required dependencies. A list can be found here
- Please grab the appropriate build for your version of Windows. If in doubt, choose 32-Bit (x86) builds.
- Download the latest VDX application from here (select the highest version number for the latest edition)
- Download the latest x360ce application from here
It's not that hard. I swear!
Attention: Extract x360ce to its own folder and copy VDX into the same folder (e.g.
Downloads\x360ce). The only things that should be in this folder are the x360ce application (and any files it generates) and the VDX application. Do NOT copy these files into any game directories like you might be used to.
- Open the x360ce_x64 application and create the DLL that it prompts you to.
- You will be prompted to search the internet for default settings. Press next and finish through the dialog.
- Configure your joystick controls.
- In some cases where VDX does not detect your controller, you may need to press the
autobutton in the bottom right of the application before you modify the controls.
- Save and close out of x360ce
Open VDX and press connect
[Pad0] Misconfigured Device, check GUIDs
Delete x360ce.ini and xinput1_3.dll from the application directory and relaunch x360ce
HidGuardian v1 driver installation
This article covers the installation of the (deprecated) HidGuardian major version 1 (a.k.a. Gen1) driver. Its development has been discontinued yet there's software out there depending on it. Please make sure you need version 1 first before going through this article!
HG) v1 is very limited in functionality. It was more of a proof of concept (PoC) than a full blown product. Nonetheless it can still assist you in blocking input devices which is its core intention.
If you're a developer starting with a fresh project, please refrain from using
HGv1 as it won't receive any new features or fixes, thank you!
Some facts about
- Configured via registry keys and values
- Can only whitelist processes based on PID (numeric Process ID)
- Has no real "official" API so might break between minor releases
This list is in no way complete as we rely on community/developer feedback. Some known products include:
Grab the driver archive matching your systems architecture from here and extract them (e.g. to
Some morons/trolls might have told you that you have to put drivers into
system32folder. Don't do that, Windows can take care of its drivers by itself, fooling around in your system folders can brick your machine. You have been warned.
Now get the Device Console (devcon) utility and also extract it somewhere (e.g. to
So the folder structure you end up with should look like so:
Alright, here we go take one last deep breath and continue reading carefully and nothing will go wrong.
Fire up PowerShell as Administrator and insert the following commands one after another:
C:\hg\devcon\x64\devcon.exe install C:\hg\x64\HidGuardian.inf Root\HidGuardian
Which is expected to return:
Device node created. Install is complete when drivers are installed... Updating drivers for Root\HidGuardian from C:\hg\x64\HidGuardian.inf. Drivers installed successfully.
This command created a virtual "dummy device" so the driver can get loaded.
C:\hg\devcon\x64\devcon.exe classfilter HIDClass upper -HidGuardian
Which is expected to return:
Class filters changed. Restart the devices or reboot the system to make the change effective. HidGuardian
This command internally adjusted some registry values causing the driver to get loaded onto every input device automatically.
That's it! You're ready to rock
You'll either need to unplug and plug in your input devices or reboot the machine for the driver to work!
HGrequires a special procedure described here or else you could end up with no keyboard/mouse!
For removal you don't need the original driver files, you will need
devconthough so make sure you got it ready as described earlier.
Then from an elevated PowerShell execute:
C:\hg\devcon\x64\devcon.exe classfilter HIDClass upper !HidGuardian C:\hg\devcon\x64\devcon.exe remove Root\HidGuardian
It might have accidentally happened that your system has more than one virtual device. If that's the case, simply execute the two commands multiple times until they're all gone.
Now reboot and you're good to go
Some registry keys and values can be safely removed manually after the driver is gone.
Computer\HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\HidGuardian\Parametersthe following values can be removed (if they exist):
Computer\HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\HidGuardian\Parameters\Whitelistand all sub-keys can be removed as well.