SYSTEM_THREAD_EXCEPTION_NOT_HANDLED CMUSBDAC.sys

If you suddenly find the Windows Recovery Environment not working and you see an error message saying, “Could not find the recovery environment”, then you’ve come to the right place as this post will guide you on how you can fix it. In times when you can’t boot into the Windows Recovery Environment, there could be several reasons behind it. However, have you ever wondered where exactly the Windows Recovery Environment is in your computer? Windows initially places the Windows RE Image file in the installation partition during Windows Setup so if you have installed Windows in the C drive, you can find the Windows RE at the C:/Windows/System32/Recovery or C:/Recovery folder. Keep in mind that this folder is hidden and later on, the system copies the image file into the recovery tools partition to make sure that one can boot into recovery if there are any issues with the drive partition. The “Could not find the recovery environment” error mostly occurs if the Windows Recovery Environment is disabled or if the “Winre.wim” file is corrupted. Thus, to fix this error, you need to refer to the given suggestions below.

Option 1 – Try to enable Windows Recovery Environment

• In the Windows Start Search, type “PowerShell” and from the search results that appear, right-click on Windows PowerShell and then select the “Run as administrator” option to open it with admin privileges.
• Next, type the “reagentc /info” command and tap Enter to execute it.
• After that, if the output states that Status is enabled, then you’re all set.
• Now type the “reagentc /enable” command and tap Enter to enable the Windows Recovery Environment. You will see a success message at the end signifying that Windows RE is available.

Option 2 – Try to fix the corrupted or missing “Winre.wim” file

If the Winre.wim file is either corrupted or missing, you need to get a new copy of this file from another computer where the Windows RE is working. Once you’re able to get a new copy of the Winre.wim file, you have to set the image path to a new location. For more details, refer to these steps:

• First, type “Powershell” in Windows Start Search and right-click on Windows PowerShell from the results, and select Run as administrator.
• Next, execute the given command below to change the path of the WIM file to the new location. Note that the steps should be used when the file path of the Windows Recovery Environment is different from the usual spot.

Reagentc /setreimage /path C:RecoveryWindowsRE

• As mentioned, if the file is corrupted, you just have to get a new copy from another PC but before you do that, make sure that the WINRE on that computer is disabled (just enable it later on) and then place it in the C:/Recovery path and then set its path again using the command given above and then verify its path by executing the following command.

reagentc /info command

Note: Since the Recovery folder is hidden as well as the WINRE folder in it and you won’t be able to access them using the Windows File Explorer, you need to use the Windows PowerShell or Command Prompt so that you can access them.

Option 3 – Try checking and fixing the WinRE Reference in the Windows Boot Loader

The Windows Boot Loader is the one that determines if it has to load the Windows Recovery Environment. It could be that the boot loader is pointing to an incorrect location which is why you’re getting the error. To resolve it, you have to check and fix the WinRE Reference in the boot loader. How? Follow these steps:

• In the Windows Start Search, type “PowerShell” and from the search results that appear, right-click on Windows PowerShell and then select the “Run as administrator” option to open it with admin privileges.
• After that, execute the “bcdedit /enum all” command.
• Next, look for an entry in the Windows Boot Loader identifier set as Current and look for “recoverysequence” in that section and take note of the GUID.
• Ensure that the device and the osdevice items show the path for the Winre.wim file and that they are the same. If not, you need to point the current identifier to the one which has the same.
• Once you’ve found the new GUID, execute this command: bcdedit /set {current} recoverysequence {GUID_which_has_same_path_of_device_and_device}
• Now check if the error in the Recovery Environment is fixed or not.

Option 4 – Try creating a Recovery Media

You could also try creating a Recovery Media to resolve the error in the Windows RE. All you have to do is download the Windows 10 ISO file using the Media Creation tool and then create a recovery drive. Once you’re done, check if it fixes the problem or not.

Error Code 28- What is it?

The error code 28 is a driver error. This is one of the many device manager error codes. When this error occurs on your computer, the following message is displayed:

“The drivers for this device are not installed. (Code 28)”

Another driver device error message you might encounter is error code 41. 

Error Causes

