Fixing the “Failed to register a VB Script dll” Error in Windows 10

As you can notice in Blue Screen errors, most of them point out a file that’s related to the errors. One of these files is the Storport.sys file which is a system file related to the storage of data in the storage unit of a computer. This file is created by the Microsoft Storage Port Driver. So if this file ends up getting dragged on Blue Screen errors, there can be a number of reasons for why it’s happened. Blue Screen errors related to the Storport.sys file may include conflicts with the hardware, incompatible firmware issues, corrupted drivers, missing or corrupted system files, to name a few. Here are some of the common Blue Screen errors related to the Storport.sys file:

• KMODE_EXCEPTION_NOT_HANDLED
• KERNEL DATA INPAGE
• PAGE FAULT IN A NONPAGED AREA
• SYSTEM THREAD EXCEPTION NOT HANDLED
• IRQL NOT LESS OR EQUAL
• SYSTEM SERVICE EXCEPTION

Microsoft Windows is the one that provides the Storport.sys file a storage port driver that is suited especially for the use of high-performance buses like fiber channel buses and RAID adapters. There are a number of advantages in using Storport instead of the SCSI Port, according to Microsoft:

• “Improved performance, both in terms of throughput and the system resources that are utilized.
• Improved Miniport driver interface that addresses the needs of high-end storage vendors, particularly host-based RAID and fiber channel vendors.”

If you encounter any of the above-mentioned Blue Screen of Death errors, then here are some troubleshooting options that might help but before you get to them, you can try to perform a System Restore first especially if you have the habit of creating System Restore points. This might fix the problem. To perform a system restore, refer to these steps:

• First, 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 in fixing the Blue Screen error, now’s the time for you to resort to the troubleshooting tips provided below but before you get started, make sure that you create a System Restore point first. In addition, you also have to boot into Safe Mode with Networking before you carry out the troubleshooting steps below.

Option 1 – Try to update or rollback your device drivers

The first thing you can try to fix the Storport.sys Blue Screen error is to either update or roll back the device drivers. 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. Note that the main drivers that might be the cause behind the Storport.sys Blue Screen error will be listed under the “ID ATA/ATAPI controllers” section as well as the “Storage controllers” section.
• 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 also directly download the relevant drivers of your computer from the manufacturers’ website. So if you have an SSD, the issue might be due to an old storage driver. Option 2 – Try to recreate the Storport.sys file If the first option didn’t work, the next thing you can do is to recreate the Storport.sys file. Every time your Windows 10 PC boots up, it looks for all the system drivers in place and if it is unable to find them, it tries to create them. This is why if you remove your corrupt driver file, chances are, you might get a fixed file recreated just for you. How? Refer to the steps below.

• Boot your Windows 10 PC in Safe Mode.
• Then open File Explorer and navigate to this location: C:/Windows/System32/drivers
• From there, look for the file named sys and rename it to Storport.old.

Note: As you can see, the file’s extension has changed from .sys to .old.

• Now restart your computer and check if the Storport.sys Blue Screen error is now fixed.

Option 3 – Run System File Checker or SFC scan

System File Checker or 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 to 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

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.

 Reboot your PC.

Option 4 – Try to run the DISM commands

You might want to repair potentially corrupted files in your system as having them could also trigger the Storport.sys Blue Screen error. To repair these corrupted system files, you can run the DISM commands:

• Tap the Win + X keys and click on the “Command Prompt (Admin)” option.
• After that, input each one of the commands listed below sequentially to execute them:
  • Dism /Online /Cleanup-Image /CheckHealth
  • Dism /Online /Cleanup-Image /ScanHealth
  • Dism /Online /Cleanup-Image /RestoreHealth

• Once you’ve executed the commands given above, restart your computer and check if the dxgkrnl.sys Blue Screen error is now fixed.

Option 5 – Run the Blue Screen Troubleshooter

Troubleshooting Blue Screen of Death errors wouldn’t be complete without the Blue Screen troubleshooter. As you know, it is a built-in tool in Windows 10 that helps users in fixing BSOD errors like Storport.sys. 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.

