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 →If Windows 7 shows 0x80070057 while installing an update, the code usually points to damaged or missing update files, a corrupt Windows Update database, a service problem, or interference from security software. The title’s 0X800070057 contains an extra zero; the documented code is 0x80070057. Start with the reversible repairs below, then progress to system-file repair, component reset, clean boot testing, and manual installation of the affected update.
The same hexadecimal code can also appear during backup, application installation, or another operation. The procedure here is aimed at the Windows Update case. Confirm where the message appears before making broader system changes.
As an Amazon Associate I earn from qualifying purchases.
Confirm the code and the operation
Windows error codes are hexadecimal identifiers, not descriptions of one unique failure. In this case, Microsoft documents 0x80070057 among Windows Update installation failures. If you copied the message from a screen or log, check that it is not 0X800070057; that version has one extra zero and is not the documented Windows Update code.
Free tools Windows power users keep installed
One-click scans. No signup required.
| Where you see the error | What it usually means | Use this guide? |
|---|---|---|
| Windows Update or an update installation | Corrupt or missing download files, a damaged update database, stopped services, damaged system files, or third-party interference | Yes. Follow the sequence below. |
| Backup or restore | A parameter supplied to the backup component is invalid, or the storage or configuration has a separate problem | Only use the identification and low-risk checks first. |
| Program installation or another Windows component | The component rejected a parameter; the cause depends on that program | Do not assume resetting Windows Update will fix it. |
Write down the full message, the update’s KB number if one is shown, whether the failure occurs before or after a restart, and whether other updates install successfully. That information prevents you from applying an update-specific fix to an unrelated 0x80070057 failure.
#1 Best Overall
- Repair, Recover, Restore, and Reinstall any version of Windows. Professional, Home Premium, Ultimate, and Basic
- Disc will work on any type of computer (make or model). Some examples include Dell, HP, Samsung, Acer, Sony, and all others. Creates a new copy of Windows DOES NOT INCLUDE product key
- Windows not starting up? NT Loader missing? Repair Windows Boot Manager (BOOTMGR), NTLDR, and so much more with this DVD
- Step by Step instructions on how to fix Windows 7 issues. Whether it be broken, viruses, running slow, or corrupted our disc will serve you well
- Please remember that this DVD does not come with a KEY CODE. You will need to obtain a Windows Key Code in order to use the reinstall option
Prepare before making changes
- Sign in with an administrator account.
- Save open work and disconnect removable drives that are not needed for the update.
- Create a current backup of personal files. Avoid registry edits, partition repairs, or deletion of system folders as first-line fixes.
- Record your Windows 7 edition and architecture. Open Control Panel > System and Security > System and check whether the installation is 32-bit (x86) or 64-bit (x64).
- If the computer is managed by an employer or school, ask the administrator before stopping services or changing startup software.
1. Restart Windows and run the built-in troubleshooter
A restart clears a pending update transaction and reloads the services that Windows Update depends on. It is the safest first action.
- Close programs and choose Start > Shut down > Restart.
- After Windows loads, open Control Panel.
- Choose System and Security, then Fix problems with Windows Update under Action Center or Troubleshoot common computer problems. The wording can vary slightly by Windows 7 edition.
- Allow the troubleshooter to detect and repair problems. Select Apply this fix when it offers a repair, and keep the report if it identifies a service or database issue.
- Restart once more if the troubleshooter requests it, then select Check for updates.
If the same update fails with 0x80070057, continue rather than repeatedly clicking Retry. Repeated retries do not repair a damaged download cache.
2. Clear the Windows Update download cache
Windows stores downloaded update files and transaction data in C:WindowsSoftwareDistribution. An incomplete or corrupt download can cause 0x80070057. Clear the contents, not the parent folder itself.
- Press Windows key + R, type
services.msc, and press Enter. - In the Services window, locate Windows Update. Right-click it and choose Stop. Wait until the status is no longer Running.
- If Windows refuses to stop the service, also stop Background Intelligent Transfer Service (BITS), then try Windows Update again. BITS transfers update files in the background.
- Open Computer or Windows Explorer and browse to
C:WindowsSoftwareDistribution. - Select the files and folders inside
SoftwareDistributionand delete them. Do not delete or rename theWindowsfolder or theSoftwareDistributionparent folder. - Return to
services.msc. Start Windows Update, and start Background Intelligent Transfer Service if you stopped it. - Restart Windows and check for updates again.
Deleting this cache removes downloaded update packages and history data stored in that location; it does not uninstall Windows or erase personal documents. Windows recreates the required cache folders when the service runs. If deletion reports that a file is in use, verify that Windows Update and BITS are stopped, restart, and repeat the operation instead of forcing removal of protected files.
3. Repair protected Windows system files
A damaged system file or incorrectly registered component can prevent the update engine from validating an update. The System File Checker (SFC) checks protected files and replaces incorrect versions when a usable copy is available.
Run SFC
- Open Start, type
cmd, right-click cmd.exe, and choose Run as administrator. - At the elevated Command Prompt, enter
sfc /scannowand press Enter. - Wait for verification to reach 100 percent. Do not close the window or power off the computer during the scan.
- Restart Windows and try Windows Update again.
SFC can report that it found no integrity violations, repaired files, found corrupt files it could not repair, or could not start the repair service. The last two outcomes require the component-store repair below rather than repeated SFC runs.
Rank #2
- Emergency Boot Disk for Windows 98, 2000, XP, Vista, 7, and 10. It has never ben so easy to repair a hard drive or recover lost files
- Plug and Play type CD/DVD - Just boot up the CD and then follow the onscreen instructions for ease of use
- Boots up any PC or Laptop - Dell, HP, Samsung, Acer, Sony, and all others
- Virus and Malware Removal made easy for you
- This is your one stop shop for PC Repair of any need!
Run DISM when SFC cannot finish the repair
Open an elevated Command Prompt again and run:
DISM.exe /Online /Cleanup-image /RestorehealthOnline DISM normally obtains replacement files through Windows Update. That creates an important dependency: if Windows Update itself cannot provide repair files, DISM may stop with a source or payload error. In that case, an offline repair source matching the Windows 7 edition and architecture is required; do not keep repeating the online command and expect a different result.
When DISM completes, restart the computer and run sfc /scannow a second time. A successful second SFC pass indicates that the protected-file corruption was repaired. If DISM or SFC still reports corruption, record the exact message before moving to component reset or support from an administrator.
4. Reset Windows Update components
Clearing SoftwareDistribution handles the download cache. A full component reset also refreshes the cryptographic catalog cache and stops the services that coordinate transfers, installation, and validation. Use this only after the simpler steps have failed.
Command-line reset
Open Command Prompt as administrator. Enter each line separately and wait for the command to complete:
net stop bits
net stop wuauserv
net stop appidsvc
net stop cryptsvc
ren %systemroot%SoftwareDistribution SoftwareDistribution.old
ren %systemroot%System32catroot2 catroot2.old
net start cryptsvc
net start appidsvc
net start wuauserv
net start bitsIf a service is already stopped, Windows may say it is not running; that is not by itself a failure. The two ren commands preserve the old folders under new names so Windows can create clean replacements. If a rename reports that files are in use, stop the listed services again, restart Windows, and retry. Do not rename unrelated system folders.
PC 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 & 11Crashes, 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 minuteAfter the final net start command, restart Windows and run Windows Update. The first scan can take longer because the update database and catalog data are being rebuilt.
Rank #3
- Perfect for installs that are corrupted or full of viruses. Works on any make or model computer.Repair boot manager is missing, NTLDR is missing, Blue Screens of Death (BSOD) and more. This item does not include a key code or a license. You must have your own key code to use the install option otherwise you will get a non-genuine message.
What this reset does not prove
A successful reset does not establish that the original cause was malware, a failing disk, or a particular antivirus product. Microsoft guidance associates 0x80070057 with several possible causes, including damaged files, BITS problems, security software scanning the update directory, and incorrectly registered system files. Treat the reset as a controlled repair, not a diagnosis of one specific fault.
5. Test for third-party software interference with a clean boot
Security scanners and other startup programs can lock files in SoftwareDistribution or inspect a package while Windows Update is writing it. A clean boot starts Windows with Microsoft services and a minimal startup set so you can test whether another program is involved.
- Press Windows key + R, type
msconfig, and press Enter. - On the Services tab, select Hide all Microsoft services. Then choose Disable all.
- Open the Startup tab and disable nonessential startup entries. On some systems this opens Task Manager; disable the listed entries there.
- Choose Apply, then OK, and restart.
- Run Windows Update and test the same KB package.
- If the update succeeds, return to
msconfigand restore Normal startup. Re-enable services and startup entries in small groups, restarting between groups, until the conflicting program is identified.
Do not leave security protection disabled after the test. If you temporarily pause an antivirus or security product under its own controls, disconnect from untrusted networks, perform only the controlled update test, and turn protection back on immediately. A clean-boot result means that software or a service is interfering; it does not identify which item until you re-enable entries methodically.
Do these 3 things before closing this tab:
1Clear out junk files and repair common Windows errors2Fix the driver behind crashes, sound loss and screen glitches3Repair Windows errors before they cause bigger problems6. Install the affected update manually
When Windows Update repeatedly fails but the individual package is available, a manual installation can bypass a damaged download transaction.
- Open Control Panel > System and Security > Windows Update > View update history. Note the failed update’s KB number. The error details may also show it.
- Use Microsoft’s Windows Update or Download Center pages to locate that exact KB package. Search by the complete KB number, not only 0x80070057.
- Choose the package whose architecture matches the computer: x86 for 32-bit Windows 7 or x64 for 64-bit Windows 7. Match the listed language and edition requirements as well.
- Download the standalone installer, close other programs, and run it as an administrator if Windows requests elevation.
- Restart when prompted, then open Windows Update and check whether the package is recorded as installed.
A package can report that it is not applicable when it is already installed, the architecture or language is wrong, a prerequisite is missing, or the package targets a different Windows 7 servicing state. Do not force an unrelated KB file. Windows 7 is no longer in ordinary mainstream support, so the availability and eligibility of a particular package can vary; use the exact package information shown for your computer.
Choose the next repair by risk and scope
| Remedy | Scope | Reversibility | Important dependency or risk |
|---|---|---|---|
| Restart and troubleshooter | Pending transactions and common configuration faults | Highest | May identify a problem without repairing deeper corruption. |
Clear SoftwareDistribution |
Windows Update download cache | High | Windows Update and usually BITS must be stopped first. |
| SFC | Protected Windows system files | High | Requires an elevated Command Prompt; unresolved corruption may need DISM. |
| Online DISM | Windows component store | Moderate | Normally needs Windows Update as a repair-file source. |
| Full component reset | Update services, catalogs, and caches | Moderate | Service names and folder paths must be entered exactly. |
| Clean boot | Third-party service and startup conflicts | High | Restore normal startup and security protection after testing. |
| Manual KB installation | One identified update | Moderate | Architecture, language, edition, and prerequisites must match. |
Common failure messages and what to do next
“Access is denied” while stopping a service or deleting files
Confirm that Command Prompt or Services is running with administrator rights. Check that both Windows Update and BITS are stopped. If a security product still holds a file, use the clean-boot test rather than deleting the file by force.
Rank #4
![Microsoft Windows 7 Home Premium Upgrade [Old Version]](https://m.media-amazon.com/images/I/41QblAjhBaL._SL160_.jpg)
- Share all of your favorite photos, videos, and music--you can even watch, pause, rewind, and record TV
- Start programs faster and more easily, and quickly find the documents you use most often
- Make your web experience faster, easier and safer than ever with Internet Explorer 8
- Easily create a home network and connect your PCs to a printer with HomeGroup
- Make the things you do every day easier with improved desktop navigation
SFC says it cannot repair some files
Run the DISM command, restart, and run SFC again. Save the exact result. If online DISM cannot find source files, obtain an appropriate offline repair source or seek Windows 7 servicing support; changing registry values is not a safe substitute.
DISM fails because Windows Update is unavailable
This is a dependency issue: the online form normally gets repair files from Windows Update. Finish the update-service and cache repairs first, or use a matching offline source. Re-running the same command without a source will not supply the missing files.
The update installs manually but Windows Update still shows an error
Restart, check update history, and run a new detection cycle. If the KB is listed as installed, Windows Update may be retrying a stale transaction; clearing the cache and resetting components addresses that state. Do not install the same package repeatedly when the history already confirms success.
The manual installer says the update is not applicable
Recheck x86 versus x64, language, edition, and the exact KB number. The package may already be present or may require a prerequisite. A package for another Windows release cannot repair this error.
The error returns only when a security product is active
Use the clean-boot procedure to confirm the relationship, then restore protection and consult that product’s documented Windows 7 compatibility settings. Do not permanently disable security software to keep updates working.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
When the code appears outside Windows Update
If 0x80070057 appears during backup, restore, an application installer, or another task, first reproduce the failure and note the exact operation. Check the application’s own logs and Windows Event Viewer for the component name. The Windows Update cache reset may have no relevance in those cases.
Back up important data before changing registry values, repartitioning a disk, replacing system files, or using recovery media. Community advice sometimes recommends registry or partition changes for this code, but those actions carry more risk and depend on the exact failing component. They should not be used as generic fixes for a message that merely contains the same hexadecimal value.
Optional shortcut after the manual fixes
If you want an optional shortcut after trying the manual steps, Outbyte PC Repair can address more than 100 common Windows issues where possible, including broken system elements and shared DLL problems, while also offering settings tweaks, temporary-file cleanup, privacy tools, vulnerability checks, a real-time boost, file shredder, and crash logging. It runs on Windows 11, 10, 8, and 7; its free trial is offered by category for at least two days and then requires a subscription. It complements antivirus software rather than replacing it, results vary, and no tool repairs every crash.
Verify the repair
- Restart Windows normally, not in a clean-boot configuration.
- Confirm that Windows Update and BITS show a Running status in
services.mscunless Windows starts them on demand. - Run Check for updates and install one small, appropriate update first if several are pending.
- Open View update history and confirm the affected KB’s final status.
- If the code returns, record the exact step that failed, the KB number, SFC or DISM output, and whether clean boot changed the result. That record is more useful than repeating every repair from the beginning.
For the Windows Update case, the dependable path is to confirm the correctly written code, restart, run the troubleshooter, clear the update cache, repair system files, reset components, test for third-party interference, and only then install the exact KB manually. Escalate beyond that sequence only when the operation, component, and backup plan are known.
Quick Recap
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.
