0x800701e3, The request failed due ...

In previous versions of Windows changing the system, the font was a pretty straightforward process, but it seems Microsoft did not want this feature to keep for whatever reason and there is no option as of the time of the writing of this article to do it in standard options in Windows 10. But do not worry, you are still able to customize your Windows and choose which font would you like to see inside it in all of its dialogs. You can choose whichever font you desire, the only prerequisite is it to be installed on your system. This guide will require you to change values in the registry of Windows itself so please follow step-by-step instructions and always make a backup of the registry before changing it in order to prevent some permanent Windows issues. All of that being said, let's start.

Setting new font

First thing is to open notepad, in the notepad paste the next block of code:

Windows Registry Editor Version 5.00 [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Fonts] "Segoe UI (TrueType)"="" "Segoe UI Bold (TrueType)"="" "Segoe UI Bold Italic (TrueType)"="" "Segoe UI Italic (TrueType)"="" "Segoe UI Light (TrueType)"="" "Segoe UI Semibold (TrueType)"="" "Segoe UI Symbol (TrueType)"="" [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\FontSubstitutes] "Segoe UI"="NEW_FONT"

Where in "Segoe UI"="NEW_FONT" instead of NEW_FONT you need to write the exact name of the font that you wish to use as a system font. Once you have replaced the default system font with your desired one, go to File and save as, from file type drop-down menu, choose all files and save this file as .REG type giving it whatever name you wish. When the file is saved, close notepad, right-click on the saved file and choose the merge option. Confirm with YES and click on OK. Reboot your system and your Windows will now use the font of your choice as its default system font.

Restoring default font

If you wish to return the old default system font as it was, follow the same steps but in your notepad paste this code:

Windows Registry Editor Version 5.00 [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Fonts] "Segoe UI (TrueType)"="segoeui.ttf" "Segoe UI Black (TrueType)"="seguibl.ttf" "Segoe UI Black Italic (TrueType)"="seguibli.ttf" "Segoe UI Bold (TrueType)"="segoeuib.ttf" "Segoe UI Bold Italic (TrueType)"="segoeuiz.ttf" "Segoe UI Emoji (TrueType)"="seguiemj.ttf" "Segoe UI Historic (TrueType)"="seguihis.ttf" "Segoe UI Italic (TrueType)"="segoeuii.ttf" "Segoe UI Light (TrueType)"="segoeuil.ttf" "Segoe UI Light Italic (TrueType)"="seguili.ttf" "Segoe UI Semibold (TrueType)"="seguisb.ttf" "Segoe UI Semibold Italic (TrueType)"="seguisbi.ttf" "Segoe UI Semilight (TrueType)"="segoeuisl.ttf" "Segoe UI Semilight Italic (TrueType)"="seguisli.ttf" "Segoe UI Symbol (TrueType)"="seguisym.ttf" "Segoe MDL2 Assets (TrueType)"="segmdl2.ttf" "Segoe Print (TrueType)"="segoepr.ttf" "Segoe Print Bold (TrueType)"="segoeprb.ttf" "Segoe Script (TrueType)"="segoesc.ttf" "Segoe Script Bold (TrueType)"="segoescb.ttf" [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\FontSubstitutes] "Segoe UI"=-

Reboot your system and your Windows will now revert the font of your choice as its default system font.

Can graphic cards wear out over a longer period of time? Recent studies and experience from crypto miners say no but they can die due to different reasons like improper use, low cleaning habits, factory mistakes, etc. Many gamers and people who use GPU intense applications tend to think that some glitches and hiccups in the software are a sign that graphic card is dying out and that it is time to be replaced. Altho this could be true in many cases these kinds of behavior are mostly due to old drivers and software issues. Older cards can produce these kinds of results due to their old age and new software is often more demanding than these cards can handle. So in order to diagnose and be sure that your GPU is indeed dying out lookout for these signs.

The Main Signs of a Dying GPU:

The Computer Crashes and Won’t Reboot

If your computer shutdown while working in the graphic application or while playing the game and the monitor loses signal there is a high chance the graphic card is soon going to be gone. Some motherboards have hardware detection failure and can signal immediate fail. If when turning your computer ON you are greeted with a blue screen with the message that the signal can not be found or you do not have picture at all it is most likely that GPU has failed.