One of the great remote assistance software that helps you remotely access and control computers is TeamViewer. However, despite how efficient it is, there are still times when it throws up some errors and one of them is when TeamViewer is not able to connect and throws an error that says, “No connection to partner, Partner did not connect to router, Error Code WaitforConnectFailed”. This kind of error in TeamViewer mostly occurs when the Partner computer is not connected to a network. On the other hand, it could also occur when they are connected to a network so there are various causes for this issue. It could also be that the installation of the program itself was at fault or there is an incompatibility between the TeamViewer versions installed on both the computers and so on. Although there are several causes for this error, the potential fixes are still the same. You can try to restart the network or allow Full Access Control to TeamViewer or flush the DNS cache. For more information, refer to the following options but before you proceed, make sure that both your Windows 10 computer and TeamViewer program are updated to their latest stable versions.

Option 1 – Reboot your router

The first thing you can try to do to fix the error is to simply restart your router. All you need to do is reboot the router from its Admin panel or you can also turn it off manually and turn it back on after a couple of seconds so that it can completely reboot. Once you’re done, try accessing your server again and see if the error is now fixed.

Option 2 – Allow Full Access Control to TeamViewer

• First, open TeamViewer, and then from the Menu bar, click on Extras.
• After that, click on Options and select Advanced from the left side navigation panel.
• Next, click on the “Show advanced options” button located on the right-hand side.
• Then select Full Access from the drop-down menu of the Access Control option under the “Advanced settings for connection to this computer section”.
• Now click OK and check if the error is now fixed or not.

Option 3 – Try to flush the DNS configuration

You could also try to flush the DNS configuration in your computer to fix the error. How? Refer to these steps:

• Tap the Win + X key combination and click on the Command Prompt (Admin) option or you could also search “cmd” in the Cortana search box and right-click on Command Prompt from the search results and select the “Run as administrator” option.
• After opening Command Prompt with admin privileges, enter each one of the commands given below sequentially in order to flush the DNS cache.
  • ipconfig/release
  • ipconfig/renew
  • ipconfig/flushdns
• Now type the exit command to close Command Prompt and then restart your computer and see if the problem is fixed.

On the other hand, you could also try to reset Winsock as well as the TCP/IP.

Option 4 – Run the Network Adapter troubleshooter

To run the Network Troubleshooter, refer to these steps:

• Open the Search bar on your computer and type in “troubleshoot” to open the Troubleshoot settings.
• Next, scroll down and select the “Network Adapter” option from the right pane.
• Then click on the Run Troubleshooter” button.
• After that, your computer will check for any possible errors and will pinpoint the root cause of the problem if possible.
• Restart your computer.

Option 5 – Try to perform Network Reset

You might perform a Network Reset to resolve the problem if none of the four given options worked. This will reset the entire network configuration including your IP address. To perform Network Reset, follow these steps:

• Tap the Win + I keys to open Settings.
• From there, go to the Network and Internet section.
• Next, scroll down and look for “Network Reset” under the status pane.
• After that, click on Network Reset and then on Reset now to start resetting the network configuration. Once done, check if it is able to fix the error or not.

Windows 10 has displayed one of the most efficient and user-friendly interfaces. However there have been many issues on the backend of this commonly praised operating system: For example, Windows Update is still a wonky and error-laded system application. One example of this error is Windows Update Error 0x80073712 which stands in the way of users just wanting to keep their PCs updated hassle-free. The error code 0x80073712 signifies that a file needed by Windows Update to function is either damaged, missing, or corrupted. However, this does not mean that your Windows version will forever stay as-is with no mode to update it. Windows Update Error 0x80073712 is perfectly fixable with the set of provided steps below and some of Windows’ built-in troubleshooting steps:

Solution 1: Open Windows Update Troubleshooter

