How to Resolve Error Code 0x80070422 on Windows 10

NDIS or Network Driver Interface Specification is a programming interface for the network interface cards that aids in the proper functioning of a system driver in a computer network. The NDIS helps the computer system in order to communicate with other connected devices and hardware components on a computer network. In relation, the ndis.sys file is a critical system file developed by Microsoft for the Windows operating system. As you know, sys files or system files are important parts of the Windows operating system as well as a repository of system driver settings used by Windows to communicate with the connected hardware and devices. The ndis.sys files are stored mostly in a driver folder at C:/Windows/System32/drivers and as mentioned, these files are essential for the system to function properly. Although the presence of ndis.sys system file is not yet known to affect the normal functioning of the Windows OS, some of the Windows 10 users reported that they encountered ndis.sys blue screen errors on their PCs. Blue Screen of Death errors or Stop errors usually occurs when you open a program or a function. Moreover, it could also occur when the driver gets loaded during the system startup or during system shutdown. It isn’t yet clear what really causes the ndis.sys blue screen error. However, like other Stop errors, it may occur due to corrupted files, misconfigured device drivers, bad drivers, corrupted Windows Registry, missing or damaged system files, and malicious programs. Aside from the aforementioned reasons, the ndis.sys blue screen error might also occur if your hard disk is damaged and if the RAM is corrupted. In such cases, a lot of users usually disable the ndis.sys file. However, it won’t really resolve the issue since the file is required for the normal functioning of the operating system and even when you disable the file, it’s pretty useless as the file will start all over again. In addition, you might want to disable security programs or firewalls and antivirus programs in the meantime to check if these programs are the ones that are causing the error. And if you’ve determined that none of the security programs or firewalls and antivirus programs are to blame, refer to the options below that might help you resolve the DRIVER_IRQL_NOT_LESS_OR_EQUAL or ndis.sys Blue Screen of Death error.

Option 1 – Try to update or reinstall the PC device driver

The Ndis.sys Blue screen error can occur when the device driver in your computer is outdated or corrupted. Thus, you either have to update or reinstall it to fix the issue.

• Tap the Win + R keys to launch Run.
• Type in devmgmt.msc into the box and tap Enter or click OK to open the Device Manager.
• After that, a list of device drivers will be displayed. If you see a red or yellow sign that shows up against the driver, right-click on the driver’s name and select “Update Driver Software” or “Uninstall”. And if you find any “Unknown device”, you need to update it as well.
• Select the “Search automatically for updated driver software” option and then follow the instructions to complete the process.
• Restart your PC.

Option 2 – Rollback your Network drivers

If you have updated the driver software as of late and you suddenly got this BSOD error, you might have to roll back the device driver – in other words, switch back to the previous working version. To do that, follow these steps:

• Tap the Win + R keys to launch the Run window and then type in the “devmgmt.msc” command and hit Enter to open the Device Manager window.
• Under the Device Manager, you will see a list of drivers. From there, look for the Network Adapters and expand it.
• Next, select the driver entries that are labeled appropriately other than anything in the context of the WAN Miniport.
• Then select each one of them and double-click to open a new mini window.
• After that, make sure that you’re on the Driver tab and if you are not, just navigate to it then click the Roll Back Driver button to switch back to the previous version of your Network adapters.
• Now restart your computer to successfully apply the changes made.

Option 3 – Try running the System File Checker

The SFC or System File Checker scan could detect and automatically repair damaged system files that could be causing the ndis.sys Blue Screen of Death error. SFC is a built-in command utility that helps in restoring corrupted files as well as missing files. It replaces bad and corrupted system files with good system files. To run the SFC command, follow the steps given below.

• Tap Win + R to launch Run.
• Type in cmd in the field and tap Enter.
• After opening Command Prompt, type in sfc /scannow and hit Enter.

The command will start a system scan which will take a few whiles before it finishes. Once it’s done, you could get the following results:

1. Windows Resource Protection did not find any integrity violations.
2. Windows Resource Protection found corrupt files and successfully repaired them.
3. Windows Resource Protection found corrupt files but was unable to fix some of them.

Option 4 – Try running the CHKDSK utility

Running the CHKDSK utility might also help you resolve the Netwtw04.sys failed BSOD error. If your hard drive has issues with integrity, the update will really fail as the system will think that it’s not healthy and that’s where the CHKDSK utility comes in. The CHKDSK utility repairs hard drive errors that might be causing the problem.