Graphic Glitches While Playing Games

If you are playing the game and all of sudden you get off-color pixels, screen flickering, strange graphic behaviors, random artifacts, or similar and that keeps repeating in multiple games it is likely that GPU days are coming to an end.

Abnormal Fan Noise or Performance

Fans are an essential part of cooling the GPU and over time if they are intensively used they could wear out and need replacing. If however you have not noticed and have not replaced the fans card can sustain overheating damage. Many cards have cooling fans that are designed to spin at a higher RPM only when the GPU is under load. It prevents bearings in the fans from dying prematurely, so don’t worry if one of your fans is inactive while you are browsing the web. However, when you play games that utilize software that your card isn’t built to support, the bearings in the fans wear out faster. Once the fans stop working under load, the graphics card can quickly die.

How to Diagnose a Dying Graphics Card

Presented next are essential steps in order to recognize a dying graphic card.

Check Motherboard Error Codes

Many motherboards today completely shut down a component that is no longer working. If your graphics card has died completely, this may be one of the easiest ways to tell. If your motherboard doesn’t have display codes, you can try testing the card in a new system.

• Open the computer case: Use your screwdriver to remove screws on the side panel and gently slide it back.
• Locate the error code display on your motherboard: If you have a motherboard with error codes, they should appear near an outer corner.
• Try to reboot your computer: Record each error number you see after you boot your computer.
• Consult the motherboard manufacturer manual for error codes: Open the manual and locate the list for your error codes. If the code matches a graphics processing unit error, your video card could have died.

Check Hardware for Damage or Debris

A graphics card that has damage or debris on the physical parts might quickly overheat and kill the card.

• Remove the screws holding the GPU in place: There are typically one or two screws holding the card to a bracket on the case.
• Unhook the power cords from the GPU and pull the release tab: Remove the power cords from your GPU by pushing in their tabs and gently rocking them out. Once you remove each cord, gently push or pull up on the release tab near the motherboard.
• Inspect the GPU for damage/debris: Check the card for any dirt or debris buildup and clean it out with a Q-tip. You can replace broken fan pieces from the manufacturer.

Test Your GPU Under Load

Download GPU stress-testing and heat-monitoring software.

• With the card installed, run a stress test.
• As you are running the stress test, run heat-monitoring software: With the stress test running, check your heat-monitoring software for GPU overheating. Any reading over 80 degrees Celsius is too hot.
• Check device manager for outdated drivers: If your GPU is clean, but still running too hot, your software drivers are not installed correctly. To check, type in “device manager” at the bottom of your desktop and click on Device Manager. Find your display adapter and right-click on it to see if it’s working. If your drivers are not working correctly, it is indicated here usually. However, the driver may appear to be functioning even if it says otherwise in the properties.

Keep your graphic card drivers updated

When you don’t have the right driver installed, graphics cards can quickly burn up, and their cooling components may fail faster. That’s why you should always keep drivers updated for each new game you install or play. Older games may also release new software patches, so your GPU drivers should be updated accordingly.

Stumbling upon downloader.dll not found error is not pleasant to experience, usually, it means that desired application can not be started. There could be several reasons why this error happens from user mistakes, corrupted files, bad installation, and even bad RAM memory. Whatever the reason might be solutions provided are the same for all and offer a fix to this issue. it is advisable to follow provided solutions from start to finish not skipping any one of them since they are tailored to address the simplest solutions and issues and move toward more complicated ones.

1. Reinstall application

   If you are receiving Downloader.dll not found when trying to run just a single certain application, reinstall the application, there is the possibility that the application has somehow corrupted downloader.dll during the installation process. Reinstalling might fix the problem.

2. Run SFC scan

   SFC scan is the tool meant to scan all files and fix any corrupted ones. To run this tool, open the command prompt in administrator mode by right-clicking on the windows start button and then left-clicking on the command prompt (admin). When you are in command prompt type in SFC /scannow and let the whole process finish.