Error 28 occurs because of unsuccessful device driver installation. This usually happens when you try to update new drive versions on your system. It is advisable to repair this error right away as it can hamper your ability to use certain hardware. For example, if error 28 occurs due to the unsuccessful installation of the USB driver, then it if not fixed and resolved it may prevent you from using hardware devices. Unsuccessful driver installation means you either didn’t install it properly or your computer has registry issues. If it’s the registry then you must fix it without any delay because it can expose your PC to serious threats like system crash and failure. To avoid such inconvenience, repair it.

Further Information and Manual Repair

When it comes to repairing the error code 28, here’s what you can do: Simply go to the control panel and click on the Device Manager option:

• In the details pane with the list of devices, locate the device for which you want to reinstall the driver software.
• Double click on it to open the properties dialog box.
• Now click on the driver tab and then click update driver.

After updating, try using that device again if it doesn’t work and shows the error code 28 on your computer screen then this means the underlying cause is the registry.

As you know, each one of the Windows 10 versions is priced differently and one of the considered more expensive compared to the Windows 10 Home version is the Windows10 Pro. The good thing is, Microsoft allows its users to upgrade from the Windows 10 Home version to the Windows 10 Pro version at a reasonable cost instead of buying the entire license again. However, upgrading your Windows 10 computer is not always that easy and you might encounter some errors along the way. One of the reported errors you could encounter is an error message that says, “Something happened, and we couldn’t start the upgrade”. This kind of problem is due to the problems with the Microsoft Store or the key authorization and to fix it, there are several options you can check out. You can try to run the built-in troubleshooters such as the Windows Update troubleshooter, Windows Store Apps troubleshooter, or Microsoft Accounts troubleshooter. You could also try to reset the Windows Store cache or re-register the Windows Store app. For more details, refer to each one of the given options below.

Option 1 – Try to run the Microsoft Accounts troubleshooter

Since the Microsoft Accounts troubleshooter is not built-in into the Windows operating system, you can download this troubleshooter by clicking on this link.

Option 2 – Try running the Windows Update Troubleshooter

Running the built-in Windows Update troubleshooter could also help you resolve the “Something happened, and we couldn’t start the upgrade” error. 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 3 – Run the Windows Store App troubleshooter

The Windows 10 Store Apps Troubleshooter will help you in fixing the problem in Microsoft Store. This is a great built-in tool from Microsoft that helps users fix any app issues. To use the Windows Store Apps Troubleshooter, follow the steps below.

• Tap Win + I keys again to open the Windows Settings panel.
• Go to Update & Security and then go to Troubleshoot.
• Under the Troubleshoot section, on your left-hand side, scroll down to find Window Store Apps.
• Then click on the Run the troubleshooter option and follow the on-screen instructions and then see if it fixes the problem.

Option 4 – Try to reset the Microsoft Store cache

As you know, like any other apps, Microsoft Store also caches as you view apps and games so it is most likely that the cache is no longer valid and must be removed. To do so, follow the steps below.

• Right-click on the start button and click on Command Prompt (administrator).
• Next, type in the command, “wsreset.exe” and tap Enter. Once you do, the command will clear the cache for the Windows Store app.
• Now restart your PC and afterward, try opening Microsoft Store again and then try to install your app or update your computer again.

Option 5 – Try to re-register the Microsoft Store app via Windows PowerShell

• Tap the Win + X key combination or right-click on the Start button and click on the Windows PowerShell (Admin) option.
• If a User Account Control or UAC prompt appears, just click on Yes to proceed and open the Windows PowerShell window.
• Next, type in or copy-paste the following command to re-register the Microsoft Store app and tap Enter:

powershell -ExecutionPolicy Unrestricted Add-AppxPackage -DisableDevelopmentMode -Register $Env:SystemRootWinStoreAppxManifest.xml

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

Option 6 – Try contacting Microsoft

If none of the options worked, you might also want to contact Microsoft for further assistance in fixing the error.

If your Windows PC encounters an error, it will display a Blue Screen of Death or BSOD error which usually comes up for a fraction of second and creates some logs or Dumps Files as what other user prefers to call it and then boots your PC suddenly. This process usually takes place quickly that most users find it hard to get the error code and won’t probably be able to check what really went wrong with their PCs. This is where the dump files come in. They are stored internally in your computer and can only be accessed by an administrator. They are classified into 4 main types and in Windows 10 they are either:

1. Complete Memory Dump
2. Kernel Memory Dump
3. Small Memory Dump (256 KB)
4. Active Memory Dumps

