Recently, a lot of users reported having an issue with Windows Update. According to these users, they got an error message saying, “Windows Update components must be repaired” after they run the Windows Update troubleshooter. So if you are also facing this issue then you’ve come to the right place as this post will guide you in fixing this problem.
There are various suggestions you can check out to fix this problem – you can try running the Windows Update troubleshooter again but this time, in a Clean Boot State or you could also run System File Checker or the DISM tool to repair corrupted Windows Update files or reset the Windows Update components. For more information, refer to the given options below.
Repairing the “Windows Update components must be repaired” error is not that complicated. One of the things you can try is to run the Windows Update troubleshooter again but this time, in a Clean Boot State. Refer to the steps below to get started.
If the Windows Update troubleshooter still failed to fix the problem, you can run System File Checker instead. It 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.
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:
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”.
Note: If it happens that the Windows Update client is broken, you need to run the following command to repair it then restart your PC and click on Update once again.
DISM.exe /Online /Cleanup-Image /RestoreHealth /Source:C:RepairSourceWindows /LimitAccess
You can also delete the contents in both the Software Distribution and Catroot2 folders as it could potentially fix the “Windows Update components must be repaired” error.
net stop wuauserv
net start cryptSvc
net start bits
net start msiserver
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:
net start wuauserv
net start cryptSvc
net start bits
net start msiserver

“Something went wrong, try rebooting your PC and then launch GeForce Experience, ERROR CODE: 0x0001.”Errors like this one diminish the overall experience of users due to the fact that when this error occurs, the NVIDIA GeForce experience wouldn’t even start which renders its features useless. There are several potential fixes you can check out to resolve this error but before you check them out, you can try to restart your computer first and then open the NVIDIA GeForce Experience once again, if you still encounter the error, then you need to check the NVIDIA Display Driver Services or update your NVIDIA display drivers or switch to the BETA release. You could also try to install and reinstall the NVIDIA display drivers or perform System Restore and see if it helps. For detailed instructions, follow the given options below.
DISM /online /get-features /format:table | more
DISM /online /enable-feature /featurename:[Enter the name of the feature here] –AllNote: Now if you want to disable a feature that’s already enabled in your computer, refer to these sub-steps:
Get-WindowsOptionalFeature –Online
Get-WindowsOptionalFeature -Online -FeatureName *Type feature name*
Enable-WindowsOptionalFeature -Online -FeatureName “Type feature name” –all
Disable-WindowsOptionalFeature -Online -FeatureName “Type feature name”
“Error 0x800701e3: The request failed due to a fatal hardware error.”There are several methods you can check out to fix this error – you can try to run System Restore or Check Disk or format the destination drive or check the SMART attribute of the drive. For more details, refer to each one of the following options.
Some users installing or upgrading to Windows 10 experienced the theKMODE_EXCEPTION_NOT_HANDLED Blue Screen of Death (or commonly known as BSOD) error. This error can be due to different types of things, ranging from software to driver issues. When you experience this BSOD error while trying to install Windows 10, it will prompt you to restart your computer every single time you experience it. In most cases, you will also not be able to proceed with the Windows 10 set-up.
Error CausesThe “KMODE_EXCEPTION_NOT_HANDLED” error is normally caused by:
You won’t be able to successfully upgrade or set up Windows 10 if you continue to encounter this BSOD error. Note that this error will always prompt your computer to restart every time it happens, preventing you from completing the Windows 10 set-up.
If you’re not tech-savvy or not capable of debugging this issue, it’s highly advisable to proceed with the basic troubleshooting techniques available in this link.
After troubleshooting, below you’ll find a few solutions to rectify the issue.
Two common causes of the KMODE_EXCEPTION_NOT_HANDLED issue are hardware incompatibility and faulty device driver or system service.
If you experience this error, check first if any of your newly installed hardware is compatible with Windows 10. You can find the required hardware for Windows 10 from this link.
If all your hardware is compatible with Windows 10, you might need to check the device driver or system service. Review the bug check message. If any of the drivers you have is listed in the message, either disable or uninstall them before upgrading or setting up Windows 10.
You might also find it useful to check the System Log available in the Event Viewer for other error messages that can help you figure out the driver or device that’s causing the error. Running hardware diagnostics can also be useful.
Other troubleshooting steps include:
If you still experience the error after doing the methods above, you might want to try a powerful and trusted automated tool to fix the job.
“Error 2753, The File is not marked for installation.”Note that this kind of error is not bound to only some specific files but it can also happen with any file, be it an executable file or an MSI file. To fix this error, here are some possible solutions that you could try.
Error Causes