Windows Update Error 0x80070057 Fix

Windows Update Error 0x80070057 is a common error for Windows 7/10. Find how to fix Windows Update Error 0x80070057 with the help of our detailed guide!

If you are faced with Windows error 0x80070057, this means that Windows has failed to install some of its updates. That is basically the sole reason behind it. The error usually has a text message that reads something along the lines of “There have been problems with the installation of the updates, but we will try again later.” It is possible that you may also have had error 0x80240437, which is basically the same thing. This is usually caused by corrupted files in your system, though the reason for the error may be different and we’ll cover it in another article. For now, we’ll give you several possible ways to fix Windows Update Error 0x80070057. Read carefully our guide and follow the instructions – we’ve tried to make everything as user-friendly as possible.The possible fixes in this article should work for all versions of window.

Windows Update Error 0x80070057 Fix

Using SFC Scan

This is probably the easiest method to fix the error. Open your start menu and in the search field type cmd. Right-click on the first result and then on Run as Administrator.

When the Command Prompt opens, you must type in the following: sfc /scannow. This will scan your computer for any corrupted files. Note that the process may take a while, so be patient.

After the scan has finished you will see one out of three possible messages. The first one is Windows Resource Protection did not find any integrity violations. If you see that, then the problem is not caused by any corrupted files or the check wasn’t able to recognize them as such. In this case you should try our second fix. The other possible message is Windows Resource Protection found corrupt files and successfully repaired them. If you see this, then your problem has probably been fixed. Go ahead and see if everything’s back to normal.

The third message that you might see is Windows Resource Protection found corrupt files, but could not repair them. If that’s the case, try typing in another command – Dism /Online /Cleanup-Image/ RestoreHealth (you can copy the instructions from here), then hit Enter. This should be able to repair any corrupted files. Just make sure that you have stable internet connection. This command will try to download replacement non-corrupt files from Microsoft, so it is very important that this happens without any incidents.

In case that this does not solve your problem or you find it difficult to follow the steps, you can instead download a program called SFCFix and run it. This tool will do the whole SFC scan and repair for you. This really is the easiest way to fix the problem, but it requires a third party software download and not all people are happy with this fact

• If none of this helped you fix the error and you are using Win 7, you can try to download System Update Readiness Tool (SURT) for Windows 7 from Microsoft’s website. Install it and try running windows update once more. If you still see the error, proceed with the Registry Edit fix.

Registry edit

If all of the quick % easy solutions failed it is time to bring in the heavy guns.

For this fix, you will need to open Notepad. Open your start menu and type Notepad in the search field and then click on the first result.

Now coppy the following text and past it in the text document:

Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\WindowsUpdate\UX]

“IsConvergedUpdateStackEnabled”=dword:00000000

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\WindowsUpdate\UX\Settings]

“UxOption”=dword:00000000

 After copying the text, click on File and then on Save as. Change the file type to All Files and type in the following file name: wufix.reg.

 Then click on Save and open the saved file from your Desktop. You will be asked whether you want the program to make changes to your computer – click on Yes and follow the prompts.

 This should be able to fix the issue. Just make sure that you try out both the Registry Edit method and SFC Scan, because the problem may have different causes. 

Did we help you fix the annoying error? Did we miss anything? If you have any questions or feedback, feel free to share your thoughts in our coment section below this article.