Dump Files are useful as they could help you in resolving the problem and so you need to configure your Windows 10 PC to create them but first, you need to make a system restore point. This is essential as you are about to modify some system files as well as critical Windows 10 settings. There are two ways you can create Dump files – first is by modifying the settings in the Startup and Recovery and lastly is via the WMIC command line. Refer to the instructions prepared below to be guided on how you can create Dump files after any BSOD error using these options.

Option 1 – via Startup and Recovery

• Type in “control panel” in the Cortana Search box and then click on Control Panel from the search results to open it.
• After opening Control Panel, you need to make sure that you view the contents by their Category then click on the header link which is labeled “System and Security” or you could also right-click on the This PC icon and then click on Properties.
• Next, select the Advanced system settings from the left panel. Once you do, a new and small window will pop up.
• Under the newly opened window, look for the section called Startup and Recovery and then click on the Settings button.
• And from the System Failure section, you can choose any option from the drop-down for Write debugging information such as:
  • None – this means that there is no dump file created by Windows
  • Small Memory Dump – this means that Windows will create a Minidump file on BSOD
  • Complete Memory Dump – this means that Windows will create a Complete Memory Dump file on BSOD
  • Automatic Memory Dump – this means that Windows will create an Automatic Memory Dump file on BSOD
  • Active Memory Dump – this means that Windows will create an Active Memory Dump file on BSOD

Note: The complete dump needs a page file that is allowed to be the size of the physical memory installed in your PC with a dedicated 1 MB of space for just the page header.

• Now once you have selected the most suitable option for you, just click on OK/Apply and then exit.
• Restart your PC to successfully apply the changes made.

Option 2 – via the WMIC command line

• The first thing you need to do to create Dump files via the WMIC command line is to tap the Win + X keys combination or simply right-click on the Start button and then select the Command Prompt (Admin) option. You could also type in “cmd” in the Cortana search box and then right-click on Command Prompt from the results and select Run as administrator.
• After that, type in any of the commands given below depending on your preferences so that your Windows 10 PC will be configured to create Dump Files:
  • No dump file: wmic RECOVEROS set DebugInfoType = 0
  • Small Memory Dump: wmic RECOVEROS set DebugInfoType = 3
  • Kernel Memory Dump: wmic RECOVEROS set DebugInfoType = 2
  • Complete Memory Dump: wmic RECOVEROS set DebugInfoType = 1
  • Automatic Memory Dump: wmic RECOVEROS set DebugInfoType = 7
  • Active Memory Dump: wmic RECOVEROS set DebugInfoType = 1

Note: A complete dump has to have a Page file which is allowed to be the size of the physical memory installed on your PC accompanied by a 1 MB space for just the page header.

• Now type in “exit” in the Command Prompt to exit it.
• Restart your PC to apply the changes made successfully.

I must admit that I am a big Western Digital fan, I have been using their hard drives really long time and I must admit that I am very happy with their products. Sometimes they could be a little more expensive than other drives on market but security and performance are on their side. If you ever wanted to purchase Western Digital or WD hard drives or you are considering getting one, no doubt that you have come across their color cryptic line of products. 1TB Hard drive can come in 6 different colors in your search products query and if you are not familiar with the WD color coding of hard drives you might be a little lost as to which one is right for you and what are the differences. This article is made to explain exactly that, what are WD colors representing so you can choose the right one for your needs. Western Digital has decided to use color codes in order to mark their series of disks which means that each color represents different hard drive series and it is made and aimed for different use, we are going to explore in detail each series below:

WD BLUE

Blue series is all around typical hard drive made and meant for daily use in desktop computers for all kinds of tasks. You can use it in casual gaming or for storage, its purpose is tailored for all-around casual daily users.

WD RED

WD Red HDD is designed for NAS and RAID systems. Its purpose is to be turned 24/7 who ever need access to it. Get this series if you need to have constant access to files or if you need a reliable RAID hard drive.

WD GREEN

Green series of the hard drive is manufactured for low power consumption and for storage, they are meant to be used for storage and not accessed regularly.

WD PURPLE

Purple line of hard drive products is designed solely for video surveillance systems. Instead of having a preference on reading data like WD RED, the PURPLE series is given preference on writing, constant writing to be more precise.

WD BLACK

The black series is made for an external storage medium with high performance. Due to the high performance, WD Black hard drives are much popular among photo editors and high-end gamers.