• Open Command Prompt with admin privileges.
• After opening Command Prompt, execute the following command and hit Enter:

chkdsk /f /r

• Wait for the process to be completed and then restart your computer.

Option 5 – Run the DISM Tool

The DISM tool is another command-line tool in the Windows operating system that could help users fix various corrupted system files. To use it, follow these steps:

• Open the Command Prompt as admin.
• Then type in this command: DISM /Online /Cleanup-Image /RestoreHealth
• The DISM command you entered will repair the corrupted system image. Do not close the window if the process takes a while as it will probably take a few minutes to finish.
• Restart your PC.

Option 6 – Perform a System Restore

Performing a System Restore on your computer can also help you fix the ndis.sys Blue Screen of Death error. You can do this option either by booting into Safe Mode or in System Restore. If you are already in the Advanced Startup Options, just directly select System Restore and proceed with the next steps. And if you have just booted your PC into Safe Mode, refer to the steps below.

• Tap the Win + R keys to open the Run dialog box.
• After that, type in “sysdm.cpl” in the field and tap Enter.
• Next, go to the System Protection tab then click the System Restore button. This will open a new window where you have to select your preferred System Restore point.
• After that, follow the on-screen instructions to finish the process and then restart your computer and check if the problem is fixed or not.

The ntkrnlmp.exe file is a file associated with the Windows operating system’s NT Kernel and other system processes. It is also related to the “CRITICAL PROCESS DIED” error. So if you encounter a Blue Screen of Death error that’s related to this file, then you’ve come to the right place as this post will guide you in fixing the ntkrnlmp.exe Blue Screen error. This kind of Blue Screen error might be caused by the file getting corrupted or infected with some malware. Aside from these causes, the error might also be due to the corruption and malfunction of the graphics card drivers. Before you troubleshoot the problem, you might want to try performing System Restore especially if you tend to create a System Restore point every now and then. Performing System Restore could help you resolve the ntkrnlmp.exe Stop error. You can do this option either by booting into Safe Mode or in System Restore. If you are already in the Advanced Startup Options, just directly select System Restore and proceed with the next steps. And if you have just booted your PC into Safe Mode, refer to the steps below.

• Tap the Win + R keys to open the Run dialog box.
• After that, type in “sysdm.cpl” in the field and tap Enter.
• Next, go to the System Protection tab then click the System Restore button. This will open a new window where you have to select your preferred System Restore point.
• After that, follow the on-screen instructions to finish the process and then restart your computer and check if the problem is fixed or not.

If System Restore didn’t help, then proceed to the given options below.

Option 1 – Disable the C-states and EIST in the BIOS

The first thing you can do is try to disable the C-states and EIST in the BIOS. To do that, refer to the steps given below.

• Go to the BIOS and from there look for an option named CPU Configuration which can usually be found under the Advanced menu.
• Next, look for CPU Power Management and under that section, disable both the “Intel EIST” and “Intel C-state” options.
• After you disable them, save the changes you’ve made and exit the BIOS.
• Now restart your computer and check if the ntkrnlmp.exe BSOD error is now fixed.

Option 2 – Try to update, rollback or disable drivers

If the first option didn’t help in fixing the ntkrnlmp.exe Blue Screen error the next thing you can do is to roll back, or update, or disable device drivers in your computer. It is most likely that after you updated your Windows computer that your driver also needs a refresh. On the other hand, if you have just updated your device drivers then you need to roll back the drivers to their previous versions. Whichever applies to you, refer to the steps below.

• Open the Devices Manager from the Win X Menu.
• Then locate the device drivers and right-click on them to open the Properties.
• After that, switch to the Driver tab and click on the Uninstall Device button.
• Follow the screen option to completely uninstall it.
• Finally, restart your computer. It will just reinstall the device drivers automatically.

Note: You can install a dedicated driver on your computer in case you have it or you could also look for it directly from the website of the manufacturer.

Option 3 – Configure the Driver Verifier Manager

The Driver Verifier Manager is another tool in Windows that could help you fix driver-related issues. And so if you want to fix the ntkrnlmp.exe Blue Screen error you need to use the Driver Verifier Manager:

• Type in the keyword “Verifier” in the Cortana search box to search for Verifier in Windows 10.
• After that, select the option “Create custom settings”.
• Make sure that you have checked everything except the options “DDI compliance checking” and “Randomized low resources simulation”.
• Next, select the option “Select driver names from a list” option.
• Afterward, you have to select all the drivers from any unofficial or third-party provider. To simply put it, you have to select all the drivers that are not supplied by Microsoft.
• Then click on the Finish button.
• Open Command Prompt as administrator and execute this command – verifier /querysettings
• The command you just executed will display the Driver Verifier settings so if you see any of the flags enabled boot your Windows 10 PC into Safe Mode.
• Open the Command Prompt as admin again and run this command – verifier /reset
• The command will reset the Driver Verifier. Once the process is done, restart your PC and check.

Option 4 – Run the Blue Screen Troubleshooter

The Blue Screen troubleshooter is a built-in tool in Windows 10 that helps users in fixing BSOD errors like ntkrnlmp.exe. It can be found on the Settings Troubleshooters page. To use it, refer to these steps:

• Tap the Win + I keys to open the Settings panel.
• Then go to Update & Security > Troubleshoot.
• From there, look for the option called “Blue Screen” on your right-hand side and then click the “Run the troubleshooter” button to run the Blue Screen Troubleshooter and then follow the next on-screen options. Note that you might have to boot your PC into Safe Mode.

By default inside Windows 11 in File Explorer, once the file is selected, the small check box will appear beside it on left indicating visually that the file is selected. Older users will remember this feature from old Windows Vista and the feature itself is great if you are on some sort of touch device and need to select multiple files. However, if you are working on a computer with a keyboard and mouse this feature might annoy you and seem like something that is not needed. Like many things inside Windows 11 this feature also can be customized and turned OFF if you do not want it. In this guide, we will see how to turn these boxes off. Microsoft has somewhat hidden this feature but luckily it is not difficult to find it if you know where to look.

Turning check boxes OFF

1. Open File Explorer (if you do not have an icon on your Taskbar, right-click on the Start button and select File Explorer from the menu)
2. Click on View on the top toolbar
3. Select Show
4. Uncheck Item Check Boxes

That is everything that needs to be done, after the checkbox is unchecked all check boxes from File Explorer will disappear. If you wish to turn boxes back ON, just follow the steps and check the box beside Item Check Boxes.

We’ve already covered disabling Security Questions If you want to disable Security Questions on your Windows 10 computer then you’ve come to the right place as this post will guide you in doing exactly that. In this post, you will be disabling Security Questions using a PowerShell script. This PowerShell script is called “Update-AllUsersQA”. It is designed to remove or disable the security questions and answers for local users on a Windows 10 computer. It lets administrators take control of the security questions in the environment and at the same time minimizes the risk that comes with them. If a user has a Microsoft account that’s configured to sign in to Windows 10 then he will not probably notice the Password Recovery questions. On the other hand, if he has a chosen local account for installing Windows, he will e prompted to create three security questions that can be used to reset the password and log into the Windows 10 account in case there is any misfortune. However, if you do not have much use for these Security Questions, then you can definitely have them disabled using a simple PowerShell script which you can download from GitHub. For more details on how to disable security questions in a Windows 10 machine, refer to the steps provided below. Step 1: You need to first download the .ps1 file from the GitHub repository. Step 2: Once you’ve downloaded the file, open the PowerShell window with admin privileges. Step 3: After that, navigate to the folder where you had saved the .ps1 file. Then copy the address of the folder location. Step 4: Next, change the directory by using the following command:

cd "folder location address"

Step 5: After that, enter the following script to disable the security questions:

Update-AllUsersQA

Once you’ve completed the steps above, the Security Questions should be disabled and you will be notified with a message stating that the feature has been disabled. On the other hand, if you have a change of heart and you want to enable the Security Questions back, here are some steps you need to take: Step 1: First, open the PowerShell window as admin. Step 2: Next, run the same script with one more parameter such as:

Update-AllUsersQA -answer SecretAnswer

Step 3: And that’s about it. Do not forget to replace the Secret Answer with your preferred one and once you’re done, it will be set as the answer for all the Security Questions. Step 4: Now all that’s left to do is go to the Settings app to change the answer to the questions and you should be good to go.

If you are checking for an update on your Windows 10 PC and you got the error 0x80070005 due to some ACCESS DENIED permissions issue, then read on as this post will show you what you can do to fix the problem. For some reason, the Windows Update does not have enough rights or permissions to continue further which is why you’re getting an error instead. Thus, the first thing you can do before you troubleshoot further is to make sure that you’re logged in as admin. However, if you’re already logged in as one, then here are some suggestions that might help you fix the Windows Update Install Error 0x80070005.

