The string 0X0070057 is ambiguous and does not match Microsoft’s documented HRESULT format. Before changing permissions or system files, copy the complete code from the dialog. It is most likely either 0x80070057, which Microsoft describes as “The parameter is incorrect,” or 0x80070005, an access-denied or insufficient-permissions error. The correct fix depends on the exact code, where it appears, whether the path is local or a network share, and which Windows edition is installed.
Identify the exact error before trying a fix
Write down every character, including all zeros after 0x. The title’s 0X0070057 has the wrong length for either documented code, so treating it as a confirmed error would send you down the wrong troubleshooting path.
As an Amazon Associate I earn from qualifying purchases.
| Code | Microsoft’s meaning | Most useful first question |
|---|---|---|
0x80070057 |
The parameter is incorrect | Does it occur while viewing effective access on a UNC network path, during Windows Update, or in setup? |
0x80070005 |
Access denied or insufficient permissions | Which account, protected folder, share, or security setting is blocking the operation? |
Also record the action that triggered the message. An error in File Explorer’s effective-access dialog on a path such as \server\share is a different problem from the same hexadecimal value appearing during Windows Update. If the dialog shows only “Denied” without the code, obtain the full event from the application or retry the operation until the complete value is displayed.
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 →Choose the troubleshooting path
| What you see | Likely code | Start here |
|---|---|---|
| File Explorer fails while calculating effective access for a file or folder on a non-Microsoft SMB 3.0 server through a UNC path | 0x80070057 |
Map the share to a drive letter and run the effective-access check from that mapped drive. |
| Windows Update reports the error | 0x80070057 |
Restart, run System File Checker, use the Windows Update troubleshooter, and check for an incomplete update state. |
| Opening, copying, installing, or changing a protected file or share is refused | 0x80070005 |
Verify the account and both NTFS and share permissions. |
| A setup program or another application reports the code | Either code is possible | Use the exact code and the application’s operation to select the relevant branch; do not assume the network-share workaround applies. |
Fix 0x80070057 in Windows 8 effective-access checks
Microsoft documents a specific Windows 8 and Windows 8.1 scenario involving Windows Explorer, a non-Microsoft SMB 3.0 file server, and a UNC path such as \server\share. Explorer asks the server for a security descriptor, but the returned descriptor has a null Owner field. Windows authorization processing expects an owner and Explorer reports 0x80070057.
#1 Best Overall
Use the documented workaround: map the share
- Sign in with the account that normally accesses the share. If the server requires different credentials, have them available.
- Open File Explorer and select This PC.
- On the ribbon, open the Computer tab and choose Map network drive.
- Choose an unused drive letter. In Folder, enter the share path, for example
\server\share. Select Reconnect at sign-in only if this computer should reconnect automatically. - If prompted, enter the credentials accepted by the file server. A mapped drive is only useful if the account can actually reach the share.
- Open the new drive letter, browse to the target file or folder, and open its security properties. In the advanced security window, choose View effective access (the label can appear as an effective-access option) and select the account to evaluate.
This changes the path Explorer uses for the check; it does not alter the server’s permissions or repair its security descriptor. If the mapped-drive check succeeds, continue using that path or ask the server administrator to correct the descriptor returned by the SMB service.
Do not install the wrong update
Microsoft lists a fix for Windows 8.1 and Windows Server 2012 R2 for this scenario, but explicitly says that update does not apply to Windows 8. A Windows 8 computer should use the mapped-drive workaround or contact Microsoft Support rather than forcing a package intended for another edition. Confirm the edition in Control Panel > System and Security > System before looking for an update.
Rank #2
- Acid-free adhesive with a neutral pH
- Easy to use formula is fast setting and can be remoistened with water
- Ideal for book binding, book repairs, framing, collage, paper art & crafts
- Adheres to most porous surfaces, dries clear
- AVOID FREEZING & DIRECT SUNLIGHT. Best used in 60-80℉
If mapping the drive does not help
- Confirm that the path is the same share named in the error and not a shortcut to a different server.
- Test ordinary file browsing on the mapped drive. If files cannot be opened there, the problem is connectivity or permissions rather than the effective-access display bug.
- Ask the server administrator whether the server is non-Microsoft SMB 3.0 and whether its security descriptor supplies an owner.
- Check the code again. If the dialog actually contains
0x80070005, follow the permissions procedure below instead.
Fix 0x80070057 reported by Windows Update
Microsoft’s Windows Update guidance associates 0x80070057 with corrupted files or an incorrect system configuration. The following sequence is a general diagnostic procedure. The referenced guidance targets currently supported Windows versions, so Windows 8 may not offer every modern servicing page or troubleshooter entry.
1. Restart and check the update state
Save your work and restart Windows. After signing in, open Windows Update and check whether a restart is pending, an update is waiting for installation, or an earlier update stopped partway through. Complete any clearly offered restart or installation action before starting another update attempt. Avoid repeatedly powering off the computer while the update screen says that changes are being applied.
2. Run System File Checker
- Open the Start screen, type
cmd, right-click Command Prompt, and choose Run as administrator. - At the elevated prompt, run
sfc /scannowand press Enter. - Wait for verification to reach 100 percent. Do not close the window because it appears idle.
- Read the final message. It will indicate whether Windows Resource Protection found and repaired integrity violations, found violations it could not repair, or found none.
- Restart Windows and try Windows Update once more.
SFC checks protected Windows system files; it does not repair a remote file server or grant access to a protected folder. If the code came from the effective-access dialog, return to the network-share procedure instead of repeating SFC.
3. Run the Windows Update troubleshooter
Open Control Panel, choose Troubleshooting, then open the Windows Update troubleshooter under the system and security troubleshooting options. Let it complete its checks and apply only the changes it reports. Restart if requested, then retry the update. On Windows 8, the troubleshooter may be unavailable, retired, or less comprehensive than the version described for supported releases; that limitation does not prove that the installation is damaged.
4. Check configuration and incomplete updates
- Verify that the computer’s date and time are plausible and that Windows Update is pointed at the intended update service.
- Look for an update that is repeatedly pending, failed, or waiting for a restart. Record its name or number before attempting another repair.
- Disconnect unnecessary removable storage and close installers that may be changing system files.
- If SFC reports unrepairable files or the same update continues to fail, preserve the exact code and SFC result when contacting Microsoft Support. Do not delete update folders or registry entries at random; those changes can remove diagnostic evidence and create a second problem.
Fix 0x80070005: access denied
0x80070005 is a separate error from 0x80070057. Microsoft uses it for access denied or insufficient permissions. It means the identity performing the operation lacks a required permission, or a policy is refusing the request.
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 errorsConfirm which account is being used
- Note the Windows account currently signed in. A mapped drive, scheduled task, service, or installer can run under a different identity than the desktop session.
- For a local operation, retry with an account that is authorized to change the target. If the action specifically requires elevation, right-click the program and choose Run as administrator.
- For a network share, verify the credentials accepted by the server. Windows evaluates the server’s share permissions as well as the local account’s permissions.
Check NTFS permissions on a local folder
- Right-click the file or folder, choose Properties, and open the Security tab.
- Select the account or group that should perform the operation and inspect the allowed permissions.
- Open Advanced to review inherited permissions, the object owner, and any explicit deny entry.
- Ask the owner or administrator to grant the minimum required permission. Do not remove inherited entries or take ownership merely to bypass a warning; doing so can break application access and reduce security.
Check permissions on a network share
For a UNC path, two permission layers apply: the share permissions configured on the server and the NTFS permissions on the shared folder. The more restrictive result wins. A user can have Full Control at the share level and still be denied by NTFS, or appear authorized in NTFS while the share itself allows only read access. Have the server administrator review both layers for the exact account and group membership.
Best Value
Protected locations and installers
System folders, another user’s profile, and application installation directories commonly reject standard-user changes. Confirm that the operation is intended, close the application using the file, and use an elevated administrator session only when the software’s instructions require it. If a setup program fails with 0x80070005, check its target directory and the account under which the installer runs; do not apply the mapped-drive workaround unless the complete code and effective-access symptom match the Windows 8 network-share case.
When the error appears in setup or another application
The same hexadecimal value can be returned by many components. Record the application name, the exact button or command that triggers the failure, the target path, and whether the target is local or remote. For 0x80070057, “parameter is incorrect” usually points to an invalid argument, path, or configuration specific to that operation; Microsoft’s network-share case is only one documented example. For 0x80070005, concentrate on identity and permissions. The application’s own log or support documentation may identify the parameter or resource that was rejected.
Common mistakes to avoid
- Do not treat
0X0070057as a verified code; reread the dialog first. - Do not use a Windows 8.1 or Server 2012 R2 hotfix on Windows 8 when Microsoft says it does not apply.
- Do not change ownership, disable security controls, or grant broad permissions before confirming that the error is actually access-related.
- Do not assume that “Denied” means
0x80070005; the complete hexadecimal value controls the diagnosis. - Do not run system-file repairs for a remote-share descriptor problem, and do not map a drive to fix an unrelated Windows Update failure.
What to record if you need support
Keep the complete code, a screenshot or transcription of the message, the Windows edition, the application involved, and the exact path. For a share, include whether the original path was UNC or a mapped drive and which account was used. For Windows Update, record the date of the failed attempt, whether a restart was pending, the SFC final message, and the troubleshooter result. These details let support distinguish a malformed search term, a permissions refusal, a server security descriptor issue, and a local update configuration problem.
Quick Recap
After the manual checks, Outbyte PC Repair is an optional shortcut for Windows 11, 10, 8, or 7: it can address more than 100 common Windows issues where possible, including broken system elements and shared DLL problems, and includes cleanup, settings, vulnerability checks, and crash logging. Its category-based free trial lasts at least two days before a 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.