WD GOLD

WD Gold HDD provides a long-term cold storage medium. Therefore, this series of Western Digital hard drives are suitable for data centers. These hard drives can handle many sophisticated systems simultaneously and work well with different servers That's it, I hope that you have now a more clear understanding of the WD color-coding of its hard drive series. As always thank you for reading and I hope you will have a great day. If you would like to read more helpful articles and tips about various software and hardware visit errortools.com daily.

Signing in to a computer that runs a Windows 10 version OS is usually fast and straightforward. However, there are instances when signing in takes too long especially if there are a lot of programs in the Startup. So if many things are loading as soon as you log into your computer, it will slow down the sign-in process. Aside from programs in Startup, it is also possible that there are too many users that are logged in to the account. In such a case, you will most likely encounter an error that says, “Your computer is running low on resources, so no new users can sign in. Please use an account that has already been signed in”. If you’ve encountered such an error when you try to log into your computer, read on as this post will be guiding you on how you can fix it. Each time a user signs in to Windows 10, it will allocate resources in order to work smoothly. But, in many cases, the system is running low on resources which is why this error pops up and blocks a sign-in of a new user. To fix it, you can try to log out the existing users, or perform a Cold Boot, as well as run both the DISM tool and System File Checker scan.

Option 1 - Try to logout existing users

The first thing you can do is to log out the existing users. If you have a shared Windows 10 computer, you have to check if someone hasn’t logged out. It could be that some background task or there is an existing program that is still running under that account. So you have to make sure to ask the same user to log out in case there is some unsaved work. On the other hand, if that user is not around, then you reboot the computer right away.

Option 2 - Try Performing a Cold Boot

You could also try to perform a Cold Boot to fix the problem. A Cold Boot is a process that makes sure that the Windows 10 Kernel shuts down properly and releases all the resources held by any account. To perform a Cold Boot, just press and hold the physical power button on your CPU until it goes off. After that, boot your computer regularly and see if you can now log into your account without any error.

Option 3 - Try to run a System File Checker scan

System File Checker is a built-in command utility in Windows that helps in restoring corrupted files as well as missing files. It replaces bad and corrupted system files to good system files that might be the cause why you’re getting the error when you log into your computer. To run the SFC command, follow the steps given below.

• Boot your computer into the Advanced Recovery mode and from there open Command Prompt.
• 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.

 Now restart your computer and see if the problem is fixed or not.

Option 4 - run the dism tool

You might also want to run the DISM tool. This tool is known to repair potentially corrupted files in your system as having them could also system issues like the “Your computer is running low on resources, so no new users can sign in” error. To repair these corrupted system files, you can run the DISM commands:

• Go to the Advanced Recovery mode and select Command Prompt.
• 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 problem is now fixed.

Being in the Microsoft Windows insider program will let you get a hands-on new Windows 11, but some people just want Windows 11 without being in the insider program. Well, people beware! It was detected that some groups have been releasing fake Windows 11 installers with malware into them. There’s one malicious file called 86307_windows 11 builds 21996.1 x64 + activator.exe. Based on the filename, one might guess that it includes Windows 11 build 21996.1, and on top of that, there’s something in it that will automatically activate Windows for you. It comes in at 1.75GB, so for some people, that might seem reasonable. It starts out looking like a normal installer, and then there’s a second installer that calls itself a download manager. If you accept the nonsense agreement that’s included, you get a bunch of malware. This is just one example of malicious installers running amok internet, but there are more of them with different software placed inside. Malware can be anything from adware to a Trojan virus. The adware usually isn’t super dangerous. It’s just malware that’s meant to inject your PC with advertisements. Viruses can be more of an issue, and they can be harder to get rid of if your machine is infected. Windows Defender does a good job of getting rid of this stuff. The only problem is that if you’re downloading Windows 11 from shady sources, you’re probably already set to click through the dozen or so warnings that pop up telling you not to install it. The solution will be to get Windows from a trusted source of roll inside the insider program and get it from Microsoft directly.

What is the Error 421?

Error 421 is a common SMTP (Simple Mail Transfer Protocol) Outlook error message. MS Outlook is one of the best and popular email applications widely used by PC Windows users for sending and receiving emails within and outside workplaces. It is most commonly used in offices by professionals for faster communication. This error may occur while sending and receiving emails on the server. The error 421 messages is displayed in either of the following formats:

“An unknown error has occurred: Server error 421” "Could not send your message. Error 421" 421 4.2.1 : (DYN:T1) http://postmaster.info.aol.com/errors/421dynt1.html 421 4.3.1 Out of disk space for temp file 421 4.3.2 All server ports are busy 421 Downstream server error 421 Fork failed 421 Greylisting enabled, please try later “An unknown error has occurred. Subject ‘Testing’, Account: ‘pop.charter.net’, Server: ‘mail.charter.net’, Protocol: SMTP, Server Response: ’421 Message rejected’, Port: 25, Secure(SSL): No, Server Error: 421, Error Number: 0x800CCC67”

Solution

Error Causes

Some common causes for this critical Outlook error are:

• PST storage size exceeds 2GB file size
• Improper ISP settings
• Slow internet connection
• PST file corruption
• Trojan attack and viral infection

This is a critical Outlook error that should be resolved timely. If you delay, it may cause you a great deal of inconvenience. The error code 421 hampers your ability to access your email account, send and receive emails, add new contacts, view emails, calendar entries, and journals. In other words, it just brings your email activities to a standstill locking you out of the account.

Further Information and Manual Repair

To resolve this error code on your system, you don’t always have to hire a professional or call the network personnel to do the job. It may be a critical error but the good news is that it is quite easy to fix. Even if you don’t have technical expertise, you can still repair it. Here are some of the best methods to repair this issue on your system:

1. Change the Server Settings to its Maximum Limit

Try changing your server settings. Here set the inbound connections limit at the maximum limit.

• To do this, open the Microsoft Exchange Server Administrator utility. The access path of this utility will vary depending on the installation procedure used to set up Exchange Server.
• Once you open the MS Exchange Server Administrator utility, click the ‘Connections’ icon in the left side navigation pane. Now double click the internet mail service icon in the right side pane. As you click it, the Properties window will open.
• Now click the ‘Connections’ tab in the Properties window and then click the ‘Advanced’ button. This will open the configuration window.
• Here reset the number for ‘Maximum Number of Inbound Connections’ to a high number, its maximum limit. After changing the settings, close all open Exchange Server Administrator program windows to successfully complete the process.

After the process is complete, try accessing your Outlook email account again; if it works, then that’s great the error 421 is resolved. However, if it doesn’t, then the problem could be related to viral infection.

2. Download a PST Repair Tool

If the cause of the error is PST files corruption, then not only will you be locked out of your email account, you are also at risk of losing all the data stored in your email account. However, the best way to resolve the error and ensure full data recovery is to download a reliable PST repair tool. By running a PST repair tool on your system, you can resolve the error 421 right away. It recovers your data, repairs corrupt and damaged PST files.

3. Scan Your PC with Restoro.

If viral infection and Trojans are causing the error 421 to pop up on your system, then it is recommended to download and scan your PC with Restoro. This is an advanced, intuitive, and user-friendly PC fixer. It is not just an antivirus but also a system optimizer and a registry cleaner. Unlike common antivirus software that only removes viruses and simultaneously slows down the system’s speed, Restoro removes all types of malicious software on your PC including malware, spyware, Trojans, and viruses, and also boosts the speed of your PC significantly. It is safe, easy to operate, and a quick fixer. It is compatible with all Windows versions. Click here to download Restoro and resolve error 421 today!

If you are using File Explorer but suddenly encountered an error saying, “No such interface supported”, read on as this post will guide you on how to fix the problem. This kind of error occurs due to the corruption in the system files which supports several tasks in the system that works with the Windows File Explorer process or File Explorer. This kind of error can give you a hard time in browsing the files on your computer, or when you open important utilities like the Control Panel, or when you copy files and other inconveniences. Needless to say, it won’t bring you any productivity at all and can only leave you frustrated. To fix this problem, there are several options you can try. You can try to run the System File Checker scan or the DISM tool. You could also try to re-register the potentially corrupted DLL files or fix the User Profile. For more details, refer to each one of the given options below.

Option 1 – Try to run System File Checker

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 that might be the cause why you’re getting the errors 0x8024a11a and 0x8024a112. To run the SFC command, follow the steps given below.

• Type “cmd” in the Start search and then right-click on the appropriate search result.
• Next, select “Run as administrator” to open Command Prompt with admin privileges.
• 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.