3. Update device driver

   If previous steps have not provided results, go to device manager and visually check is there a device with an exclamation or other sign next to it, if there is, right-click on it and choose update driver.

The Error Code 0x80070057 is rather typical with Win7. Customers of Win7 maintain reporting that each moment they strive to install this Operating system, it shows this problem error. Often, the total information that comes with this specific error is:

"Error Code 0x80070057: The parameter is wrong"

When this problem happens, you will end up struggling to move private documents from one person to another.

Solution

Error Causes

You could get the error message when you attempt installing Win7,

"An Internal Error has occurred. Incorrect parameters".

If this happens to you, realize that you are dealing with malfunction code 0x80070057. This error occurs mostly when you are trying to build a full backup of your Windows 7 OS.

The primary source of Error 0x80070057 is huge registry values.

Extensive registry values usually occur when you are trying to back up your Windows 7 OS. This means that you need to immediately create a bigger virtual memory space to avert the occurrence of the error.

Error Code 0x80070057 can be a result of incompatibility between the motherboard and some drivers.

Check whether the computer's motherboard and the installed drivers are compatible. If you can't do this effectively on your own, it might be a good idea to enlist the services of a qualified technician.

The Problem Signal 0x80070057 has a close Connection with RAID Installations

RAID installations have a tendency of sparking off the Error Code 0x80070057. If you experience this error while using RAID, first turn off the RAID setup and check whether that resolves the problem.

Further Information and Manual Repair

Error Code 0x80070057 is repairable. Thus, there's absolutely no cause for alarm when you see it with respect to your own Windows 7 Operating System. So what can you do to resolve it? a) Increase Virtual Memory: This is perhaps the most common solution to Error Code 0x80070057. In most cases, simply raising the virtual memory especially on Windows 7 Operating-System completely eliminates the error. Moreover, you don't have to be technically advanced to effect the change. Simply follow these steps:-

• Click the Start Button and visit Control Panel
• Click System Security, and proceed to System.
• Click the Advanced System Settings, subsequently proceed to the Advanced Level Tab.
• Click Change, which can be under the Virtual Memory
• Change the virtual memory value. For instance, you can customize entirely from 2000MB to 6000MB.
• Click Set, then Ok. You are done

As with each additional change you make with respect to your Computer, you will have to conclude by re-booting it. This way you make certain that they'll stay as you've established them and apply the necessary modifications. If the error still persists after attempting the preceding fix, download a registry-cleaning software. The software will clean up your disk and free up memory thus increasing the available virtual memory for your computer. This should solve your persistent Error Code 0x80070057.

What Is Sndvol32.exe Error?

Sndvol32.exe is actually an important part of the Windows operating system. Responsible for managing the sound-card volume and running programs properly, the problem occurs when error messages appear. The user will be unable to listen to music on the system. Usually, Windows XP users encounter the Sndvol32.exe error.

Solution

Error Causes

Sndvol32.exe error can be caused by any one or several of the reasons listed below.

• Accidental deletion of the DLL file from the system
• Damage to the DLL file due to spyware or virus infection
• Improper removal of software
• Unintentional overwriting on the DLL file by a mismatched version
• Obsolete hardware drivers
• Several obsolete/invalid registry entries
• Corrupt registry entries

Regardless of what triggers the Sndvol32.exe error, it is of utmost importance to take immediate measures to fix the problem and to keep it from occurring again.

Further Information and Manual Repair

If you are looking for ways to fix this error manually, the Windows functionality of System Restore will come into play in this particular scenario. In case the error is caused by a damaged or corrupt file, performing System Restore is an ideal choice as it will allow you to not only get a fresh copy of the operating system, it will be possible for you to remove the error at the same time as well. The procedure for performing System Restore is outlined below as follows.

• Click on the Start menu and type ‘System Restore’ in the search box.
• When the icon for ‘System Restore’ appears, click on it.
• Now type ‘Restore’ in the search box that appears on the start menu.
• The window for the System Restore center will now appear.
• Now you have two options. You can either opt for “Recommend Restore” which is the case where the system itself will choose a restore point for you or you can select “Choose a different restore point”. Users are advised to choose the latter option as it is more customizable.
• Users can now select from a list of restore points that have been created before. If you observe closely, you will realize that one of the restore points is prior to the occurrence of the Sndvol32.exe error.
• Click on the restore point. Once you have confirmed your selection, your system will restart and it will roll back to its previously selected restore point.

