If a Windows 8 or Windows 8.1 update ends with 0x80070057, the usual causes are damaged update files, missing permissions, or an incorrect system configuration. The title of this problem is often typed as “0X800070057 win8 failed,” but Microsoft’s documented code is 0x80070057—there is one fewer zero after 8007. Confirm the code on your own computer before applying a fix.
Work through the steps in order: protect your files, identify the exact failed update, run the built-in troubleshooter and System File Checker, reset the downloaded-update cache, and then inspect logs or the component store if the failure continues. The first remedies are low-risk; commands that stop services or repair system components require an administrator account.
As an Amazon Associate I earn from qualifying purchases.
What 0x80070057 means in Windows 8
Microsoft uses 0x80070057 for a parameter or configuration problem. In Windows Update, Microsoft associates it with corrupted files, permission issues, and incorrect system configuration. A damaged download can make the update engine repeatedly process the same bad package; a permissions problem can prevent the service from writing to its working folders; and a configuration error can make an otherwise valid package fail validation.
The code does not identify one specific update or prove that Windows is infected. It is a failure result, so the exact update name, the point at which installation stops, and the accompanying entries in the logs are important. If Windows Update keeps failing with 0x80070057, record those details before deleting anything.
#1 Best Overall
- NOTE: This USB flash drive does not include a Windows key, you must have a Windows key to activate Windows, but you can still clean install or reinstall Windows 7.
- Latest Version: Deployed with the latest official original version of Windows 7 (SP1), no viruses, no spyware, 100% clean.
- Professional: Using professional Windows 7 production tool to ensure product quality.
- Compatibility: Compatible with all PC brands, laptop or desktop, 64-bit/32-bit, Dell, HP, Sony, Lenovo, Samsung, Acer, Toshiba and more.
- Plug & Play: Includes user guide and online technical support services. Plug it in and you are ready to go.
Protect your files before changing Windows components
Back up documents, photos, browser exports, and any other irreplaceable files before troubleshooting. Microsoft’s Windows Update guidance says: “Before trying any of the solutions below, make sure you back up your personal files.” A USB flash drive or another separate backup destination is suitable for a straightforward copy. Do not rely on a backup stored only on the same drive that Windows is repairing.
- Copy the contents of your Desktop, Documents, Pictures, Videos, and Downloads folders if they contain important files.
- Export any application data that is not automatically synchronized, such as local email archives or saved project files.
- Safely eject the USB drive or verify that the second backup destination contains the copies before proceeding.
The cache reset later in this guide removes downloaded update files, not your personal documents, but a current backup protects you if a separate disk or system problem appears during repair.
Confirm the exact update and code
Do not assume that every failure showing a similar number is the same problem. On Windows 8.1, open PC settings > Update and recovery > View your update history. Find the entry marked failed and write down the update name, date, and complete error code. Windows 8 may expose the same history through Control Panel: open Control Panel > System and Security > Windows Update > View update history.
The Tool Desk
Outbyte PC Repair FREERepair Windows errors before they cause bigger problemsFix Now →Outbyte Driver Updater FREEFix the driver behind crashes, sound loss and screen glitchesFind Drivers →Check the characters carefully. The documented code is 0x80070057. If your screen actually shows another code, use that code when searching Microsoft’s support material or when contacting support; a near match can point to a different repair path. Also note whether the failure occurs while downloading, while installing, or after a restart. That distinction helps determine whether the downloaded cache or the component store deserves attention first.
Choose the least disruptive repair first
| Approach | Primary scope | Personal-data risk | Access needed | Time and complexity | Diagnostic value |
|---|---|---|---|---|---|
| Windows Update troubleshooter | Common update settings and service conditions | Low; it does not target personal files | Usually standard account; elevation may be requested | Short and guided | May identify a service or configuration fault |
sfc /scannow |
Protected Windows system files | Low, but close applications first | Administrator Command Prompt | Often several minutes | Reports whether system files were repaired or could not be repaired |
| SoftwareDistribution download-cache reset | Downloaded update packages and temporary metadata | Low for personal files; pending downloads must be obtained again | Administrator Command Prompt | Moderate; services must be stopped and restarted | Tests whether a damaged download was the cause |
| Component-store and log investigation | Windows servicing store and detailed records | Low when following Microsoft’s procedure, but more technical | Administrator rights | Longest and most complex | Highest; logs can identify a package, permission, or servicing failure |
Start at the top rather than deleting system folders immediately. If a step changes the symptom, keep the result and the exact message; that information is useful for the next branch or for Microsoft Support.
Run the Windows Update troubleshooter
- Open the Start screen, type troubleshooting, and open the matching Control Panel result. Alternatively, open Control Panel > Troubleshooting.
- Select Fix problems with Windows Update under System and Security.
- Choose Advanced if it is available, select Run as administrator, and allow the tool to apply suggested repairs.
- Read the results page. Note whether it reports a stopped service, a registration problem, a damaged database, or no issue found.
- Restart Windows even if the troubleshooter says it made only a minor change, then try Windows Update once.
The troubleshooter can correct common service and configuration conditions, but it cannot repair every corrupted component-store entry. If 0x80070057 returns, continue rather than repeatedly running the same scan.
Repair protected system files with System File Checker
System File Checker (SFC) checks protected Windows files and replaces damaged copies when a valid local copy is available. Use an elevated Command Prompt so the command has the required permissions.
Do these 3 things before closing this tab:
1Clear out junk files and repair common Windows errors2Scan for outdated or missing drivers - takes under a minute3Repair Windows errors before they cause bigger problems- From the Start screen, type Command Prompt.
- Right-click Command Prompt and choose Run as administrator. Approve the User Account Control prompt.
- At the prompt, enter
sfc /scannowand press Enter. - Leave the window open until verification reaches 100 percent. Interrupting it can leave the check incomplete.
- Read the final message, restart the computer, and retry the failed update.
SFC can report that it found no integrity violations, that it found and repaired corrupt files, or that it found files it could not repair. A successful SFC run does not guarantee that Windows Update will succeed; it only tells you about protected system files. Keep the result because it distinguishes a system-file problem from a download-cache problem.
Reset the Windows Update download cache
If the failure occurs during download or repeats for the same package, the contents of the update download cache may be damaged. The reset removes temporary downloaded packages so Windows can obtain clean copies. It does not remove your personal files, but any update that was waiting to install will need to download again.
Stop the two services that hold the cache
- Open Command Prompt as administrator again.
- Run
net stop wuauservand wait for the message that the Windows Update service has stopped. - Run
net stop bitsand wait for the Background Intelligent Transfer Service (BITS) to stop.
If either command says the service is not started, continue. If Windows reports that the service cannot be stopped, close Windows Update, restart the computer, open an elevated Command Prompt immediately after sign-in, and run the commands again.
Delete only the downloaded files
- Open File Explorer and enter
C:WindowsSoftwareDistributionDownloadin the address bar. - Select the contents of the Download folder and delete them. Do not delete your personal folders, and do not alter other Windows directories.
- If a file is in use, confirm that both services are stopped. A stubborn file may require another restart before it can be removed.
Deleting the contents, rather than the entire SoftwareDistribution folder, keeps the operation narrowly focused. Windows recreates or repopulates the needed download data when the service runs again.
Start the services, restart, and retry
- Return to the elevated Command Prompt and run
net start wuauserv. - Run
net start bits. - Restart Windows.
- Open Windows Update and select Check for updates. Allow the replacement package to download completely, then install it.
If the same code appears immediately after the fresh download, the cache was probably not the only cause. Record the time of the attempt and move to log and component-store analysis instead of deleting the cache repeatedly.
Check permissions and configuration symptoms
Because Microsoft associates 0x80070057 with permissions and incorrect configuration as well as corruption, observe what happens when the failure occurs. A message that access is denied, a service that will not start, or a command that works only when elevated indicates that account permissions or service state needs attention.
Rank #2
- [Win OS Install or reinstall] — Boot from the USB to install or reinstall Win 11, 10, or 7 Home & Pro editions. Includes OS installations and reinstallations media plus WinPE Utility Suite.
- [WinPE Repair & Recovery Tools] — Boot into the included WinPE utility suite to backup system and important files, troubleshoot startup problems, repair boot issues, recover data, recover Win User accounts password, and diagnose common PC problems.
- [All-in-One PC Rescue USB] — Combines Win 11, 10, and 7 installation media with PC repair, recovery, and diagnostic tools on one bootable 64GB USB drive, helping you troubleshoot and restore a computer without needing multiple discs or downloads.
- [Support] — Full instructions are included in packaging plus a printable copy of the instructions with troubleshooting information on the device. Also, a video “How to boot from a bootable USB drive.mp4” to help guide you through starting a PC from a USB drive. If you need help using the USB please contact us for assistance, we are here to help.
- [Video] - If you are new to booting from a USB drive or need a refresher see our video "How to boot from USB drive" both in description and on USB device.
- Use an administrator account for SFC, service-control commands, and component-store repair.
- Make sure the Windows Update and BITS services can be started after the cache reset. In the Services console, their status should not remain permanently stopped when Windows Update is operating.
- Do not change registry values or security permissions merely because the code mentions a parameter. An unsupported registry edit can create a second configuration problem and makes later diagnosis harder.
- Keep the computer connected to reliable power and network access while the update downloads and installs. If the connection drops, note whether the resulting code differs from 0x80070057.
These checks do not replace the documented repairs. They help explain why a troubleshooter or cache reset may appear to work but fail again when the service tries to write its files.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Inspect Windows Update and servicing logs
When the built-in repairs do not resolve the error, logs provide the diagnostic detail that the short code lacks. Windows Update activity is recorded in WindowsUpdate.log; servicing and protected-file activity is recorded in CBS.log. Their exact location and readability can vary by Windows 8 edition and servicing state, so use the paths and log-collection instructions Microsoft provides for your installation.
Quick wins for a faster PC:
Clear out junk files and repair common Windows errorsFree Scan →Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →Repair Windows errors before they cause bigger problemsFix Now →- Reproduce the failure once after the cache reset, noting the exact time and the update identifier.
- Open the Windows Update log and search around that time for
0x80070057, “failed,” “error,” or the update’s package identifier. - Review CBS.log for entries at the same time, especially lines naming a component, package, missing file, or access failure.
- Save copies of the relevant log files before making additional changes. Include the timestamp, code, and failed update name in your notes.
A log that identifies one package or a component-store inconsistency is more useful than a generic retry. Do not remove log files to make the error disappear; they are evidence for the next repair decision.
Repair the component store only with the matching Microsoft procedure
The component store is the source Windows uses to service and replace system components. If CBS.log or WindowsUpdate.log points to component-store corruption, follow Microsoft’s Windows 8 or Windows 8.1 component-store repair instructions for the exact edition and build. The available DISM options and whether installation media is required depend on that version.
Open an elevated Command Prompt and first use the health-check operation Microsoft specifies for your release. If Microsoft’s procedure calls for an online repair, use its exact command and source instructions rather than substituting a DVD or ISO from a different edition, language, or service-pack level. A mismatched source can cause another servicing error. Allow the operation to finish, restart Windows, run sfc /scannow again if Microsoft’s procedure requests it, and retry the update.
Component-store repair is the point at which an incorrect command or source can make recovery harder. If you cannot match the procedure to your Windows 8 edition, stop after collecting the logs and escalate with the exact code and files.
When to contact Microsoft Support
Escalate when the troubleshooter, SFC, cache reset, and the applicable component-store procedure have not resolved the failure, or when a service will not start and the logs show a persistent servicing error. Provide a concise record:
- Whether the computer runs Windows 8 or Windows 8.1, including the system edition and architecture.
- The exact code as displayed, confirming whether it is
0x80070057or another value. - The update name or knowledge-base identifier, the date and time of each attempt, and whether the failure happened during download, installation, or restart.
- The final SFC message and the relevant WindowsUpdate.log and CBS.log entries.
- Which services were stopped, whether the Download folder was cleared, and whether the error changed afterward.
This information prevents support from sending you through steps you already completed and lets an analyst distinguish a bad package from a broader servicing problem. Keep the original backup until the update has installed and the computer has restarted normally.
Common failure branches
The troubleshooter finds nothing
That result does not rule out corruption. Run SFC, restart, and retry. If the code returns, perform the service-and-cache reset and preserve the resulting logs.
SFC cannot repair some files
Do not keep running SFC in a loop. Note the final message, inspect CBS.log, and use Microsoft’s component-store repair procedure for your edition before running SFC again.
Crashes, No Sound, or Screen Glitches?
Random freezes, missing sound and display glitches usually trace back to one bad driver. Find and replace yours safely.Free scan · under a minutePC Slower Than It Used to Be?
A free scan shows the junk files, broken settings and background clutter dragging Windows down - then fixes them in one click.Free scan · Windows 10 & 11A service refuses to stop or start
Restart Windows and repeat the elevated commands before deleting cache contents. If the service still fails, capture the exact Service Control Manager message and contact Microsoft Support; forcing deletion while files are locked can leave the cache in an indeterminate state.
The update fails with a different code afterward
Use the new code as the primary diagnosis. A changed code means the latest attempt reached a different stage, so reusing the 0x80070057 procedure without reading the new log can waste time.
The update installs but Windows will not restart normally
Disconnect nonessential USB devices, allow Windows several minutes to complete servicing, and use the recovery options available for your Windows 8 installation. Do not remove the SoftwareDistribution folder or power off repeatedly while Windows is configuring the update. If recovery cannot complete, provide Microsoft Support with the update history and logs collected before the restart.
Quick Recap
Optional shortcut after the manual fixes
Outbyte PC Repair is an optional shortcut for common Windows problems, including broken system elements, invalid redirects and shared DLL issues, while also offering settings adjustments, temporary-file cleanup, privacy tools, vulnerability checks, a real-time boost, file shredding and an app-crash log. It runs on Windows 11, 10, 8 and 7; a free trial is available by category for at least two days before a paid subscription. Results vary, and it does not repair every update failure.
Recommended Free Tools
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
