"Windows cannot complete the extraction" means File Explorer started unpacking a ZIP but could not write one or more files to the destination. The full message usually adds "The destination file could not be created" or "The compressed (zipped) folder is invalid". The most common causes are a path that is too long, a file name Windows does not allow, a protected destination folder, an encrypted ZIP, or a damaged archive. The quickest fix for most people is to extract to a short folder you own, such as C:\x, and if that fails, use a full archive program instead of File Explorer.
Work through the fixes below in order. Each one starts with how to tell whether it applies to you.
Read the full error first
The second line of the message points to the cause, so it is worth reading before you start trying fixes:
| Second line of the error | Most likely cause | Go to |
|---|---|---|
| The destination file could not be created | Long path, invalid name or protected folder | Fixes 1 to 3 |
| The compressed (zipped) folder is invalid | Incomplete, damaged or unsupported ZIP | Fix 5 |
| Error 0x80004005 or an unspecified error | Encrypted ZIP | Fix 4 |
| Error 0x80010135: Path too long | Path over 260 characters | Fix 1 |
| There is not enough space | Destination drive is full | Fix 6 |
Fix 1: Shorten the path
Windows traditionally limits a full path, including the drive, every folder name and the file name, to 260 characters. Downloads land in a folder like C:\Users\YourName\Downloads\, Extract All then creates a folder named after the ZIP, and the archive's own nested folders go inside that. A project with deep folders easily goes past the limit.
- Create a short folder at the root of a drive, for example
C:\x. - Move the ZIP into it and rename the ZIP to something short, like
a.zip. - Right-click it, choose Extract All, and extract into
C:\x.
If that works, you can move the extracted folders wherever you like, keeping in mind that moving them back into a deep folder can hit the same limit. Our guide to error 0x80010135 path too long covers the other options, including turning on long path support.
Fix 2: Deal with file names Windows does not allow
ZIPs made on a Mac or Linux machine can contain names that are legal there but not on Windows. Windows does not allow any of these characters in a name: \ / : * ? " < > |. It also rejects names such as CON, PRN, AUX, NUL, COM1 and LPT1, and names that end with a space or a period.
Signs that this is the problem: extraction fails on the same file every time, and the file name in the error looks odd, for example a date with colons such as 12:30 notes.txt.
- Browse the archive and extract everything except the problem files, then ask the sender to rename those and send them again.
- Or open the archive in an archive program, which can often extract around invalid names more gracefully than File Explorer.
Fix 3: Extract to a folder you own
File Explorer cannot create files in protected locations such as C:\Program Files, C:\Windows or the root of the system drive without elevation, and it may fail silently on folders synced by OneDrive or watched by Controlled folder access in Windows Security.
- Extract to a plain folder inside Documents or Desktop, or to a short folder like
C:\x. - If you use Controlled folder access, check Windows Security → Virus & threat protection → Protection history for a blocked entry.
- If the destination is a OneDrive folder, pause syncing or extract elsewhere first and move the files in afterwards.
Running File Explorer as administrator is rarely the answer. Extracting to a folder you already control is simpler and safer.
Fix 4: The ZIP is encrypted
File Explorer can only decrypt ZIPs that use the old ZipCrypto method. Most modern tools encrypt ZIPs with AES, which File Explorer cannot read. You may see the list of files, but extraction fails with error 0x80004005 or a vague message, and no password box appears.
The fix is to open the ZIP with an archive program that supports AES and enter the password there. Universal Zip handles AES-256 ZIP and 7Z archives as well as password-protected RAR files. If the password then appears to be wrong, see zip file password not working.
Fix 5: The archive is incomplete or damaged
An interrupted download, a failing USB stick or a copy that was cut short all produce extraction errors. Check these in order:
- Right-click the ZIP, choose Properties, and compare its size with the size shown on the download page or in the email.
- If it is smaller, delete it and download it again.
- If the size matches, test the archive in an archive program. Universal Zip can run an integrity test and lists any files inside that fail.
- If only some files are damaged, extract the healthy ones and ask for a fresh copy of the rest.
The "compressed (zipped) folder is invalid" variant has its own causes, such as files that are not really ZIPs, and they are covered in compressed zipped folder is invalid.
Fix 6: Free up space on the destination
A ZIP that is 2 GB can easily expand to 6 GB or more, especially if it contains documents or databases. File Explorer does not always warn you before it starts, so the extraction stops part-way.
- Check free space in This PC before extracting large archives.
- Use an archive program to see the total unpacked size of the contents before you extract.
- Extract to a drive with more room, or extract only the folders you need.
Other causes worth ruling out
- A file with the same name is open. If you are re-extracting over an earlier copy and one of those files is open in Word or another program, Windows cannot overwrite it. Close it, or extract to a new folder.
- Antivirus interference. Security software may block a file inside the ZIP it considers suspicious. Check its quarantine or history before deciding whether to trust the file.
- Blocked downloads. This does not usually stop extraction, but it makes extracted files show warnings or open in Protected View. See how to unblock a downloaded ZIP file.
- Very old or unusual ZIP compression. File Explorer only supports the common Deflate methods. ZIPs made with LZMA, BZip2 or other methods need an archive program.
When to stop using File Explorer for extraction
File Explorer is fine for the occasional small ZIP. If you regularly hit these errors, a dedicated archive program saves time: it reports exactly which file failed and why, opens encrypted archives, tests for damage before you extract, and can extract many archives in one pass. With Universal Zip, Extract Here and Extract to folder are on the right-click menu, so the habit barely changes.
Frequently asked questions
What does 'the destination file could not be created' mean?
Windows could not write a file from the ZIP, usually because the path is too long, the name contains invalid characters, or the folder is protected.
Why does extraction fail only on some files?
Those files may have very long paths, names that Windows does not allow, or be damaged inside the archive.
Does running Explorer as administrator help?
Rarely. It is better to extract to a folder you own, such as one in Documents or a short folder like C:\x.