• Now restart your computer and see if the problem is fixed or not.

Option 2 – Try to fix the User Profile

The next thing you can do to fix the problem is to fix the User Profile. All you have to do is migrate to a new User Profile in Windows 10 by creating a new User Account and migrating all your personal files from the current user profile folder in the C:/Users location to the new user profile folder which is also located in the same folder.

Option 3 – Run the DISM tool

You can try running the Deployment Imaging and Servicing Management or DISM tool to fix the “No such interface supported” error. Using this built-in tool, you have various options such as the “/ScanHealth”, “/CheckHealth”, and “/RestoreHealth”.

• Open the Command Prompt with admin privileges.
• Then type in the following commands and make sure to hit Enter right after you type each one of them:
  • Dism /Online /Cleanup-Image /CheckHealth
  • Dism /Online /Cleanup-Image /ScanHealth
  • exe /Online /Cleanup-image /Restorehealth
• Do not close the window if the process takes a while as it will probably take a few minutes to finish. Once it’s done, restart your computer.

Option 4 – Try to re-register the problematic DLL file

You may have to re-register the ntdll.dll file using the regsvr32.exe before you can successfully install the program and fix the error. The Regsvr32 tool is a command-line utility that can be used to register and unregister OLE controls like DLL and ActiveX (OCX) controls in the Windows operating system. Follow the steps below to use it.

• Open Command Prompt as admin from the WinX menu.
• Next, type the following command in the elevated Command Prompt and hit Enter to execute it. This will re-register the affected DLL file using the Windows operating system tool, regsvr32.exe.

regsvr32 c:windowssystem32actxprxy.dll

• After you execute the given command, you should see a message saying, “DllRegisterServer in vbscript.dll succeeded” if the Regsvr32 tool was able to run successfully. If it didn’t work, you can try to execute this command instead: FOR /R C: %G IN (*.dll) DO "%systemroot%system32regsvr32.exe" /s "%G"
• Once it’s done, restart your computer.

Recently, a number of users reported an error while trying to update their computers. This particular Windows Update error has an error code of 0x80073701. If you are one of the users who encounter this error, then read on as this post will guide you on how exactly you can fix it. Here’s the exact context of the error:

“Updates failed. There were problems installing some updates, but we’ll try again later. 2019-07 Cumulative Update for Windows 10 Version 1903 for x86-based Systems (KB4507453) – Error 0x80073701”

The Windows Update Error 0x80073701 also comes with a code “ERROR_SXS_ASSEMBLY_MISSING” which indicates that some system files are missing on your computer that caused the update installation failure error. Although this Windows Update error does not cause any severe issues, it is still being reported in the section of Windows Update where it is marked as “Update failed”. There are several potential solutions you can check out to resolve this error. You can try to run the DISM tool or the SFC or System File Checker scan. You could also try to run the Windows Update troubleshooter. For more information, make sure to follow the options given below.

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

Restarting your computer can also help in fixing the Windows Update failed to install error 0x80073701. There are cases where the issue resolves on its own as it could just be some simple network or PC error.

Option 2 – Try to run the DISM tool

Running the DISM Tool helps in repairing the Windows System Image as well as the Windows Component Store in Windows 10. Using this built-in tool, you have various options such as the “/ScanHealth”, “/CheckHealth”, and “/RestoreHealth”.

• Open the Command Prompt as admin.
• Then type in this command: exe /Online /Cleanup-image /Restorehealth
• Do not close the window if the process takes a while as it will probably take a few minutes to finish.

After you run this tool, a log file is created at C:WindowsLogsCBSCBS.log. On the other hand, if the Windows Update client is already broken, you will be prompted to use a running Windows installation as the repair source or use a Windows side-by-side folder from a network share, as the source of the files. Although the chances of this happening is less, if it turns out to be the case, you need to run an advanced command in the DISM tool to repair a broken Windows Update. Just repeat the process above but use the following command instead:

DISM.exe /Online /Cleanup-Image /RestoreHealth /Source:C:RepairSourceWindows /LimitAccess

Option 3 – Try to run the System File Checker

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 that might be causing the error 0x80073701. 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.

• Restart your computer.

Option 4 – Try running the Windows Update Troubleshooter

Running the built-in Windows Update troubleshooter could also help you resolve the Windows Update error 0x80073701. 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.