One recommendation is to perform the system restore in Windows Safe Mode. This is just to ensure that the System Restore is performed smoothly and any potential problems are kept at bay.

If you were trying to open File Explorer but it suddenly stopped working and you encounter an error message that states, “An attempt was made to reference a token that does not exist”, read on as this post will guide you in fixing this problem. This problem was initially reported after the April Update and Microsoft was able to fix it right after correcting the build. However, this effort seems futile for some users as recently, some reported getting the same error when they try to open not just Windows File Explorer but also with utilities like Microsoft Management Console or MMC, Visual Studio, Task Manager, Printer, Recycle Bin, etc. Two of the most likely causes of this error are a troublesome Windows Update and corrupted system files. Whatever the cause is, here are some suggestions you can follow to fix the “An attempt was made to reference a token that does not exist” error.

Option 1 – 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 ntdll.dll file crash error. The Regsvr32 tool is a command-line utility that can be used to register and unregister OLE controls like DLL and ActiveX (OCX) control 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 commands in the elevated Command Prompt and hit Enter to execute the command. This will re-register the affected DLL file using the Windows operating system tool, regsvr32.exe.
  • exe /[DLL file]
  • exe [DLL file]

Note: Replace “[DLL file]” with the name of the DLL file that was pointed out in the error.

• After you execute the given commands, you should see a message saying, “DllRegisterServer in vbscript.dll succeeded” if the Regsvr32 tool was able to run successfully. After that, try to install the program again and see if it now works.

Option 2 – Replace the DLL file from a trusted source

• First, you need to get the new DLL file from another computer with preferably the same file version number.
• After that, you need to boot your PC into Safe Mode and navigate to the paths listed below and then replace the file using a USB drive or other external storage devices.
  • x86: This PC > C:/Windows/System32
  • x64: This PC > C:/Windows/SysWOW64
• Next, type “cmd” in the Cortana search box and right-click on Command Prompt, and select “Run as administrator” to open it with administrator privileges.
• Now type the “regsvr32 ntdll.dll” command and hit Enter.
• Restart your PC and check if the error is now fixed.

Option 3 – Perform a System File Checker scan

The System File Checker or SFC scan could detect and automatically repair damaged system files that could be causing the “An attempt was made to reference a token that does not exist” error to pop up. 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 reverting back to the previous build of Windows

This kind of error might have something to do with a Feature Update so you can try to revert your computer to a previous build of Windows 10 as it could help you fix the problem. In this case, it would better if you refrain from updating your Windows 10 computer until this problem is completely resolved by Microsoft.

As you know, Bluetooth headphones allow users to connect to their mobile devices wirelessly. This allows you to talk on your mobile device or listen to music without having to connect any cords or wires. Additionally, it even allows you to adjust the volume of a left or right speaker. However, Bluetooth headphones in Windows 10 are another story as their scope is limited. For instance, the left and right pieces can’t have different volume levels. But if you still want to change the dual control of the volume of headphones separately in Windows 10. And in this post, you will be guided on how exactly you can do that. In addition, in this post, you will also be guided on what you can do if the Windows Update messed with the Bluetooth volume control and what you can do to disable the absolute volume in Windows 10. In case you don’t know, the Absolute Volume feature is actually incompatible with a number of Bluetooth devices which can result in the inability of the Bluetooth device to adjust its volume. Thus, if you experience this kind of issue, you’ll notice that the volume slider in the taskbar and the device volume control neither have any effect in adjusting the volume. And each time you try to adjust the volume level for one speaker, the volume of another speaker also automatically changes. In such a case, it would be difficult for you to separately change the dual volume control headphones. Worry not for there is an easy registry tweak you can try to make this possible to do. But before you proceed with the instructions provided below, make sure that you create a System Restore first. Once you have that covered, follow the steps below carefully. Step_1: Tap the Win + R keys to open the Run dialog box and type “Regedit” in the field and hit Enter to open the Registry Editor. Step_2: Next, navigate to this registry path: HKEY_LOCAL_MACHINESYSTEMControlSet001ControlBluetoothAudioAVRCPCT Step_3: After that, look for the entry named “DisableAbsoluteVolume” which should be located in the right pane. But if you’re unable to find this entry, you can just create it by right-clicking on the CT key and selecting New > DWORD (32-bit) value, and then assign “DisableAbsoluteVolume” as its name. Step_4: Once done, double click on the “DisableAbsoluteVolume” DWORD and set its value from 0 to 1. Step_5: Now exit the Registry Editor and restart your computer. On the other hand, you can also disable or enable the Absolute Volume feature by executing a command in the Command Prompt.

