Unknown Error; Unspecified Parameters; Service Not Running

The message with Windows Update Error 0x80070057 may vary depending on where the error was found in the update service, but it is usually a variation of “unknown error”, “unspecified parameter found”, or just “the required service is not”. run. “The update service or activity you participated in will then end and get you back on track.

Although this error has not disappeared, you have seen a large number of error reports in the recent Windows 10 Anniversary Update or Windows 10 Build 1607. Due to this error It is usually related to the Windows update process, so many users are dissatisfied because their system either has an incomplete update process, or temporarily “suspends” their system, or is just forced to enter Windows 10 Build 1507 (aka Threshold 1).

The Windows Update Error 0x80070057 usually occurs when:

  • You are trying to back up your file, but it is damaged.
  • You are trying to install the Windows operating system, but the system reserved partition is damaged.
  • A corrupt registry or policy entry is interfering with the Windows update process.
  • There was a problem installing the update. The system will try again later.

All interesting things are annoying, and all interesting things can be solved.

We’ll Try Again Later

After the anniversary update, some Windows 10 users saw the following Windows update error message:

There were some problems installing updates, but we’ll try again later. If you keep seeing this and want to search the web or contact support for information, this may help – (0x80070057).

There are a number of ways we can attempt to alleviate this issue.

Rename the SoftwareDistribution Folder

Press Windows key + R to open the Run dialogue, then type %SystemRoot% and press Enter. Scroll down to find the SoftwareDistribution folder. Rename this SoftwareDistributon.old. Now restart your computer, and attempt the update.

Change the Windows Registry

If this doesn’t work, we can make changes to the Windows Registry. Press Windows key + R to open the Run dialogue, then type regedit and press Enter.

Ensure the following registry entries match your own:


[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\WindowsUpdate\UX] "IsConvergedUpdateStackEnabled"=dword:00000000


[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\WindowsUpdate\UX\Settings] "UxOption"=dword:00000000

Make the changes if necessary, then reboot your system and attempt the upgrade.

The Parameter Is Incorrect

In this instance, the backup process begins, using Windows inbuilt service. The process fails, generating the message:

An internal error has occurred: The parameter is incorrect: (0x80070057)

Press Windows key + R to open the Run dialogue. Type regedit and press Enter. Now, find the following registry key:



Right-click SystemCertificates, and create New > DWORD (32-bit) Value. Enter the name as CopyFileBufferedSynchronousIo, and set the Value to 1. Hit OK, then restart your system. Your backup should now complete!

How to Fix Windows Update Error 0x80070057

Alter Decimal Symbol

Head to Control Panel > Clock, Language, and Region. Under Region, select Change date, time, or number formats. This will open a new panel. Select Additional Settings. Ensure there is a period (full-stop) next to the Decimal symbol option, then press Apply, and OK.

How to Fix Windows Update Error 0x80070057

Group Policy Interference

This hasn’t been the case for everyone, but when Windows 10 was released many users (understandably) took affront to the archaic Windows Update system metered out by Microsoft. Windows 10 Home users were largely bound to this system, but Windows 10 Pro users had the option to alter their Group Policy settings as to render the update system impotent.

However, interfering with this policy may be exactly what is causing the issue to the Windows Update process.

Press Windows key + R to open the Run dialogue. Type gpedit.msc and press Enter. Now follow this path Computer Configuration > Administrative Templates > Windows Components > Windows Update > Configure Automatic Updates > Not Configured.

Restart your system, and hopefully the update will now complete.

Use the System File Checker

Windows has a built-in system file checking tool, we can use it to scan the system for possible damaged files. This tool will detail any accidental damage and possibly repair it, which will restore the system to a good working condition.

Open an elevated command prompt by right-clicking on the start menu and selecting Command Prompt ( Admin). Now run the following command:


sfc /scannow

This command may take some time. Do not close the command prompt window until the verification is 100% complete. Upon completion, you will receive one of the following messages:

  • Windows Resource Protection did not find any integrity violations.Your system did not contain any corrupted files; you need to try another fix for this issue
  • Windows Resource Protection could not perform the requested operation.You need to reboot your system into Safe Mode, then run the command
  • Windows Resource Protection found corrupt files and successfully repaired them. Details are included in the CBS.Log %WinDir%\Logs\CBS\CBS.log.To view the details of what the System File Checker fixed, see the instructions below
  • Windows Resource Protection found corrupt files but was unable to fix some of them. Details are included in the CBS.Log %WinDir%\Logs\CBS\CBS.log.You’ll need to manually repair the corrupted files. Follow the below instructions to find the corrupted file, then manually replace with a known good copy of the file.

