Error 0x80070057 is not one single Windows failure. Microsoft describes it as “The parameter is incorrect,” but the operation that triggered it determines the remedy. Windows Update commonly reports it after corrupted update files, a permissions problem, or an incorrect configuration; Microsoft Edge uses it for invalid installation or update parameters; and a documented legacy network-share problem appears while viewing effective access. Work through the branch that matches what you were doing instead of applying a random registry edit or buying hardware.
If the message explicitly says Access denied, check the code carefully. 0x80070005 is Microsoft’s access-denied or insufficient-permissions code. It is different from 0x80070057, although a permissions problem can be one cause of the latter.
| # | Preview | Product | Price | |
|---|---|---|---|---|
| 1 |
|
Microsoft Windows 11 (USB) | $128.99 | Buy on Amazon |
| 2 |
|
Microsoft System Builder | Windоws 11 Home | Intended use for new systems | Install on a new PC |... | Buy on Amazon |
As an Amazon Associate I earn from qualifying purchases.
What 0x80070057 means
The hexadecimal value is a Windows error code returned when a component receives a parameter, setting, or data structure it cannot use. “Parameter” can mean an update package, an installer option, a path, a configuration value, or information returned by a network server. Consequently, the same code can appear in unrelated places.
Quick wins for a faster PC:
Clear out junk files and repair common Windows errorsFree Scan →Scan for outdated or missing drivers - takes under a minuteDriver Scan →Repair Windows errors before they cause bigger problemsFix Now →| Where you see it | What Microsoft’s guidance associates with it | First remedy to try |
|---|---|---|
| Windows Update | Corrupted files, permission issues, or incorrect system configuration | Run the Windows Update troubleshooter, then an elevated System File Checker scan |
| Microsoft Edge setup or update | Invalid parameters during installation or update | Clear temporary files and download Edge again from Microsoft |
| Effective Access for a network share | A legacy SMB response can omit the security descriptor’s Owner field | Map the UNC path to a drive letter, or apply the Microsoft fix for the affected legacy Windows versions |
| Another application, backup, disk, or setup task | An application-specific parameter or configuration failure | Record the exact operation and follow that product’s current documentation |
There is no general hardware replacement or universal one-click command for this code. The correct fix depends on the operation, your Windows edition, and whether the task is local or network-based.
#1 Best Overall
- Less chaos, more calm. The refreshed design of Windows 11 enables you to do what you want effortlessly.
- Biometric logins. Encrypted authentication. And, of course, advanced antivirus defenses. Everything you need, plus more, to protect you against the latest cyberthreats.
- Make the most of your screen space with snap layouts, desktops, and seamless redocking.
- Widgets makes staying up-to-date with the content you love and the news you care about, simple.
- Stay in touch with friends and family with Microsoft Teams, which can be seamlessly integrated into your taskbar. (1)
Identify the failing operation before changing anything
Read the complete message and note the action that was in progress. A code displayed in Settings during an update needs a different path from the same code displayed by an installer or by File Explorer’s Effective Access tab.
- Windows Update: the failure appears under Settings > Windows Update, during “Checking for updates,” downloading, installing, or restarting.
- Edge: a setup program or Edge update reports invalid parameters, often while installing or updating the browser.
- Network share: File Explorer or a security dialog fails when you calculate effective access for a UNC path such as
\servershare. - Other software: a backup, disk, archive, game, or business application displays the code. In that case, the application’s log and documentation are more useful than a generic Windows recipe.
Write down the exact file or path, the account you used, the Windows version (for example, Windows 11 or Windows 10), and whether the item is on the local disk or a server. This record lets you undo a change and gives support staff enough context to select the right procedure.
Safe preparation
Use an administrator account only when required
Some repairs need elevation, but an administrator token does not make an invalid parameter valid. Sign in with an account that can approve elevation, and approve the prompt only for commands you understand. Do not take ownership of system folders or grant “Everyone” full control as a first response; broad permission changes can create new security and servicing problems.
Check basic conditions
- Restart Windows once. A pending restart can leave an update or installer in an incomplete state.
- Keep the computer connected to reliable power, especially during servicing.
- Confirm that the system drive has free space. An update or installer that cannot create its temporary files may fail before it can report a more specific message.
- Temporarily disconnect a VPN while testing Windows Update or an online installer. Reconnect it after the test if your organization requires it.
- If the failure involves a server, verify that the server is reachable and that you can authenticate to the share with the intended account.
Fix 0x80070057 during Windows Update
Microsoft’s Windows Update guidance associates 0x80070057 (and, in the same guidance, 0x80080005) with corrupted files, permission issues, and incorrect system configurations. Follow the steps in order and retry the update after each meaningful change.
1. Run the built-in Windows Update troubleshooter
- Open Settings.
- On Windows 11, choose System > Troubleshoot > Other troubleshooters. On Windows 10, choose Update & Security > Troubleshoot > Additional troubleshooters.
- Select Windows Update, choose Run (or Run the troubleshooter), and allow the checks to complete.
- Apply any change it recommends, restart if requested, and return to Settings > Windows Update to select Check for updates.
The troubleshooter can correct common service and configuration conditions; it cannot repair every damaged package or third-party conflict. If it reports that no problem was found, continue with the file-integrity check.
2. Run System File Checker from an elevated Command Prompt
- Open Start, type
Command Prompt, right-click it, and select Run as administrator. - At the prompt, enter
sfc /scannowand press Enter. - Wait for verification to reach 100 percent. Do not close the window while the scan is running.
- Restart Windows, then try Windows Update again.
System File Checker reports whether it found and repaired protected Windows files. If it says it could not repair some files, save the result and use Microsoft’s current servicing guidance for that message rather than repeatedly running the same scan.
3. Inspect update storage and temporary files
Windows Update needs working space for downloaded packages and temporary extraction. In Settings > System > Storage (Windows 11) or Settings > System > Storage (Windows 10), check the system drive’s available space and remove only files you recognize as disposable. Emptying a cache is not a guarantee of success; the purpose is to remove an incomplete download and make room for a fresh one.
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 →If the error began after an interrupted download, restart first and let the troubleshooter handle the update cache. Avoid deleting folders inside C:Windows by hand. When a manual cache reset is necessary, follow Microsoft’s current Windows Update reset procedure for your exact Windows release, because service names and protected paths can change.
4. Check service state
- Press
Win+R, typeservices.msc, and press Enter. - Find Windows Update. Its status should not be permanently disabled while you are trying to update. Use Start or Restart if it is stopped.
- Check Background Intelligent Transfer Service and Cryptographic Services as well. They must be allowed to run when Windows Update downloads and validates packages.
- Close the Services console and retry the update.
On a managed work computer, an administrator policy may intentionally control these services. Do not override an organizational policy; ask the administrator to confirm the intended state.
5. Review permissions and configuration without weakening security
Microsoft’s explanation includes permission issues and incorrect system configuration. Confirm that the Windows installation has not had security software, cleanup software, or a manual script change ownership or access on system directories and registry areas. Do not grant unrestricted access to system locations. If you know exactly which policy or permission changed, restore the documented default for your Windows edition; otherwise, use Microsoft support or an administrator rather than guessing.
6. Test without a VPN or unusual network filter
A VPN, proxy, or traffic filter can interfere with update endpoints. Disconnect the VPN temporarily, review Settings > Network & internet > Proxy, and retry on a normal connection. Re-enable required corporate settings after the test. If the error occurs only on one network, the network administrator should inspect filtering and authentication rather than having you alter random registry values.
7. Retry and capture the result
After the troubleshooter, SFC scan, storage check, and service review, select Check for updates again. Record the update’s name, the point at which it fails, and any second code. A new code can identify a different problem; do not assume every later failure has the same cause.
Fix 0x80070057 during Microsoft Edge installation or update
Microsoft Edge support labels 0x80070057 as “Invalid parameters during installation or update.” Use this branch when the browser installer or updater, rather than Windows Update itself, displays the code.
1. Remove stale temporary installer data
- Close all Edge windows and any installer window.
- Press
Win+R, enter%temp%, and press Enter. - Delete files and folders that Windows allows you to remove. Skip anything reported as in use; do not force-delete locked files.
- Empty the Recycle Bin if you need the space, then restart Windows.
Temporary-file cleanup removes leftover installer data; it does not alter your bookmarks or browsing profile. If an organization manages Edge, its policy can still block an installation after cleanup.
Rank #2
- STREAMLINED & INTUITIVE UI, DVD FORMAT | Intelligent desktop | Personalize your experience for simpler efficiency | Powerful security built-in and enabled.
- OEM IS TO BE INSTALLED ON A NEW PC with no prior version of Windows installed and cannot be transferred to another machine.
- OEM DOES NOT PROVIDE SUPPORT | To acquire product with Microsoft support, obtain the full packaged “Retail” version.
- PRODUCT SHIPS IN PLAIN ENVELOPE | Activation key is located under scratch-off area on label.
- GENUINE WINDOWS SOFTWARE IS BRANDED BY MIRCOSOFT ONLY.
2. Download the installer again from Microsoft
Use Microsoft’s official Edge download page and select the installer that matches your Windows architecture and language. A partial or altered download can pass the first stage and fail when parameters are validated. Close other installers while the new package runs, and save it locally before launching it.
3. Verify Windows Update services
Edge updates can rely on Windows servicing components. Open services.msc and verify that Windows Update, Background Intelligent Transfer Service, and Cryptographic Services are not disabled. Start or restart a stopped service, restart Windows, and run the Edge installer again. If the computer is managed, have the administrator confirm whether policy intentionally controls these services.
4. Separate an Edge problem from a Windows servicing problem
If Windows Update itself also fails with 0x80070057, complete the Windows Update branch first. If only Edge fails while Windows Update works, keep the investigation focused on the Edge installer, temporary data, architecture, and organizational policy. Do not apply a network-share fix or change system permissions for an Edge-only failure.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Fix the documented network-share effective-access failure
A Microsoft support article describes a specific problem on Windows 8, Windows 8.1, Windows Server 2012, and Windows Server 2012 R2. When Windows Explorer calculates effective access for a share, some non-Microsoft SMB servers return a security descriptor with a NULL Owner field. Microsoft explains that the SECURITY_DESCRIPTOR structure returned by the server contains a NULL Owner field when NetShareGetInfo returns to Windows Explorer. The result can be 0x80070057.
This is a legacy, narrowly defined scenario. Do not present its hotfix as a universal remedy for Windows 10 or Windows 11. First confirm that you are using one of the listed Windows versions and that the failure occurs specifically while viewing effective access on a UNC share.
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 & 11Outdated Drivers Are Slowing You Down
One free scan finds every outdated or missing driver and matches the right update for your exact hardware.Free scan · exact hardware matchMap the UNC path to a drive letter
- Open File Explorer and select This PC.
- Choose See more (the three-dot menu) and select Map network drive. On older Windows versions, the command is on the Computer tab.
- Pick an unused drive letter and enter the share path, such as
\servershare. - Choose Reconnect at sign-in only if the mapping should persist, and select Finish.
- Authenticate with an account that has the intended share and NTFS permissions, then retry the operation through the mapped drive.
Mapping changes how Windows addresses the resource; it does not grant new permissions. You still need both share-level and file-system access.
Apply the Microsoft update only when its applicability matches
Microsoft released a fix for the affected legacy Windows and Windows Server versions. Use Microsoft’s support article to identify the applicable update for your edition and servicing level. Do not install an unrelated package, and do not assume that the legacy article is a current Windows 10/11 solution.
Check the server implementation
If mapping works but Effective Access still fails, ask the server administrator whether the SMB server returns a complete security descriptor, including an Owner field. A non-Microsoft server may need its own firmware or software update. Changing client permissions cannot supply an Owner field that the server did not return.
When another application reports 0x80070057
For a backup program, disk utility, archive tool, setup package, or business application, the code means only that this component rejected a parameter or configuration in that operation. The available Microsoft guidance does not establish one generic command that repairs every such case.
Free tools Windows power users keep installed
One-click scans. No signup required.
Collect useful evidence
- Copy the full error text, including the application name and any file or path.
- Note whether the target is local, removable, or on a network share.
- Record the Windows edition and build shown in Settings > System > About.
- Check the application’s own log, update history, or diagnostic page.
- Reproduce the failure with a simple local test path only when the vendor’s instructions recommend it; never move sensitive data merely for testing.
Then use the application maker’s current documentation or support channel. A product may require a particular path format, a supported file system, a valid date or number format, or a specific account permission. Those details cannot be inferred safely from 0x80070057 alone.
Do not confuse 0x80070057 with 0x80070005
Microsoft identifies 0x80070005 as a general access-denied or insufficient-permissions error. Microsoft Learn also explains that servicing can fail when file-system or registry permissions have changed and the servicing stack no longer has the required access. If your dialog says “Access is denied” and the code is 0x80070005, follow the permissions and servicing guidance for that code. If the code is 0x80070057, start with the operation-specific branches above.
| Code | Typical wording | How to choose the investigation |
|---|---|---|
| 0x80070057 | The parameter is incorrect; invalid parameters during an Edge operation | Identify the operation first: Update, Edge, legacy share effective access, or another application |
| 0x80070005 | Access denied or insufficient permissions | Inspect the account, policy, file-system permissions, and servicing access for the affected resource |
Checks after the repair
Repeat the exact action that originally failed. For Windows Update, install the pending update and verify that Windows reports the device is up to date. For Edge, open Settings and more > Help and feedback > About Microsoft Edge and let it complete its update check. For a share, reopen the mapped location and test only the access that the account is supposed to have.
If the same code returns, stop changing unrelated settings. Capture the new message, the operation, and any additional code. Repeated failures after a clean retry usually mean the remaining issue is specific to the update package, installer, policy, server, or application rather than a missing universal Windows fix.
Recommended Free Tools
Quick Recap
What this error does not justify
- It does not by itself prove that Windows is infected or that hardware has failed.
- It does not justify buying a new drive, memory, or a generic repair kit; the documented remedies are software and configuration steps.
- It does not justify disabling antivirus protection, Windows security controls, or network authentication permanently.
- It does not justify granting full control to every user or deleting protected Windows directories.
- It does not make a legacy Windows 8/Server 2012 network-share update applicable to modern Windows releases.
As an optional shortcut after you have identified the failing operation, Outbyte PC Repair can address more than 100 common Windows issues where possible, including broken system elements, invalid redirects, shared DLL files, settings that increase CPU, RAM or disk load, temporary and cache files, privacy warnings, 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. It complements antivirus software rather than replacing it, results vary, and no tool repairs every crash.
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.