Option 1 – Restart your computer and try installing the Updates again

You can restart your computer and then try installing the updates once again. There are instances when a simple restart resolves Windows Update errors. Thus, after you restart your computer, check for updates once again and see if you’re still getting the error or not.

Option 2 – Delete the contents in the Software Distribution folder and Catroot2 folder

• Open the WinX Menu.
• From there, open Command Prompt as admin.
• Then type in the following command – don’t forget to hit Enter right after typing each one of them.

net stop wuauserv net start cryptSvc net start bits net start msiserver

• After entering these commands, it will stop the Windows Update Service, Background Intelligent Transfer Service (BITS), Cryptographic, and the MSI Installer
• Next, go to the C:/Windows/SoftwareDistribution folder and get rid of all the folders and files thereby tapping the Ctrl + A keys to select them all and then click on Delete. Note that if the files are in use, you won’t be able to delete them.

After resetting the SoftwareDistribution folder, you need to reset the Catroot2 folder to restart the services you just stopped. To do that, follow these steps:

• Type each one of the following commands.

net start wuauserv net start cryptSvc net start bits net start msiserver

• After that, exit Command Prompt and restart your computer, and then try to run Windows Update once more.

Option 3 – Try running the Windows Update Troubleshooter

Running the built-in Windows Update troubleshooter is one of the things you can first check out as it is known to automatically resolve any Windows Update errors like error 0x80070005. To run it, go to Settings and then select Troubleshoot from the options. From there, click on Windows Update and then click the “Run the troubleshooter” button. After that, follow the next on-screen instructions and you should be good to go.

Option 4 – Take control of the User App Data

There are times when permission to access the files is not configured correctly. As a result, it blocks the downloading of the updates. Thus, you have to take full control of the User App Data which is placed at C:/Users/USERNAME/AppData.

• First, go to C:/Users/USERNAME/AppData and right-click on it then select Properties.
• Next, click on the Edit button in the Properties window and click OK to confirm if you got a User Account Control elevation request.
• After that, select user/group from the permission windows or click on the Add button to add another user or group. It would be best if you add “Everyone” to give permission.
• Then check “Full Control” under the “Allow” column to assign full access rights control permissions.
• Now edit the permission to Full Control for “Everyone”.
• Click OK to save the changes made and then exit.

Option 5 – Try to update Windows after a couple of minutes or an hour

There are times when the issue is from Microsoft’s end. It could be that there’s some issue with Microsoft’s server so it would be better if you give it a couple of minutes or an hour or so before trying to run Windows Update again.

Universal Windows Platform (UWP) applications are the modern application in the windows store that can be used in all the Window devices like Xbox, Hololens, Tablet, PC or Phone. Basically, UWP provides a common platform for every device that runs Windows 10. When attempting to login into these applications and receive this error:

Can’t sign in with a Microsoft account This program is blocked by group policy. For more information, contact your system administrator. 0x8000704ec

Then this post is for you. We will guide you on how to easily resolve issues, please follow the steps provided.

1. Local group policy editor solution

   • Press ⊞ WINDOWS + R to open the Run dialog.
   • In the Run dialog box type gpedit.msc and press ENTER to open Group Policy Editor.
   • Inside the Local Group Policy Editor, navigate to the path below:
   Computer Configuration > Windows Settings > Security Settings > Local Polices > Security Options
   • On the right pane, double-click on Accounts: Block Microsoft accounts to edit its properties.
   • Under Local Security Setting tab, click on the drop-down and select This policy is disabled.
   • Click Apply > OK to save the changes.
   • Exit Group Policy Editor.

2. Registry editor solution

   As always, it is highly recommended to make a backup of the registry editor just in case that something goes wrong.
   • Press ⊞ WINDOWS + R to open the Run dialog.
   • In the Run dialog box, type regedit and hit ENTER to open Registry Editor.
   • Navigate to the registry key path below:
   HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System
   • At the location, on the right pane, identify the NoConnectedUser key. The key value might be set to either 1 or 3.
   • Now, double-click the NoConnectedUser entry to edit its properties.
   • Input 0 in the Value data field and hit Enter to save the change.

