The Office installation error 0x80070057 does not have one universal cause. It can indicate leftover files from a failed Office attempt, an unsupported Windows and Office combination, network or security software interference, Windows servicing corruption, or—in a managed business deployment—a specific Configuration Manager build problem. Identify where the code appears before choosing a fix.
For a normal Windows installation, restart and retry first. If that fails, remove remnants with Microsoft’s setup or uninstall troubleshooter, repair any existing Office installation, confirm system requirements, and switch to the Microsoft 365 offline installer when the web installer is being blocked. The enterprise procedure is different and is covered separately below.
As an Amazon Associate I earn from qualifying purchases.
What 0x80070057 means during an Office installation
Windows error codes are context-dependent. Microsoft’s documentation uses 0x80070057 in more than one situation: a Microsoft 365 version 1910 deployment failure through System Center Configuration Manager, and Windows servicing failures associated with corrupted files, permissions, or incorrect system configuration. Therefore, seeing the same hexadecimal code does not prove that every affected computer has the same fault.
First note the exact point at which the message appears:
#1 Best Overall
- The Microsoft Office 365 Bible: The Most Updated and Complete Guide to Excel, Word, PowerPoint, Outlook, OneNote, OneDrive, Teams, Access, and Publisher from Beginners to Advanced
- ABIS BOOK
- Consumer or standalone installation: the Microsoft 365 or Office installer stops while downloading, preparing, or configuring the product on an individually managed PC.
- Existing Office repair: an Office application or installation entry is already present, and setup fails while changing or repairing it.
- Windows Update or servicing: the code appears in Windows Update rather than in Office setup.
- Enterprise deployment: Configuration Manager is deploying Microsoft 365 Apps, particularly version 1910, and reports the code during deployment.
The stage, Windows version, Office installation technology, and whether the computer is centrally managed determine which branch below applies.
Before changing anything: record the installation context
Write down the Office product you selected, the Windows edition and version, whether another Office version is listed under installed apps, and whether the computer is controlled by an organization. This prevents a consumer fix from being applied to a Configuration Manager deployment, or a clean-install procedure from being used when a repair would preserve an existing installation.
Also note whether the installer is the normal web setup program or an offline package. A web installer depends on a working download path and can be affected by a proxy, firewall, antivirus product, or unstable internet connection. An offline installer is designed to avoid those download-time dependencies after its installation files have been obtained.
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 minuteFix a normal Office installation in the supported order
Use these steps for a home or individually managed Windows PC. Stop when the installation succeeds; do not remove unrelated Windows components or edit the registry merely because the code contains “57.” Microsoft does not identify a single registry change, disk-space adjustment, or third-party cleaner as a universal fix for this error.
1. Restart Windows and retry
- Save your work and close Office, the installer, and other open programs.
- Choose Start > Power > Restart.
- After Windows has loaded, start the Office installation again using the correct product installer.
A restart clears a pending reboot and releases files or installer services that may still be in use. If the same code returns, continue rather than repeatedly launching setup without removing the failed attempt.
2. Remove remnants of a failed attempt
A partial installation can leave registration data, services, and files that cause the next setup run to fail. Use Microsoft’s Microsoft 365 setup or uninstall troubleshooter, selecting the Office product and removal option that matches the failed installation.
- Open Microsoft’s setup or uninstall troubleshooter.
- Choose the option to remove or clean up Office when prompted.
- Allow the tool to complete; do not interrupt it while it is removing the previous installation.
- Restart Windows when the troubleshooter requests it.
- Run the installer for the exact Office product you intend to keep.
This path is especially important when an earlier attempt stopped partway through, when an old Office entry remains in the installed-apps list, or when setup reports that another installation is already in progress. If the troubleshooter cannot remove the product, record its result and proceed to Microsoft support rather than deleting folders manually.
3. Repair Office when an installation is already present
If Office appears in Windows’ installed-apps list and the problem is an existing installation rather than a completely clean machine, repair it before removing everything. Microsoft provides different repair flows for Click-to-Run and MSI installations.
Click-to-Run: choose Quick Repair or Online Repair
- Open Settings > Apps > Installed apps (or Apps & features on older Windows versions).
- Select the Microsoft 365 or Office entry and choose Modify or Change.
- When the repair choices appear, try Quick Repair first if you want the shorter local repair.
- If Quick Repair does not resolve the installation error, repeat the path and choose Online Repair.
Online Repair is the more complete Click-to-Run option and may require a reliable internet connection. It can reinstall damaged Office components, so allow it to finish before opening an Office application.
MSI-based Office: use Change and Repair
- Open Control Panel > Programs > Programs and Features.
- Select the Office entry, choose Change, and follow the repair wizard.
- Restart Windows if the wizard asks you to, then retry the installation or update.
Do not assume that a Click-to-Run repair menu applies to an MSI installation. The presence of a Change button in Programs and Features is a useful indication that the MSI flow is the relevant one.
4. Confirm that Windows supports the Office version
Check the system requirements for the exact Office edition and release you are installing. Microsoft specifically notes that unsupported systems, including Windows XP and Windows Vista for some Office versions, cannot install those releases. A setup program can fail even when the installer itself downloads correctly if the operating system is outside the product’s supported range.
Recommended Free Tools
- Confirm the Windows edition and architecture shown in Settings > System > About.
- Compare them with the requirements for the Office release and installation technology.
- Install pending supported Windows updates before retrying Office, unless your organization controls update timing.
- If the computer cannot meet the Office requirements, use an Office release that supports that Windows version or upgrade Windows through a supported path.
Do not force an unsupported Office release with compatibility settings. That can leave an incomplete installation and make cleanup harder.
5. Switch from the web installer to the Microsoft 365 offline installer
When setup fails during download or configuration and a proxy, firewall, antivirus product, or unreliable internet connection is plausible, use Microsoft 365’s offline installer. Microsoft says that the offline installer may help bypass potential proxy, firewall, antivirus, or internet-connection issues that can occur during installation.
- Obtain the offline installer from your Microsoft 365 account or organization’s official deployment source.
- Let the installer download its package completely before moving it to the target PC if you are preparing it on another connected computer.
- On the target PC, close Office and other installation programs.
- Run the offline setup and select the same Office product, language, and architecture you intend to use.
- Keep the computer powered on until setup reports completion, then restart Windows and open an Office application.
The offline package changes the delivery path; it does not repair an unsupported Windows version or a damaged existing installation by itself. If offline setup fails with the same code, return to the cleanup and repair steps rather than repeatedly downloading the same package.
When the code appears in Windows Update instead of Office setup
If 0x80070057 is shown by Windows Update, treat it as a Windows servicing problem first. Microsoft associates this code, along with 0x80080005 in its Windows table, with corrupted files, permission issues, or incorrect system configurations. Office setup may continue to fail until the underlying servicing condition is corrected.
- Restart the PC and check Windows Update again.
- Run the Windows Update troubleshooter from Windows Settings.
- Verify that Windows Update services and their configuration have not been disabled or altered.
- Review whether the account has the permissions required to install updates and applications.
- Investigate file corruption or configuration errors indicated by the troubleshooter or Windows Update history.
Once Windows Update completes successfully, restart and retry Office. If Windows Update continues to report 0x80070057, keep the Office installer out of the troubleshooting loop and resolve the servicing failure through Microsoft’s Windows support process.
Configuration Manager deployments: the Microsoft 365 version 1910 case
A business computer receiving Microsoft 365 Apps through System Center Configuration Manager follows a different path. Microsoft documented a specific Office 365 version 1910 Configuration Manager update failure affecting x86 and x64 Monthly Channel and Targeted builds in the 12130.20xxx range. This is not a general explanation for every consumer installation that displays 0x80070057.
Check the deployed build
- In Configuration Manager, identify the Microsoft 365 Apps deployment and the build assigned to the device.
- Confirm whether it is version 1910 and whether the architecture and update channel match the affected x86 or x64 Monthly Channel or Targeted combinations.
- Compare the installed build with Microsoft’s documented corrected baseline.
The affected updates were removed from the Microsoft Update Catalog. Microsoft states that build 12130.20410 or later is available. Devices that have not yet installed an affected build should be assigned 12130.20410 or a later build rather than the removed update.
Devices already on an affected build
Computers that already received an earlier affected build may need Microsoft’s fix tool to enable further updates. Coordinate this change with the administrator who owns the Configuration Manager deployment, because the remediation must be applied through the organization’s approved software-distribution process. Do not substitute the consumer setup troubleshooter for a centrally managed deployment unless the administrator has first removed that device from management.
The Tool Desk
Outbyte PC Repair FREERepair Windows errors before they cause bigger problemsFix Now →Outbyte Driver Updater FREEScan for outdated or missing drivers - takes under a minuteDriver Scan →Choosing the right branch
| Situation | Most relevant first action | Why it differs |
|---|---|---|
| Clean, individually managed PC | Restart, then retry; use the setup or uninstall troubleshooter if it fails again | A failed prior attempt or a pending reboot is more likely than a managed-build issue. |
| Office entry already installed | Repair the existing Click-to-Run or MSI installation | Repair can restore damaged components without treating the PC as a clean installation. |
| Installer blocked during download | Use the Microsoft 365 offline installer | The offline package can bypass proxy, firewall, antivirus, or internet-path problems. |
| Windows Update reports the code | Run the Windows Update troubleshooter and check services, permissions, and corruption | The failure is in Windows servicing, not necessarily in Office setup. |
| Configuration Manager deployment of Office 365 version 1910 | Check the 12130.20xxx build and move to 12130.20410 or later | Microsoft documented a version- and channel-specific enterprise failure. |
Click-to-Run, MSI, online, and offline: what the distinctions change
Click-to-Run versus MSI: Click-to-Run exposes Quick Repair and Online Repair through the Modify flow, with Online Repair as the fuller option. MSI installations use the Change and Repair wizard in Programs and Features. Selecting the wrong procedure can leave you looking for controls that do not exist.
Online versus offline installer: The online installer obtains files as setup runs and can be disrupted by network controls. The offline installer uses a complete package and is useful when that delivery path is unreliable. Neither option removes remnants or corrects an unsupported operating system; cleanup and requirements checks remain necessary.
Consumer versus enterprise: A personally managed computer can usually be cleaned and reinstalled by its owner. A Configuration Manager device may be intentionally restricted, and its 0x80070057 failure could be tied to a particular Office build. In that case, the deployment administrator must control the correction.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.What to do when each supported step fails
The troubleshooter cannot remove Office
Restart if you have not already done so, run the troubleshooter again, and note the exact product entry it detects. If multiple Office products or languages are listed, select the failed product rather than removing unrelated software. Escalate with the troubleshooter’s result instead of deleting Office directories or registry entries manually.
Quick wins for a faster PC:
Repair Windows errors before they cause bigger problemsFix Now →Scan for outdated or missing drivers - takes under a minuteDriver Scan →Clear out junk files and repair common Windows errorsFree Scan →Repair completes but setup still returns 0x80070057
Confirm whether the repair was Quick Repair or Online Repair. For Click-to-Run, use Online Repair if Quick Repair was the only attempt. For MSI, repeat the Change and Repair flow. If the installation is still inconsistent, use the setup or uninstall troubleshooter, restart, and perform a clean reinstall with the correct product installer.
The offline installer also fails
That result makes a simple download interruption less likely. Recheck Windows support, remove remnants, and determine whether Windows Update itself is reporting the code. On a managed device, ask the administrator to verify the deployment build and channel before making local changes.
The code returns after every restart
Do not treat repetition as proof of a single cause. Record the exact screen, product, build, installation technology, and whether the failure occurs before or after files are downloaded. Those details distinguish a leftover installation from Windows servicing or an enterprise deployment issue.
Verify the installation after the error is gone
- Restart Windows once more if setup or repair requested it.
- Open an Office application and confirm that it reaches the sign-in or document screen without another configuration loop.
- Check the installed-apps list to ensure only the intended Office product remains.
- Run the Office account or update check available in the application and allow it to complete.
- If the computer is managed, confirm in Configuration Manager that the device reports the assigned build and a successful deployment state.
Keep the installer result, build number, and any troubleshooter message if you need support. A precise record is more useful than the hexadecimal code alone.
Do these 3 things before closing this tab:
1Repair Windows errors before they cause bigger problems2Fix the driver behind crashes, sound loss and screen glitches3Clear out junk files and repair common Windows errorsOptional shortcut after the manual fixes
Outbyte PC Repair is an optional shortcut for Windows issues beyond a single Office setup screen. It can fix more than 100 common Windows issues where possible, including broken system elements, invalid redirects, and shared DLL files; adjust settings, clean temporary and cache files, provide privacy and vulnerability checks, and include tools such as real-time boost, file shredder, and an app-crash log. It runs on Windows 11, 10, 8, and 7, offers a category-based free trial of at least two days, and then requires a paid subscription. It complements antivirus software rather than replacing it, results vary, and no tool repairs every crash.
Frequently overlooked details
Why a registry “fix” is not the starting point
Microsoft’s cited guidance does not identify one registry edit as a universal solution for 0x80070057. Because the code can represent different failures, an unrelated registry change can conceal the original condition or create a new one. Use the restart, troubleshooter, repair, requirements, offline-installer, Windows-servicing, or Configuration Manager branch that matches the evidence.
Why disk cleanup alone is not a diagnosis
The documented causes include corruption, permissions, incorrect configuration, network interference, remnants, unsupported systems, and a specific enterprise build. Removing temporary files without identifying which of those conditions applies does not establish that the Office error has been fixed.
Why the exact Office product matters
Microsoft 365 Apps, a perpetual Office release, Click-to-Run, and MSI installations do not expose identical setup and repair controls. Select the product and architecture you actually own or that your organization assigned; installing a different package can produce a new failure that looks similar to the original one.
Free tools Windows power users keep installed
One-click scans. No signup required.
The Bottom Line
For most individually managed PCs, the reliable sequence is restart, remove remnants with Microsoft’s troubleshooter, repair the existing installation when present, verify Windows support, and use the offline installer when the network path is the problem. Treat Windows Update and Configuration Manager appearances of 0x80070057 as separate cases, with their own checks and build requirements.
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.