1. Open the Windows Update Troubleshooter by pressing the Window Key and  “S” keys simultaneously.
2. Enter the word “Troubleshoot” in the search box and select the Troubleshoot result
3. On the new window, select “Windows Update” to troubleshoot.
4. Run the troubleshooter, then open Windows Update and try to install the update again.

Solution 2: Run the DISM tool

1. Open the command prompt by pressing Windows Key and “S” key simultaneously
2. Enter “cmd” in the search box. Right Click command prompt among the results and select “Run as administrator”
3. In the Command Prompt window type the following and press the Enter key after every command

DISM.exe /Online /Cleanup-image /Scanhealth DISM.exe /Online /Cleanup-image /Restorehealth

4. To close the Administrator: Command prompt window, type Exit, and then press Enter.
5. Run Windows Update again.

Solution 3: Rename the Software Distribution folder

1. Open the command prompt as previously mentioned
2. Input the following command pressing Enter after every line net stop wuauserv net stop cryptSvc net stop bits net stop msiserver rename c:windowsSoftwareDistribution softwaredistribution.old net start wuauserv net start cryptSvc net start bits net start msiserver exit
3. Restart the PC and run the updater if it works again.

Solution 4: Restart Windows Update Services

1. Press the Windows logo key and R together to open Run -> Input services.msc -> and press Enter
2. Search for the Windows Update service -> Check its status
3. If it is not indicated, right-click on the service and select Start to force start your Windows Update
4. If you see an error, locate the Startup Type option and set it to Automatic
5. Now you should reboot your computer and see if your Windows Update is OK

Solution 5: Fix Registry Issues

If after all the aforementioned solutions, you still experience problems with Windows Update, the problem may lie in the registry that is either damaged or corrupted. You may choose to do manual editing of your Windows registry by opening your Windows registry editor. But doing so is risky as one wrong letter may do incalculable damage to your system. To do so safely for more inexperienced users., we recommend using a third-party registry cleaner/tools, many of which can be found online.

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.

Experiencing issues while using Remote Desktop connections is not uncommon. One of the issues that users encountered recently while trying to connect to their Remote Desktop network is the error saying, “Your credentials did not work, The login attempt failed”. If you are one of these users, then you’ve come to the right place as this post will walk you through fixing the problem. When facing this kind of problem, the first thing you can try before you do some troubleshooting steps is to verify the credentials. But if you are certain that you’ve entered the correct credentials just like what other users reported, then it’s completely a different matter. Based on the reports, this error is common on newly installed versions of Windows 10 or after reinstalling the operating system which could mean that the problem might be due to the Windows security policies or the username might have been recently modified. The latter case is a possibility especially if you’ve reinstalled Windows 10 and had entered a new username. In such a case, you will really have a difficult time connecting to your Remote Desktop connection since its credentials do not really automatically change. If you’ve verified that your credentials are correct, then now’s the time you troubleshoot the problem with the help of the potential fixes provided below. Just make sure that you follow each one of them in sequence.

Option 1 –Try to run the Network Adapter troubleshooter

To run the Network Troubleshooter, refer to these steps:

• Open the Search bar on your computer and type in “troubleshoot” to open the Troubleshoot settings.
• Next, scroll down and select the “Network Adapter” option from the right pane.
• Then click on the Run Troubleshooter” button.
• After that, your computer will check for any possible errors and will pinpoint the root cause of the problem if possible.
• Restart your computer.

Option 2 – Try to change the network profile from public to private

According to some reports, this error occurs on systems where the network profile was set to public. Thus, you need to change the network profile to private to resolve the problem. How? Refer to these steps:

• Go to Start and from there click on Settings > Network & Internet > Status.
• Next, click on the “Change connection properties” option.
• After that, set the radio button of Network Profile from Public to Private.
• Wait for a couple of seconds until the system is done applying the changes you’ve made and then see if you can now connect to the Remote Desktop connection.

Option 3 – Try changing the account username

As mentioned, one of the possible causes for this error is the reinstallation of the operating system. You might have changed the username for the system but it does not really change the username of the Remote Desktop connection as well. Thus, you have to change the username back to what it was before you’ve reinstalled Windows 10.