One of the important functions in the Windows operating system is the Task Scheduler. It can automatically run various tasks at a certain time where you’ll have to add a task that needs to be executed and then choose the time it has to run at. So when that time comes, the Task Scheduler will run the task automatically. However, some users reported getting an Error 0x80070057 where the Task Scheduler fails to start. This kind of error may be due to a disabled service that prevents the service from running. It is also possible that the antivirus program interfered with the task – it could be that the Task Scheduler is somewhat in the block list since the antivirus adds it to the list automatically when it’s installed. On the other hand, it could be that you lack administrator-level privilege which is why the Task Scheduler was not able to carry out the task. To fix this issue, here are some suggestions you can try.

Option 1 – Try to restart the Task Scheduler service

As mentioned, it is possible that the Task Scheduler service could be disabled. You could have disabled it when trying to enhance your computer’s performance and whatnot. Thus, you need to verify if it’s running or not and then restart it.

• First, you need to tap the Win + R keys on your keyboard to open the Run dialog box.
• Next, type “services.msc” in the field and click OK or tap Enter to open the Windows Services Manager.
• You will see a list of Services and from there, look for the Task Scheduler service and double click on it.
• After that, go to the General tab and click on the Startup Type options and then select “Automatically” from the given list.
• Click on the “RUN” option and select the “Restart the Service” option.
• And click on the “After Second Failure” option and then select the “Restart-Service” option again.
• Now click on the “After Subsequent Failures” tab and select the “Restart the Service” option.
• Finally, click on the Apply and OK buttons and then run the Task Scheduler and see if the issue is now fixed.

Option 2 – Try to temporarily disable the anti-virus program

As mentioned, the error could be due to the antivirus program or the Windows Defender Firewall installed in your computer. Thus, disabling them or any security software installed on your computer is always a good idea you can try when you’re not able to access the shared drive on your computer. There are times when you encounter problems like the Task Scheduler Error 0x80070057 due to interference of antivirus or security programs. Thus, you have to disable both your antivirus program for the meantime and check if it fixes the error or not.

Option 3 – Run the Task Scheduler with an administrator account

Like pointed out, the Task Scheduler Error 0x80070057 may be due to the lack of admin privileges. Thus, you have to log in to an administrator account and try running the Task Scheduler again. It is also recommended that the administrator account you’re going to use as a password when logging in.

Option 4 – Repair the Task Scheduler by deleting corrupted tasks

Note that a single corrupted file can cause big problems so this option is quite important. And for you to delete a corrupted task or any task from the Task Scheduler, you have to use the Registry Editor if you are not able to use the Task Scheduler interface. To do so, follow these steps:

• Tap the Win + R keys to open the dialog box for Run.
• Next, type in Regedit and click on OK or tap Enter to open the Registry Editor.
• Then navigate to this path: ComputerHKEY_LOCAL_MACHINESOFTWAREMicrosoftWindows NTCurrentVersionScheduleTaskCacheTree

Note: In this path, you can see all the tasks that are currently set in the Task Scheduler. And since it would be hard to tell which one of them is corrupted, you have to delete the latest one in Task Scheduler last. But before you do so, make sure that you take note of the ID of the tasks. And for you to get the ID, you have to select the task you wish to delete and double click on the ID string located on your right-hand side, and then copy it in the Notepad.

• Right-click on the task name and then delete it.
• After that, delete the very same GUID which you have copied earlier from these folders:
• ComputerHKEY_LOCAL_MACHINESOFTWAREMicrosoftWindows NTCurrentVersionScheduleTaskCacheBoot
• ComputerHKEY_LOCAL_MACHINESOFTWAREMicrosoftWindows NTCurrentVersionScheduleTaskCacheLogon
• ComputerHKEY_LOCAL_MACHINESOFTWAREMicrosoftWindows NTCurrentVersionScheduleTaskCacheMaintenance
• ComputerHKEY_LOCAL_MACHINESOFTWAREMicrosoftWindows NTCurrentVersionScheduleTaskCachePlain
• ComputerHKEY_LOCAL_MACHINESOFTWAREMicrosoftWindows NTCurrentVersionScheduleTaskCacheTasks

Note: You might not see the same GUID from these folders but if you see it, delete it right away.

• Next, navigate to this location: C:/Windows/System32/Tasks
• Delete the very same tasks you just deleted from the Registry Editor.
• Restart your PC and check if the Task Scheduler is back to its normal state or not.

Microsoft's anniversary update has come with many new features and improvements. One of these features is that Microsoft's Cortana can now be installed on your Android phone and as long as you are logged in to your Microsoft account on different devices, she can pass information between devices. You can not see battery life on your desktop PC, notifications, etc. There are some prerequisites in order to get this going, first is to have a Windows version 1607 or newer. The second is to have the last Android version