Access the Log

If you have received one of the most recent pair of messages, you may want to view the System File Checker log. This is especially important when you receive the last message.

First, you need to open an elevated command prompt by right-clicking on the start menu and selecting Command Prompt (Admin). Now run the following command:


findstr /c:"[SR]" %windir%\Logs\CBS\CBS.log >"%userprofile%\Desktop\sfcdetails.txt"
How to Fix Windows Update Error 0x80070057

This will copy the log details into a simple notepad file, which you can find on your desktop. Since my Windows installation is fairly new, I haven’t encountered any problems. Therefore, my log looks like this:

However, if you damage a file that the SFC process cannot automatically replace, you will find some entries like this (from the Microsoft support document in the System File Checker):


2007-01-12 12:10:42, Info                  CSI    00000008 [SR] Cannot


repair member file [l:34{17}]"Accessibility.dll" of Accessibility, Version =


6.0.6000.16386, pA = PROCESSOR_ARCHITECTURE_MSIL (8), Culture neutral,


VersionScope neutral, PublicKeyToken = {l:8 b:b03f5f7f11d50a3a}, Type


neutral, TypeName neutral, PublicKey neutral in the store, file is missing

Manually Replacing Corrupted Files

We can now replace the damaged file with a known good copy from the command prompt again. First, you need to open an elevated command prompt by right-clicking on the start menu and selecting Command Prompt( Admin). We now need to take management ownership of the damaged file. Note that in each instance listed, you should replace the pathandfilename with the information in the sfcdetails.txt created in the previous section.

Use the following command:

takeown /f pathandfilename

Now use the following command to grant the administrator full access to the damaged file system:


icacls pathandfilename/grant administrators:F

Finally, use the following command to replace the damaged system file with a known good copy:


copy sourcefile destinationfile

For example, if you copied a known good system file from a system running the same operating system & # 40; and the same version, build, etc. on a USB flash drive, the command might look like this:


copy f:\usbstick\jscript.dll c:\windows\system32\jscript.dll

Using DISM

If manual replacement is too difficult or there are too many files to be replaced, we can use the DISM command. DISM stands for Deployment Image and Service Management. Using this command we can try to download and restore the state of system files. At an elevated command prompt, type the following command:


DISM /Online /Cleanup-Image /RestoreHealth

Depending on your system condition and degree of damage, this command may take a while to run. As we all know, this process will get stuck at 20%. If this happens, please wait a while and it should continue on its own. When finished, check if any files have been replaced. If so, you will need to restart your computer and run the sfc/scannow command again. This time it should replace the damaged file.

Reset Windows Update Repository

Sometimes, we can reset the Windows update repository to solve the problem. This is a somewhat lengthy process and I will not go into details in this article.

However, I would recommend the Microsoft support document to you, which details the entire process so that you can try to troubleshoot with their information.

Windows Update Troubleshooter

I’m not sure how well the Windows Update troubleshooter handles this error, because it may be directly affected by Group Policy and other system settings. However, if you still cannot complete the update, it may be worth downloading and trying it out. It will only fail, right? on the right? !

Go to this page and download the Windows update troubleshooter. After downloading, run the troubleshooter. Select Windows Update, then select Advanced, and then select Run as administrator. This will allow the troubleshooter to run as an administrator and be able to find and fix a wider range of problems. Click Next.

The troubleshooter will automatically scan your system for issues related to Windows Update. If problems are found, the troubleshooter will try to fix them automatically, unless you clear the Automatic fix check box.

Any Other Options?

You thought I was done wrong.

The free SetupDiag tool provided by Microsoft can also help you analyze and repair Windows update errors. Some users have reported Yamicsoft Windows 8 Manager to fix Windows update issues. I haven’t tried this fix personally, so I recommend operating it with relative caution in case the tool has unexpected side effects. You have been warned.

I Have Updated Your Information

Your system should now be fine and truly updated. In addition, you now know how to deal with any other Windows update issues that may arise in the future. As long as Microsoft continues this mandatory update system, if ordinary users are negatively affected, the system will be subject to close scrutiny. This is not the only issue discovered since the anniversary update. Other users have reported random system freezes.

Before Microsoft releases its official fix, enterprising users work together to understand what is going on. Before Microsoft responded, they managed to find a solution. However, users reported that the official fix still did not completely solve the problem, leaving many users with persistent system problems.

Microsoft insists on its position, but now is definitely the time to consider setting up a handbrake for the update, especially when the user is deprived of the right to choose.

Finally, I hope after reading this article you will never see this Windows Update Error 0x80070057 again.