Option 4 – Try modifying the Windows Security Policy

You can also try to edit the Windows Security Policy as it could help in resolving the error. This Windows Security Policy, when enabled, will not allow non-admin users to log on to the Remote Desktop connection. So if you want to allow non-admin users to use the Remote Desktop connection, then you need to modify this policy. Note that you can only do that if you are the admin of the system yourself.

• Tap the Win + R keys to open the Run utility.
• Then type “secpol.msc” in the field and tap Enter or click OK to open the Local Security Policy.
• After opening the Local Security Policy window, select Local Policies > User Rights Agreement located on the left pane.
• Next, double click on “Allow log on through Remote Desktop Services” located in the right pane.
• And in the next window that appears, select Add user or group.
• After that, type in the username of the intended non-admin user under the “Enter the object names to select” column.
• Once done, click on the Check Names button to fix the username and then click OK to save the changes made.
• Restart your computer.

Option 5 – Use the Group Policy Editor

• Tap the Win + R keys to open the Run dialog box and then type “gpedit.msc” in the field and tap Enter to open the Group Policy Editor.
• Next, navigate to this path: Computer Configuration > Administrative Templates > System > Credentials Delegation.
• Double click on the “Allow delegating default credentials with NTLM-only server authentication” policy setting located on the right pane to edit it.
• After that, shift its radio button to Enabled and click on Show.
• Then type “TERMSRV/*” in the Value box and click OK.
• Now repeat the same for the following policy settings:
  • “Allow delegating default credentials”
  • “Allow delegating saved credentials”
  • “Allow delegating saved credentials with NTLM-only server authentication”

• Once you’re done, restart your computer and see if the problem is fixed.

If you are trying to install or upgrade your Windows 10 computer but suddenly encountered an error message saying, “Windows could not configure one or more system components”, read on as this post will show you how you can fix the problem. You are not alone in experiencing this problem as other users also reported having the same scenario. Some of them reported getting the following error message:

“Windows could not configure one or more system components. To install Windows restart the computer with error code 0xc1900101-0x30018.”

When you check on the Windows 10 rollback log, you will see a part with the “iisetup.exe” that’s related to the abort. Usually, the upgrade process completes over 50% and gets stuck and then rolls back later on and generates the error logs. This kind of error, in most cases, appears during the upgrade of Windows 10 and is related with the Internet Information Services or IIS in Windows 10. For some unknown reason, it restricts the installation or the upgrade which causes the error to appear. To fix the “Windows could not configure one or more system components” error, you can try to remove the IIS from the Windows Features or rename the “inetsrv” folder. You could also move all the folders related to IIS to another drive. For more details, refer to the options provided below.

Option 1 – Try to remove the IIS from Windows Features

The IIS is installed from the Windows Features and you can find it at Control Panel > Programs. From there, uncheck the checkbox for the Internet Information Services. Once done, click on the OK button to save the changes. Note that this process will get rid of all the related programs, services, and folders from Windows 10. So if you want to, you can just install them later on or use an offline installer from the official site of Microsoft.

Option 2 – Try renaming the inetsrv folder

The next option you can check out to resolve the problem is to rename the “inetsrv” folder. If you have uninstalled IIS from the Windows Features, this should remove the folders as well, however, it didn’t remove the folder then you have to delete the folders that are related to the IIS by following these steps:

• First, you have to boot into the Advanced Recovery Mode and from there, open Command Prompt.
• Next, execute this command to rename the folder from this location, C:Windowssystem32inetsrv: rename C:/Windows/system32/inetsrv/inetsrv.old
• Once done, boot into your computer normally and try to upgrade Windows 10 again, and check if the problem is fixed or not.

Option 3 – Try to move the folders related to IIS to a different drive

• Tap the Win + R keys to launch the Run utility and type “services.msc” in the field and hit Enter to open the Windows Services Manager.
• Next, look for the Application Host Helper Service from the list of services and stop it.
• Once done, take ownership of the “WinSxS” folder and then move the *windows-iis*.*” folders to another drive. You can just search using the “*windows-iis*.*” keyword in the Start Search.
• Next, tap the Ctrl + X keys and paste the folders to another drive.
• After that, start the update process for Windows 10 again.

Call of Duty is a fun and good game, a great time killer with a squad of friends, however sometimes the game crashes, and fun is interrupted. In this guide, we will address and solve this unpleasant issue.

1. Scan game files

   inside launcher choose options and under them, choose scan and repair game files This process can take 5-30 minutes, as the game is 60GB large. This will look through all your game files and make sure they’re all valid and that none are corrupted, which may cause crashes. When it’s complete, you’ll get a notification that the game is now playable. Try again and see if your crashes continue.

2. Update drivers

   Keeping drivers updated is crucial for the game to run smoothly, GPU drivers are possibly important. Go to your GPU manufacturer's website and get the latest drivers.

3. Lower graphic settings

   Intensive graphic requirements can overload GPU and cause crashes, try lowering details in-game and see if this will fix the issue.

4. Disable overlays

   If you’re using a program like Discordthat has an overlay, you’ll want to disable it as it may be causing the graphic error

When it comes to booting an operating system on a computer, one of the most essential pieces of software you can use is the UEFI. In fact, a lot of users now prefer to use UEFI instead of BIOS. It also depends on whether the UEFI or the BIOS is supported on the motherboard. Recently, a number of users reported an issue with UEFI where they were unable to find it under the Advanced Options screen where it’s supposed to be located. The missing UEFI Firmware settings in the Advanced Options could be caused by several reasons. It is possible that the access to the UEFI menu is blocked or it could also be due to the Extra Fast Startup feature being enabled. It is also possible that the operating system is installed in Legacy mode. There are several options to try to fix this issue. You need to check if your computer supports UEFI or you could also try to disable Fast Startup or bypass the Extra Fast Startup feature. You can also use a boot to UEFI shortcut as well as check the CMOS battery.

Option 1 – Try checking if your computer supports UEFI

The first thing you have to do is to verify if your computer supports UEFI. If your computer does not support UEFI, then it’s no wonder why you don’t see the UEFI Firmware settings in the Advanced Options.

Option 2 – Try turning off Fast Startup

• First, boot your computer in Safe Mode.
• Once your computer is booted in Safe Mode, tap the Win + R keys to open the Run dialog box and type in “control” to open the Control Panel.
• Next, click on the Hardware and Sound section and click on Power Options.
• Afterward, select the “Choose what the power buttons do” option from the left side menu pane.
• Now click on Change settings that are currently unavailable and uncheck the entry that says, “Turn on fast startup (Recommended)”.
• Then click on Save Changes and restart your computer and see if it has fixed the problem or not.

Option 3 – Try bypassing the Extra Fast Startup feature

As mentioned, the missing UEFI Firmware settings could be due to the Extra Fast Startup feature. To fix it, you have to disable this feature. All you have to do is tap and hold the Shift key and click on the Shutdown button from the Start button. This will boot your PC with the UEFI booting from the beginning and then use the hotkey for your motherboard to boot into the UEFI setup.

Option 4 – Try using a boot to UEFI shortcut

• Right-click on any empty space on your Desktop and select New > Shortcut.
• This will open a new mini window. And here, you have to type this in the text field: shutdown /r /fw
• After that, click on Next and name the desktop shortcut and then click on Finish.
• Next, right-click on the newly created shortcut and select Properties.
• Click on the Advanced button and select the “Run as administrator” option.
• Now click OK to save the changes made. Each time you execute this shortcut, your computer will automatically be booted to the UEFI Firmware Settings.

Option 5 – Try to check the CMOS battery

Another thing you can do is check the CMOS battery physically on the motherboard and see if it has to be replaced since a damaged CMOS battery can also cause the issue with the missing UEFI Firmware settings.

Option 6 – Set your computer from Legacy to UEFI

If applicable, you can try to set your computer from Legacy to UEFI to resolve the problem.

• In the Windows Search box, type “command prompt” and from the search results that appear, right-click on Command Prompt and select the “Run as administrator” option.
• After that, execute this command: mbr2gpt.exe /convert /allowfullOS
• Now, wait until the process is completed since you can track its process on your screen.
• Once it’s done, go to Settings > Update & Security > Advanced Startup options and from there, click on Restart Now. This will restart your computer and give you advanced options.
• Next, select Troubleshoot > Advanced Options where you will see further options including System Restore, Startup Repair, Go back to the previous version, Command Prompt, System Image Recovery, and UEFI Firmware Settings.
• Now select the UEFI Firmware Settings. This will take you to the BIOS. Boot Mode is typically available under Boot > Boot Configuration. Once you’re there, set it to UEFI and then save the changes you’ve made. After that, your computer will restart.

The Windows Update service, just like other services in Windows 10 may sometimes experience some issues and stop behaving properly. One of the issues you might encounter as you use the Windows Update service is the Windows Update error 0x8024A10A. This kind of error code signifies that the Windows Update service is shutting down. So if you encounter this error, read on as this post will guide you on how you can fix it. When you receive the Windows Update error 0x8024A10A, you may see this error message on your screen: “USO_E_SERVICE_SHUTTING_DOWN indicates that the WU Service is shutting down. This may happen due to a very long period of time of inactivity, a system hang leading to the service being idle and leading to the shutdown of the service. Ensure that the system remains active and the connections remain established to complete the upgrade.” You could try to restart your computer to resolve the problem since there are instances when a simple restart can fix errors. However, if it does not work, you might find the options provided below useful.

Option 1 – Try to restart the Windows Update Service

The first thing you can do to fix Windows Update error 0x8024A10A is to restart the Windows Update Service from the Services Manager. To do so, follow these steps:

• In the Cortana search box, type “services” and click on the Services icon to open the Services Manager. Alternatively, you can also tap the Win + R keys to launch the Run prompt and then type “services.msc” in the field and hit Enter to open the Services Manager.
• After opening the Services Manager, look for the Windows Update Service.
• Once you found it, right-click on it and check if the Service is stopped. If it is, then select the Start option. On the other hand, if the Windows Update Service is already started, just select the Restart option.
• After that, try to run the Windows Update again and see if the error 0x8024A10A is now fixed.

Option 2 – Run the Windows Update Troubleshooter

Since the Windows Update troubleshooter reviews the status of the services that support the process, it would prompt and fix it if there is anything that’s not right. Thus, you might want to run a built-in Windows Update troubleshooter to resolve the Windows Update error. It is one of the things you can check out as it is known to automatically resolve any Windows Update errors like error 0x8024A10A. To run this troubleshooter, 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 3 – Run Microsoft’s online troubleshooter

Aside from the Windows Update troubleshooter, running Microsoft’s online troubleshooter might also help you fix the Windows Update Error 0x8024A10A. This online troubleshooter is known to help in fixing Windows Update errors, it scans your computer for issues that might be causing the problem and then fixes them automatically.

Option 4 – Try to run the Windows Update Service in a Clean Boot State

There are some instances that some conflicting programs installed in your computer might be the one that’s causing Windows Update error code 0x8024A10A. To identify which program is causing the problem, you need to put your computer in a Clean Boot State. To do so, follow the steps below.

• Log onto your PC as an administrator.
• Type in MSConfig in the Start Search to open the System Configuration utility.
• From there, go to the General tab and click “Selective startup”.
• Clear the “Load Startup items” check box and make sure that the “Load System Services” and “Use Original boot configuration” options are checked.
• Next, click the Services tab and select the “Hide All Microsoft Services” check box.
• Click Disable all.
• Click on Apply/OK and restart your PC. (This will put your PC into a Clean Boot State. And configure Windows to use the usual startup, just simply undo the changes.)
• Now try to run the Windows Update Service again and see if Windows Update error 0x8024A10A is now gone.