Installing Cortana on Android

1. Download and install the Cortana app from the Google Play store.
2. Open the app and accept the license terms.
3. Enter the credentials for the Microsoft account you use to sign in to your PC.
4. After a few seconds, Cortana will open.
5. Click the settings button and select Sync Notifications.
6. By default, missed calls, incoming messages, and low battery notifications will be turned on. You can turn this on\off from here. The only option off by default is for App notifications. Any non-system apps such as Facebook and Instagram can also send alerts to your Windows box. You can choose to enable the App notification sync option or leave it off.
7. If you enable “App notification sync,” you will need to give Cortana permissions to read and control notifications on your phone.
8. You can then select exactly which applications will be synched to your PC.
9. Once done you can exit out of Cortana.

Configuring Cortana on PC

1. Click the Windows button and type Cortana. Click the icon for Cortana and Search Settings.
2. Scroll through the settings list and look for Send notifications between devices
3. Click the switch to turn it on.
4. Sign in to the same Microsoft account you used in the previous section
5. Navigate back to the Cortana & Search settings tool.
6. Click Edit Sync Settings. Make sure that your phone shows up on the list. You can also determine if you want PC notifications are sent to your phone.

With those settings in place, you should now start getting alerts for the items you enabled in your Action Center. As notices come in, you will see them pop up in a small bubble on the lower right of your screen. You can dismiss the notification or use the link to find a compatible app in the Windows store.

As you know, USB is now being widely used in all devices with USB A as the leading type with most devices based on it. Peripheral devices such as Pen Drives, External Hard disks, and many more also use a USB port. On the other hand, USB C is also coming up to be the next big standard in the computing world because of its high transfer speeds, wider compatibility as well as support for external Graphics Processing Units. However, just recently, USB 3.0 ports have been reported to cause the following error to pop up on Windows 10 computers every time a USB device is plugged in.

“Not enough USB controller resources. The controller does not have enough resources for this device.”

To fix this error, here are some guidelines you can check out. Make sure to follow them carefully.

Option 1 – Try to use a lower generation USB port

The first thing you can do is to try using a lower generation USB port as this issue mostly occurs when a device is connected to a USB 3,0 port. This means that you have to plug in your device to a USB 2.0 port and then see if it fixes the error or not. You can easily decipher a USB 3.0 port from a USB 2.0 port as the former is in blue.

Option 2 – Try to use a dock

You could also try to use a dock to resolve the error. Note that when too much power on laptops and notebooks are drawn from the USB ports and as a USB 3.0 port draws more power compared to a USB 2.0 port. Thus, if you plug in your USB storage device into a USB 2.0 port with the help of a dock, it should fix the problem.

Option 3 – Try disabling the xHCI Mode option in the BIOS

• First, boot your computer into the BIOS.
• Once your computer has booted, go to the Advanced tab.
• Next, make sure that the entry for “xHCI Pre-boot mode” is set to Disabled under the USB Configuration section.
• Now save the changes you’ve made and then restart your computer to Windows 10 and see if the error is now fixed.

Option 4 – Update or reinstall the Universal Serial Bus Controller driver

Since it could be a driver issue, you can try to update or reinstall the Universal Serial Bus Controller drivers using the Device Manager. Refer to the following steps:

• First, click the Start button and type “device manager”.
• Then click on the “Device Manager” from the search results to open it.
• From there, look for the “Universal Serial Bus controllers” option and then right click on each one of the USB drivers, especially the Generic USB Hub driver, and then select the Update Driver from the menu.
• Restart your PC and then click the “Search automatically for updated driver software” option.

Note: If updating the USB Controller drivers didn’t work, you can try to reinstall them instead.

Option 5 – Run the Hardware and Devices Troubleshooter

You could also run the Hardware and device Troubleshooter to try and fix the “Not enough USB controller resources” error.

• The first thing you need to do is click on Start and then on the gear-like icon to pull up the window for Settings.
• After opening Settings, look for the Update and Security option and select it.
• From there, go to the Troubleshoot option located on the left-hand side of the list.
• Next, select Hardware and Devices from the list and open the Troubleshooter and run it. Once it is doing its job, wait for it to complete the process and then restart the system.
• After the system restarts, check if the problem’s now fixed. If not, refer to the next option given below.