The affected user encounters the error when he tries to pair the controller with the system. In some cases, the user encountered the error after using the controller for a long time, whereas other users faced the issue while setting up the device for the first use. Some users encountered the issue only with the external Bluetooth dongles. Before moving on with the solutions, make sure the Bluetooth module of your system is working fine (try to use a Bluetooth headset or another device). Moreover, restart your controller/system and then try to pair the devices. If the issue is occurring with the Steam client, try to use the Big Picture mode of the client. Moreover, it is always a good idea to unpair the controller from Windows after you are done with gaming.
Solution 1: Re-Pair the Devices and Sync Through the WiinUSoft Application
A temporary software/communication glitch can be the reason for the issue at hand. The glitch can be cleared by Re-Pairing the devices.
Solution 2: Enable Service for HID for the Controller
The Controller is a Human Interface Device and it must be set up as one. You may encounter the error under discussion if the HID service is not enabled for your controller. In this context, enabling the HID device service may solve the problem.
Solution 3: Change Start Up Type of Related Services to Manual
Some system services are essential for the operation of your controller. You may encounter the error at hand if these services are stuck in an error state. In this context, setting the startup type of theses services to the manual may solve the problem.
Solution 4: Disable Xboxstate.exe at System Startup
XBoxstate.exe is used to emulate your controller and make it as a 360 controller. You may encounter the error at hand if the XBoxstate.exe is stuck in the operation. In this case, force closing the process of the executable may solve the problem.
Solution 5: Add the Device Through the Personal Area Network
Since Creators Update, Bluetooth devices without PIN could not be paired with Windows machines. In this context, setting up the controller through the Personal Area Network of the Bluetooth settings (PIN will not be required) may solve the problem.
Solution 6: Update the WiinUSoft Application
WiinUSoft is updated regularly to satiate the technological advancements and improve performance by patching the known bugs. You may encounter the error under discussion if you are using an outdated version of the software. In this context, updating the software to the latest build may solve the problem.
Solution 7: Revert the Windows Update
Microsoft has a history of buggy updates. You may encounter the error under discussion if a buggy update of Windows has broken the operation of the controller. In this context, reverting the update may solve the problem.
Solution 8: Use WinSCP Service
WinSCP service is used to forward the controller input to Xbox Xinput. You may encounter the error at hand if you have not installed the WinSCP driver with the controller software. In this context, installing the WinSCP driver may solve the problem.
Solution 9: Install the Toshiba (Dynabook) Bluetooth Stack After Disabling the Driver Signature Enforcement
The WiinUSoft application was built on Toshiba Stack. Although, in the recent version of the application, Microsoft stack is also supported. But you may encounter the error at hand if your controller is having issues with the Microsoft stack. In this context, using the Toshiba Stack may solve the problem. If you are still having issues to pair the controller and system, then try to use Mayflash
Pairing Failed: Your Apple Watch Couldn’t Pair with Your iPhone [FIX]How to Pair Xbox One S Controller with Xbox One Controller DongleApple May Pair HomePod Mini and Apple TV in Tandem To Allow Better SmartHome…How to Pair Your Smartwatch with Android Phone
