Windows cannot complete the extractionWindows File Explorer

How to Fix Windows cannot complete the extraction (Windows File Explorer)

Quick Answer

The error 'Windows cannot complete the extraction. The destination path is too long.' occurs when attempting to extract files to a location where the combined path and file name exceed the operating system's character limit. The fastest fix involves extracting the archive to a root directory or a short-named folder to reduce the path length.

What Causes This Error

The full path to the extracted file, including its name, exceeds the 260-character limit imposed by Windows.
Nested folders within the archive create excessively long directory structures upon extraction.
The archive contains files with very long filenames.
Extracting to a deeply nested folder on the system.
Using an older version of Windows or third-party archiving software that does not fully support long paths.

Step-by-Step Fixes

1Extract to a Shorter Path to Fix 'Windows cannot complete the extraction'

Right-click on the compressed (zipped) folder you wish to extract.
Select 'Extract All...' from the context menu.
In the 'Extract Compressed (Zipped) Folders' dialog box, click 'Browse...'.
Navigate to a root directory like 'C:\' or 'D:\', or create a new, short-named folder directly on a drive (e.g., 'C:\TempExtract'). Select this location.
Click 'Extract' to begin the extraction process to the chosen shorter path.

2Rename the Compressed (Zipped) Folder and Parent Folders

Locate the compressed (zipped) folder that is causing the error.
Right-click on the compressed folder and select 'Rename'.
Give the folder a significantly shorter name (e.g., 'Archive.zip' instead of 'My_Project_Files_Version_1_Final_Review_Compressed.zip').
If the compressed folder is located within several nested folders, navigate to those parent folders and rename them to shorter, more concise names.
Attempt to extract the contents of the compressed folder again after renaming.

3Move the Compressed Folder to a Top-Level Directory

Locate the compressed (zipped) folder on your system.
Right-click on the compressed folder and select 'Cut'.
Navigate to a top-level directory on your drive, such as 'C:\' or 'D:\', or directly to your Desktop.
Right-click in the empty space within the chosen top-level directory and select 'Paste'.
Attempt to extract the contents of the compressed folder from its new, shorter path location.

4Use a Third-Party Archiving Tool

Download and install a reputable third-party archiving utility such as 7-Zip or WinRAR. These tools often have better handling of long path names than the built-in Windows extractor.
Locate the compressed (zipped) folder you wish to extract.
Right-click on the compressed folder.
From the context menu, hover over the installed third-party tool's entry (e.g., '7-Zip' or 'WinRAR').
Select an extraction option such as 'Extract files...' or 'Extract Here'. If selecting 'Extract files...', specify a short destination path as described in previous fixes.

Advanced Fixes

Enable Long Path Support in Windows 10/11

Press the 'Windows key + R' to open the Run dialog.
Type 'gpedit.msc' and press Enter to open the Local Group Policy Editor. (Note: This is not available in Windows Home editions).
Navigate to 'Computer Configuration' > 'Administrative Templates' > 'System' > 'Filesystem'.
Double-click on 'Enable Win32 long paths'.
Select 'Enabled', then click 'Apply' and 'OK'.
Alternatively, for Windows Home or users preferring Registry Editor: Press 'Windows key + R', type 'regedit', and press Enter.
Navigate to 'HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\FileSystem'.
Locate the 'LongPathsEnabled' DWORD value. If it does not exist, right-click in the right pane, select 'New' > 'DWORD (32-bit) Value', and name it 'LongPathsEnabled'.
Double-click 'LongPathsEnabled' and set its 'Value data' to '1'. Click 'OK'.
Restart your computer for the changes to take effect. This modification allows applications that declare support for long paths to bypass the 260-character limit.

Frequently Asked Questions

What is the 260-character path limit in Windows?

The 260-character path limit, often referred to as MAX_PATH, is a historical restriction in Windows on the total length of a file path, including the drive letter, colon, backslashes, folder names, filename, and extension. While modern Windows versions (10/11) can support longer paths, many older applications and some core Windows components still adhere to this limit unless explicitly configured otherwise.

Why does this error specifically occur during extraction?

This error frequently occurs during extraction because compressed archives often contain deeply nested folder structures or files with long names. When these are extracted, the combined length of the destination path and the internal path within the archive can easily exceed the 260-character limit, even if the original archive file itself was stored in a short path.

Can I prevent this error from happening in the future?

Yes, to prevent this error, always extract archives to a short, top-level directory (e.g., 'C:\Extract'). When creating archives, consider using shorter folder and file names. Enabling long path support in Windows 10/11 can also mitigate the issue for applications that support it, but it does not guarantee all applications will bypass the limit.

Does this error affect all types of compressed files?

This error primarily affects ZIP files extracted using the built-in Windows File Explorer. While other archive formats like RAR or 7z might also encounter path length issues, third-party tools designed to handle these formats often have more robust path handling capabilities and may be less prone to this specific error.

Is it safe to enable long path support in the Registry or Group Policy?

Enabling long path support is generally safe for Windows 10 and 11 systems. It allows applications that are designed to use long paths to do so. However, some legacy applications or scripts that were not designed with long paths in mind might behave unexpectedly. For most modern usage, it is a recommended setting to improve compatibility with complex file structures.