Skip to main content

Fix: Insufficient System Resources Exist to Complete the Api Xbox Controller

Some users have been reaching us with questions after their Xbox controllers (Xbox 360 or Xbox One) have suddenly stopped working on Windows 10, Windows 8.1 and Windows 7. Most affected users report that the device is flagged with a yellow exclamation mark inside Device Manager.
Double-clicking the device and looking at the Device status (in the General tab) will reveal the following error message:

“This device cannot start (Code 10).  Insufficient system resources exist to complete the API.”
Note: This is typically reported on users that connecting a wireless Xbox 360 controller via a USB dongle.

Reasons Why Insufficient System Resources Exist to Complete the Api Error Occurs

After investigating  the issue and looking at various user reports, we have put together a list of situations where this error might occur:
  • The device driver has glitched – This is typically reported to occur after a Windows Update or if the system has recently woke from hibernation.
  • UpperFilters and LowerFilters are corrupted – These are two registry values that can become corrupted and cause the Code 10. Refer to Method 3 for steps on dealing with them.
  • Files from the controller driver became corrupted – A windows update or a third party interference might trigger the Xbox controller error.
  • Front USB cannot support the demand – This typically happens with controllers that are plugged into a front USB (via USB dongle). Usually, front USB ports don’t have the same kind of power and might not function properly with some devices.

How to Fix the ;Insufficient System Resources Exist to Complete the Api’ Error

If you’re struggling to resolve the same error message, this article will provide you with a list of effective troubleshooting steps. Below you have a list of methods that other users in a similar situation have used to get the issue fixed.
For the best results, follow the methods in the order that there are presented. Start with the first potential fix and work your way down until you discover a fix that is effective in forcing your Windows version to recognize your Xbox controller. Let’s begin!

Method 1: Unplugging the device and removing it from via the Devices screen

Some users struggling with the same kind of issue have managed to force Windows into recognizing the controller again by disconnecting the device and using the Devices screen in order to force Windows into restarting the driver that is creating the issue.
If the error is simply caused by a badly installed driver or a temporary glitch, restarting the connection of the device will resolve the issue. Here’s what you need to do:
  1. First things first, disconnect your Xbox controller by physically unplugging the USB cable. If you’re using a wireless dongle, disconnect the USB stick.
  2. With the device disconnected, press Windows key + R to open up a Run box. Next, type or paste “ms-settings:connecteddevices” and hit Enter to open the Devices tab of the Settings app.
  3. In the Devices tab, scroll down to Other devices, click on your Xbox controller and click on Remove Device.
  4. Once the device has been removed, close the Devices tab and restart your computer. After the next startup is complete, re-connect your Xbox controller and wait patiently until the setup is complete.
  5. See if the controller is functioning properly now.
If your Xbox controller is still showing the Insufficient system resources exist to complete the API error, continue down with the next method below.

Method 2: Replace Controller driver with the locally cached version

If re-creating the connection didn’t work, let’s see if you’ll have better luck by replacing the currently installed Xbox Controller driver with a locally stored copy.
Note: Keep in mind that this method is only applicable for those of you that are encountering the issue with an Xbox 360 controller.
Some users finding themselves in a similar position have managed to regain the normal functionality of their Xbox 360 controllers by using Device Manager to updating the unidentified device with the Xbox 360 Wireless Receiver for Windows Version driver which is stored locally. Here’s a quick guide on how to do this:
  1. Press Windows key + R to open up a Run box. Next, type  “devmgmt.msc” and hit Enter to open up Device Manager. If prompted by the UAC (User Account Control), accept by clicking on Yes.
  2. Inside Device Manager, right-click on your Xbox controller driver (it should be listed as an Unidentified device) and choose Properties.
  3. In the Properties screen of the device, go to the Driver tab and click on the Update Driver button.
  4. In the next screen, click on Browse my computer for driver software and then click on Let me pick from a list of available drivers on my computer.
  5. Next, select Windows Common Controller for Windows Class and then choose Xbox 360 Wireless Receiver for Windows Version : 2.1.0.1349
  6. At the Update Driver Warning, click Yes to install the outdated driver version.
  7. Once the older driver version is installed, reboot your computer and see if the issue has been resolved at the next startup.
If the issue is still occurring and you’re prevented from using your Xbox 360 controller, continue down with the next method below.

Method 3: Use a primary 2.0 USB port