• If you want to disable the Absolute Volume feature, just execute this command: reg add HKLMSYSTEMControlSet001ControlBluetoothAudioAVRCPCT /v DisableAbsoluteVolume /t REG_DWORD /d 1 /f
• If you want to enable the Absolute Volume feature, just execute this command: reg add HKLMSYSTEMControlSet001ControlBluetoothAudioAVRCPCT /v DisableAbsoluteVolume /t REG_DWORD /d 0 /f

After you execute the command, just restart your computer.

After your computer restarts.

Once you’re done executing the given instructions above, you have to right-click on the speaker icon located in the system tray and select Open Sound Settings and click on Manage device settings – the same controls will be visible to you like earlier. Now when you change the volume level for one speaker, the other speaker should now remain as it is and won’t change alongside the speaker.

BSOD or Blue Screen of Death errors are one of the toughest issues you can encounter in Windows 10 as well as the hardest ones to resolve as they simply shut the system down or restart it abruptly and claims that it isn’t possible to boot Windows again. One of the difficult BSOD errors is the Machine Check Exception BSOD error. The reason why it is hard to fix is that in most cases, it occurs soon after Windows loads which gives users little to no time in resolving it. To make things worse, the system also freezes right before it displays the blue screen error and shuts the system down. Usually, the Machine Check Exception Stop error occurs due to the failure or overstressing of the hardware components. And in the case of almost all Blue Screen of Death errors, the issue usually has something to do with the drivers. So if you frequently see this BSOD error from time to time, now’s the time to act on it by following the solutions given in this post.

Option 1 – Update the Device drivers

• 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. Look for the device driver you and then select either “Update driver” or “Uninstall device”. 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.
• If you have chosen to uninstall the driver, follow the screen options to complete the process and then restart your PC.
• Connect the device and Scan for hardware changes – you can see this option under Device Manager > Action.

Option 2 – Try running the Blue Screen Troubleshooter

The Blue Screen troubleshooter is a built-in tool in Windows 10 that 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.

Option 3 – Try running 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 with good system files that might be causing the Machine Check Exception BSOD error. 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.

Option 4 – Run the Startup Repair

In the Blue Screen where the Machine Check Exception error is displayed, tap the F8 key to go to the Startup Settings where you can find Startup Repair and then run it. Note that this is a must-try option especially if you are unable to start your computer and if you can use your computer for a few moments.

Option 5 – Run the DISM tool

There are cases when the Machine Check Exception error is caused by the Windows System Image so you need to repair it using the DISM or Deployment Imaging and Servicing Management 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 /CheckHealth
• Do not close the window if the process takes a while as it will probably take a few minutes to finish.

Option 6 – Try resetting the BIOS

If you have made some modifications in the BIOS that might have caused this error, you have to revert those changes to resolve the issue. On the other hand, if you have made a couple of changes and you do not remember which is which, you might have to reset the BIOS.

Option 7 – Try resetting Windows 10

To fix this BSOD error, you can try resetting Windows 10. Doing so won’t get rid of any file in your system – instead of erasing all your media files and documents, this reset option resets all the system settings and files.

Researchers have discovered 16 vulnerabilities in Bluetooth connections that could be exploited and make from minor to some serious damage to your device. The flaw can be used on chips manufactured by Intel, Qualcomm, and Texas Instruments while connecting to external devices like speakers, headphones, keyboards, mice, etc.

Who is affected?

