Observe and repeat carefully or you'll be left with unusable devices If your controller or Bluetooth dongle is still showing up in the libusbK node, right-click, uninstall and re-plug until it's gone for good I strongly recommend you re-plug all devices and check if they are still running under the SCP drivers! You might think that you're done now but there's a twist! A copy of the driver can still remain in memory and therefore won't be deleted. Right-click on each of those and select Uninstall:Īlternatively the section and device names may differ, depending on your specific case, like so: Open Device Manager and look for a node titled libusbK USB Devices:Įxpanding said node shall reveal the devices running under SCP's drivers: Sweet! Now we need to instruct Windows to revert the devices to their default drivers. Select those, tick the Force Deletion box on the right and then click Delete Package: The highlighted entries belong to the toolkit installation. You'll be presented with a list of drivers found on your machine: Make sure to run it with administrative permissions!
We'll use this to safely remove the driver files from the system. If you don't have enough USB ports just repeat the described steps for each device, plugging it in one after another.ĭownload and run the DriverStore Explorer tool. Have MSBuild/nmake available in PowerShellįor this procedure to work properly make sure you've got your controller(s) and Bluetooth dongle(s) connected. Vendor and Product IDs used by NSS drivers SIXAXIS/DualShock 3 native HID Report Descriptor
#Scp toolkit wireless controller how to#
How to check which architecture I'm runningįix Symbol loading for Kernel Driver minidump analysis Amazon's Choice "Pro Controller" CompatibilityĬORSAIR GLAIVE RGB native HID Report Descriptor
0 kommentar(er)