If you connect your Xbox controller through a front USB, try connecting it to one of the USB ports that are present on the back. Front USB ports get treated as AUX and in case your system is struggling to keep up with the power demand, front USB ports will not have priority. This might lead to situations where certain devices will not function properly because the front port cannot support the demand.
This particular scenario is particularly common with users that connect their Xbox controller with a USB dongle. If this scenario applies to you, simply move the USB connection to a back USB port. Also, if you have USB 2.0 and USB 3.0 ports, make sure you switch the connection to the USB 2.0 port. Finally, restart your computer and see if the issue is resolved.
If you’re still encountering the same issue, continue down with the next method below.

Method 4: Deleting the UpperFilters and LowerFilters Registry values

As per various user reports, UpperFilters and LowerFilters are two registry values with the potential to crash a wide array of devices that are connected through USB ports.
Some users in a similar situation have reported that the issue was fixed after they used Registry Editor to delete these two Registry values, forcing Windows to create new ones.
Follow the instructions down below to remove the UpperFilters and LowerFilters registry values via Registry Editor to resolve the Insufficient system resources exist to complete the API error:
Note: These steps should be applicable regardless of which Windows version you’re using.
  1. Press Windows key + R to open up a new Run box. Next, type “regedit” and hit Enter to open up Registry Editor. If prompted by the UAC (User Account Control), choose Yes.
  2. Inside Registry Editor, use the left pane to navigate to the following location:
    HKEY_LOCAL_MACHINE \ SYSTEM \ CurrentControlSet \ Control \ Class
  3. In this Class subkey, each 32-digit subkey is entirely unique and corresponds to a particular hardware in Device Manager. For the purpose of resolving an Xbox controller related issue, we’ll need the USB Class GUIDs which is 36FC9E60-C465-11CF-8056-444553540000.
  4. Double-click on the 36FC9E60-C465-11CF-8056-444553540000 (USB host controllers and hubs) inside the Class subkey .
  5. With the correct Class selected from the left pane, move over to the right pane, right-click on UpperFiltersand choose Delete. Then, repeat the same procedure with the LowerFilters key.
  6. With both keys deleted, close Registry Editor and Restart your computer. At the next startup, see if the problem has been solved and you’re able to use your Xbox controller.

Comments

Popular posts from this blog

Fix: System Found Unauthorized Changes on the Firmware, Operating System or UEFI Drivers

Several users are struggling with the  System found unauthorized changes on the firmware error  at every startup or when trying to take their computer out of hibernation mode. Most affected users report that the issue started occurring after they installed some pending Windows updates. The issue is mostly encountered on Windows 7. The system found unauthorized changes on the firmware, operating system or UEFI drivers. Press [OK] to run the next boot device, or enter directly to BIOS Setup if there are no other boot devices installed. What is causing the System found unauthorized changes on the firmware error We investigated this particular issue by looking at various user reports. This error will occur whenever your system is checking the firmware one some computer hardware parts as part of a new security feature. To be precise, the error is occurring because not all Windows versions will support this new security feature. As it turns out, there are sev...

Fix: The Following Error Occurred Attempting to Join the Domain

Several users are getting the ‘ following error occurred attempting to join the domain ‘ error when trying to connect a computer to a home or work domain. Most of the time, the error is accompanied by an explanation message telling the user that it has exceeded the maximum number of computer accounts. The issue is not restricted to computers that connect to a domain for the first time, as it’s often reported to occur with PCs and laptops previously connected to the same domain. The following error occurred attempting to join the domain. Your computer could not be joined to the domain. What is causing the ‘following error occurred attempting to join the domain’ error? We investigated this particular error by looking at various user reports and the troubleshooting guides that they themselves followed to get the issue resolved. Based on what we were able to gather, there are several different scenarios that might trigger this particular error message: SMB1 support is di...

How to Fix Startup Repair Loop on Windows 7

Getting a  boot loop  which doesn’t let you go past the  Startup Repair  in Windows 7 is something that a lot of users have experienced, and it is most likely due to corrupt registry entries. It might be your mistake if you have messed around in the registry and changed a key you shouldn’t have, but it can also happen by itself, as Windows isn’t really immune to that kind of problems. No matter whether it is your fault or not, you will not be able to boot up Windows, as it will be stuck rebooting itself and won’t make it past the  Startup Repair  screen no matter what. However, there is a solution that begins at the Startup Repair screen, and uses the command prompt to fix the problem by backing up your files, and refreshing Windows, so follow the steps below to see how you can get out of the boot loop. Backup your old files and refresh your Windows In order to start the system in start-up repair, you will need either the windows installation ...