Fix 0x80070057 Video Editor Denied Error

This guide fixes the 0x80070057 error that appears when you try to save, export, or open a project in the Windows Video Editor (Clipchamp or the legacy Photos app editor). The error usually means Windows is rejecting a file path or a storage operation because of a corrupted cache, a permissions problem, or a conflict with a temporary file. Below are step-by-step fixes that resolve the issue in most cases, starting with the easiest and safest methods.

What You’ll Need

• Administrator access to your Windows PC (you’ll need it for some steps).
• Your video project files backed up (optional but recommended).
• At least 2 GB of free disk space on the drive where your project is saved.

Step-by-Step

1. Close the Video Editor completely. Save your work if possible, then right-click the app in the taskbar and choose “Close window.â€� If it’s stuck, use Task Manager (Ctrl+Shift+Esc) to end the process.
2. Restart your PC. A simple reboot clears temporary glitches that often cause error 0x80070057. After restarting, open the Video Editor and try the same action again.
3. Run the Windows Store Apps troubleshooter. Go to Settings > System > Troubleshoot > Other troubleshooters. Find “Windows Store Apps� and click “Run.� Follow the prompts. This fixes corrupted app cache or permission issues automatically.
4. Clear the app’s cache. Open Settings > Apps > Installed apps. Find “Video Editorâ€� or “Clipchamp,â€� click the three-dot menu, choose “Advanced options,â€� then click “Reset.â€� This clears the app’s data and cache. Your project files are not deleted, but you’ll need to re-import them.
5. Check your file path length. The error often appears when the project file or media files are in a folder with a very long path (over 260 characters). Move your project and all source videos to a short, simple folder like C:\Videos\ and try again.
6. Run the Video Editor as an administrator. Right-click the app icon and select “Run as administrator.� This gives the app full access to your files and folders, which may resolve permission-related denials.
7. Repair the app. In Settings > Apps > Installed apps, find the Video Editor, click the three-dot menu, and choose “Advanced options.â€� Scroll down and click “Repair.â€� If that doesn’t help, click “Resetâ€� (this is more thorough).
8. Check disk errors. Open Command Prompt as administrator (search “cmd,â€� right-click, “Run as administratorâ€�), type sfc /scannow and press Enter. Wait for it to finish. Then type chkdsk C: /f and restart your PC when prompted. This fixes file system corruption that can cause the error.
9. Reinstall the Video Editor. If nothing else works, uninstall the app from Settings > Apps, then reinstall it from the Microsoft Store. Your projects are stored separately and should remain intact.

Common Mistakes

• Skipping the reset step. Many users try only the troubleshooter and give up. The Reset option is more powerful and often fixes the error.
• Not moving files. If your project is in a deeply nested folder like C:\Users\YourName\Documents\Projects\Video\Final\, the path length can trigger the error. Shorten it.
• Ignoring disk space. The Video Editor needs free space for temporary files. If your drive is full, you’ll get errors. Free up at least 2 GB.
• Using the wrong account. If you’re not logged in as an administrator, some fixes (like running as admin) won’t work. Switch to an admin account.

Tips

• Save your project frequently under a short name like “project1.mp4â€� to avoid path issues.
• Keep your Windows updated to the latest version. Microsoft regularly fixes bugs in the Video Editor.
• Use an external drive if your main drive is low on space. But ensure the drive is formatted as NTFS, not FAT32, to support large files.
• Export to a different format (e.g., MP4 instead of AVI) if the error only appears during export.

Troubleshooting

If the error persists after all steps:

• Try a different video editor. If the error is specific to the Windows Video Editor, use a free alternative like DaVinci Resolve or Shotcut to complete your project. This isn’t ideal but ensures your work isn’t lost.
• Create a new user profile. Sometimes the error is tied to your user account’s permissions. Create a new local administrator account, log in, and try the Video Editor there.
• Check for third-party antivirus interference. Temporarily disable your antivirus (not Windows Defender) and try again. If it works, add the Video Editor to the exclusion list.
• Use the legacy Photos app editor. If you have the older Windows 10 Photos app, it includes a video editor. Try that instead—it may not have the same bug.
• Contact Microsoft Support via the Get Help app if the error is persistent and you have a Microsoft 365 subscription, as they may have a specific fix.

Frequently Asked Questions

Will resetting the app delete my video projects?

No. Resetting clears the app’s cache and settings, but your project files (the .mp4 or .wlmp files) are stored in your user folders and are not touched. You’ll need to re-import them into the app.

Why does error 0x80070057 happen specifically when exporting?

It usually means the app can’t write to the destination folder. This can be due to a long path, insufficient permissions, or a corrupted temporary file. Moving the output folder to a short path and running as admin often solves it.

Can I fix this error without reinstalling the app?

Yes, most users fix it with the reset or repair option, or by moving files to a shorter path. Reinstalling is the last resort, but it’s not always necessary.

Does this error affect Clipchamp as well?

Yes, the error can appear in both the legacy Video Editor and the newer Clipchamp app. The fixes are the same for both, though the menu names may differ slightly.

Is this error a sign of a hardware problem?

No, it’s a software issue. It’s related to file system permissions or app data corruption, not your GPU or hard drive failing.

I get the error when opening a project, not saving. What should I do?

Follow the same steps, especially clearing the cache and moving the project file to a shorter path. Also, check that the project file isn’t read-only (right-click the file, Properties, uncheck “Read-onlyâ€�).

Related

• How to Add QuickBooks Data to Microsoft Word
• PowerShell vs CMD: Key Differences Explained
• Window Managers vs Desktop Environments