Mentioned chips are used by many in a vast range of devices including big players with their products like Microsoft Surface laptops, Dell desktops, Samsung Phones, Google Pixel, and OnePlus handsets. The Bluetooth bug affects a wide range of devices, including smartphones, laptops as well as smart home gadgets. In total, more than one billion devices that rely on Bluetooth are believed to be impacted.

What is the damage?

The amount of damage possible with this flaw depends on the type of device with the chipset. Some devices can only be crashed after a specially crafted packet is sent to the flawed chip. If that's the case with your gadget, it can be easily resolved with a simple restart. With other devices, hackers can take advantage of the Bluetooth Classic flaw to remotely run malicious code. That could allow malware to be installed remotely. Researchers say vendors were informed about these issues months ago before the findings were published. The good news is this should have given plenty of time for the relevant patches to be pushed out that remedy the flaws. However, you'll need to make sure that you're running the latest version of the operating system to be protected by the patch crafted by the manufacturers.

Android Bluetooth threat

The researchers emphasize the lack of basic tests in Bluetooth certification to validate the security of Bluetooth Low Energy (BLE) devices. The BrakTooth family of vulnerabilities revisits and reasserts this issue in the case of the older, but yet heavily used Bluetooth classic (BR/EDR) protocol implementations. We would also advise users to disable Bluetooth on devices that do not need it. This way you can prevent attackers from sending you malformed LMP packets. Since BrakTooth is based on the Bluetooth Classic protocol, an adversary would have to be in the radio range of the target to execute the attacks. So, in a safe environment Bluetooth can be enabled.

Windows updates have become a regular occurrence in our digital lives. They are frequent and have become quite necessary. Most of the time they bring us quality content like fixed security, resolved bugs, and even new features but from time to time update itself can be not downloaded properly or it can have some issues when installing. Windows Update Error 0x800F0825 is one of these update errors that will be reported seemingly after applying the update. Altho annoying error it is nothing system breaking and can be easily resolved. Hello and welcome everyone, today we will provide you with solutions on how to resolve error 0x800F0825 when trying to complete a Windows update.

Run Windows troubleshooter

Built-in Windows troubleshooter can help a lot in resolving these issues and we will try it as a first solution because of its simplicity and ease of use.

• Click on START
• Click on settings
• Navigate to Update & Security > Troubleshoot > Additional Troubleshooter > Windows Update
• Click on Run the troubleshooter
• Follow onscreen instructions and let the troubleshooter try to solve the issue

Clear contents of SoftwareDistribution & Catroot2 folders

Altho SoftwareDistribution and Catroot2 folders are essential for the update process it can happen that badly downloaded updates or similar corruption can be stored there and thus producing this error.

• Open file explorer and locate these two folders, go inside and delete content inside them
• Try updating again to see if corruption inside folders was the issue.

Update manually

If the previous two solutions have not produced a result and the error is still present then go to the official Microsoft Update Catalog and download the update manually The catalog is here. Search for updates from the Windows Update Catalog In the Search box, type your search terms. You can carry out a full-text search, using a keyword, KB article, MSRC bulletin, driver manufacturer, driver model, driver version, product, and a classification. Select the appropriate version of Windows. Search or click on Advanced Search if you want to refine your search. A list will be displayed. Select the updates that you want to download. Click Add for each selection to add it to the download basket.

• Download the updates. You may be asked to install an Active-X download control to be able to download files from this site
• Double-click on the downloaded updates to install them

Administrators can download updates from the Microsoft Download Center or the Windows Update Catalog to deploy to multiple computers If you are running Windows Server Update Services (WSUS) 3.0, System Center Essentials (SCE), or System Center Configuration Manager (SCCM) you can import updates directly into these applications. Security updates, critical updates, service packs, update rollups, definition updates, and critical drivers can be configured to synchronize with your server automatically. You can still import these updates into your application by using Microsoft Update Catalog; however, depending on how you configure WSUS, SCE, and SCCM, you may not need to import the updates.

Disable system protection

In some rare cases, antivirus or firewall could interfere with both downloads and execution of certain files. If each previous solution failed disable temporarily your security software and try executing the update again.