Free tools Windows power users keep installed
One-click scans. No signup required.
The fastest fix is to extract the ZIP into a short folder such as C:Temp. Windows is usually rejecting the complete path it would create—not just the visible file name. That path includes the destination folder, every nested directory stored in the archive, separators, the file name and its extension.
If a short destination does not work, inspect the archive for deeply nested or oversized names, then consider Windows long-path support or an extractor whose documentation explicitly confirms long-path handling. Enabling a Windows setting alone will not make File Explorer or every other application accept long paths.
As an Amazon Associate I earn from qualifying purchases.
What the “file name too long” error actually means
ZIP extraction errors often say “file name too long,” “path too long,” or Error 0x80010135: Path too long. In each case, the blocked item is normally the full output path that would exist after extraction.
For example, a ZIP might contain a perfectly ordinary file named report.docx. If you extract it to C:UsersAlexDownloads2026Client ProjectsNorth RegionPlanningArchive and the archive adds several nested folders, the resulting path can exceed the limit even though no individual name looks extreme.
#1 Best Overall
- [Ultra-Lightweight Ear Buds Designed for Small Ears] Each earbud weighs only 3.7g and features a compact, ergonomic in-ear design made especially for small ears. Secure, low-profile, and comfortable for workouts, all-day wear or overnight sleeping.The ultra-slim profile sits flush in your ear with no hard edges poking or rubbing, so you can even sleep on your side without discomfort.
- [Immersive Stereo Sound with TOZO OrigX Technology] TOZO OrigX tuning delivers clear vocals, balanced mids, and natural stereo sound for music, podcasts, and videos.
- [Long Battery Life for Daily Use] Get up to 7 hours of playtime on a single charge, with up to 32 hours total using the charging case—ideal for workdays, commuting, and extended listening sessions.
- [Bluetooth 5.3 & Stable Connection] Bluetooth 5.3 provides fast pairing, stable wireless performance, and reduced dropouts as you move around home or office.
- [Deep Bass with Clear Vocals] High-performance drivers produce punchy bass while keeping vocals clean and detailed for everyday listening.
The path length includes:
- The drive letter and colon, such as
C:. - Every folder in the destination.
- Every folder stored inside the ZIP.
- Backslash separators.
- The final file or folder name, including its extension.
Microsoft’s path guidance identifies 260 characters as the common legacy Windows MAX_PATH limit. That is a limit for the complete path, not a limit of 260 characters for the final file name. Microsoft separately documents a maximum of 255 characters for an individual file or folder name. A path can therefore fail because of its total length even when every component is under 255 characters.
Think in terms of the resulting path
A useful way to reason about the error is:
destination path + archive folders + final name and extension = resulting path
Count the destination and the longest branch inside the ZIP, including each separator. You do not need to count only the name shown in the error dialog. A short name near the bottom of a deep tree can be the item that crosses the limit. Conversely, shortening a filename by a few characters may not help if the destination itself consumes most of the available length.
The 260-character figure describes the legacy full-path constraint. It does not guarantee that every path of 260 characters will work in every program, nor does it mean that a path under 260 characters is immune from a separate component limit or an application’s own restriction.
Try the low-risk fix first: extract to a short folder
A shorter destination removes characters from every output path without changing the ZIP’s contents or names.
- Open File Explorer and create a folder close to the drive root, for example
C:Temp. You can also open an elevated or ordinary terminal and runmkdir C:Temp. - Copy the ZIP into that folder, or leave the ZIP where it is if you can select a different destination during extraction.
- Right-click the ZIP, choose Extract All…, and set the destination to
C:Tempor another short path. - Start the extraction and check whether the files are created successfully.
Do not assume moving only the ZIP file will solve the problem. The ZIP’s own location matters much less than the destination plus the directory and file names stored inside it. If the archive contains very deep folders, even a root-level destination can still produce an overlong result.
Why this is the best first test
This change is reversible and does not alter archive data. It also tells you something useful: if extraction works in C:Temp but not in the original project folder, the destination path was a significant part of the problem. You can then move the extracted tree to a longer location in stages, or keep the working copy in the short location while you reorganize the destination.
If extraction fails in both locations, the archive’s internal hierarchy, a single component, or the extractor’s path handling is more likely to be responsible. Keep the destination short while testing the other possibilities so that you are changing one variable at a time.
Inspect the paths stored inside the ZIP
If extraction to C:Temp still fails, inspect the archive’s file list before changing Windows settings.
Look for deep nesting
Expand the folders shown by your archive utility and identify the longest branch. A structure such as DepartmentProjectYearRegionContractWorkingExportsFinalApprovedDocuments can consume more characters than the final file name itself.
Rank #2
- 【IP68 Waterproof Multifunctinal Smart Watch】Torjalph fitness activity tracker smart watch is IP68 waterproof technology ,you can wear it when swimming,handwashing,it's rain-proof which means that you perform multiple exercise modes outside without worrying about sweat or rain corroding your fitness smart watch,and this watch equipped with a 230 mAh large capacity battery magnetic charging ,and this sports activity tracker watch can be used 5-7 days If fully charged.
- 【Larger 1.83'' Full Screen Watch & Multi-dial Selection】1.83 inch full HD color touch screen smart watch for men / women provides excellent 240*284 resolution image quality ,This Bluetooth smart watch offers a better touch experience and remarkable immersion and ,more than 200 watch faces for you to choose from App"Da Fit ", you can change the dial style according to your mood to wear keeping the world on your wrist
- 【Accurate Activity Tracker Smart Watch 】sports watch activity tracker uses sweat and dust resistant breathable silicone strap, our Fitness Tracker Smart Watch for Android iOS Phones supports 12 sports modes,walking,running,bicycle,swimming,badminton,basketball,football,rope skipping. This bluetooth calls smart watch for men women is lightweight and stylish, bringing more convenient and relaxing sports experience while also providing more protection.
- 【Your 24 Hour Personal Daily Health Monitor】Fitness watch for women men full touch screen IP67 waterproof bluetooth smartwatch for Android iOS Phones with heart rate blood pressure monitor multifunction Andriod smart watch with steps counter sleep monitor sports fitness watch, monitoring blood oxygen saturation allows you to understand your physical condition in real time to track fitness progress ,to know your health status in time.
- 【More Functions Bluetooth Call Smart Watch】This fitness activity smart watch full screen for iPhone and Android phones includes a bunch of new features including:The bluetooth smart watch can hang up the phone, receive and display WhatsAPP /Text /Facebook /Twitter /Messenger reminder.Support sedentary reminder, alarm clock, stopwatch, timer,weather information,music control, remote camera control compatible with Android 5.0 and above or iOS 9.0 and above smartphones.
Some archives contain repeated project, customer, date and version folders that were useful in the original storage system but are unnecessary at extraction time. Do not remove those levels automatically: they may distinguish files with identical names. Instead, identify the deepest branch and decide whether the hierarchy can be shortened without losing meaning.
The Tool Desk
Outbyte Driver Updater FREEFix the driver behind crashes, sound loss and screen glitchesFind Drivers →Outbyte PC Repair FREEClear out junk files and repair common Windows errorsFree Scan →Look for a single oversized component
Windows can reject one file or folder name that is near or above the documented 255-character component limit, even when the overall path is otherwise short. Count the individual component separately from the complete path.
A component can be long because of a generated description, a list of identifiers, or a full sentence used as a filename. The extension counts as part of the filename. A destination change cannot make a single component comply with its own limit, so that entry must be renamed or handled by a program that documents a different supported behavior.
Rename only when your workflow permits it
If the archive is under your control, shorten a deeply nested folder or file name and create a new archive. Keep the original ZIP as an untouched backup. Renaming entries can break scripts, project files, manifests, shortcuts or documentation that expect the original names, so preserve names when another system depends on them.
Some archive applications let you rename entries in place; others require extracting, renaming and recompressing. The exact menu labels vary, but the principle is the same: reduce the internal path, not merely the ZIP’s storage location.
When names are contractual, checksum-related or referenced by an automated process, do not rename just to make one extraction succeed. Prefer a shorter destination or a documented long-path-capable application, and record which method was used so another person can reproduce it.
Know which Windows limit is involved
| Constraint | What it measures | Practical implication |
|---|---|---|
Legacy MAX_PATH |
The complete path, commonly documented as 260 characters | A deep destination plus nested archive folders can exceed it even with short individual names. |
| Individual component | One file or folder name, commonly documented as up to 255 characters | Shortening the destination cannot fix a single component that is itself too long. |
| Application behavior | The limit enforced by the program performing extraction | Two extractors can behave differently on the same ZIP. Windows settings do not override an application that has its own limit. |
Microsoft says that, beginning with Windows 10 version 1607, many common Win32 file and directory functions no longer have the old MAX_PATH limitation. The important qualification is that an application must opt in to the newer behavior. The operating system setting and the application’s manifest are separate requirements.
What changed in Windows 10 version 1607
The change removed the legacy limitation from many common Win32 functions; it did not rewrite every Windows program. Microsoft’s wording is explicit: the application must opt in to the new behavior. A program built without the appropriate manifest can continue to reject a path even when the system setting is enabled and the operating system is new enough.
This distinction also explains inconsistent results. One utility may extract the same ZIP successfully while Explorer reports a path error. That difference is evidence about application support, not proof that the ZIP is damaged.
Enable Windows long-path support—without expecting a universal fix
Long-path support is worth trying when shortening the destination or archive names is not practical. It is conditional, not a switch that makes every Windows program path-length aware.
Rank #3
- [Low Noise High Fidelity] New bee guitar cord with 22AWG oxygen-free-copper center conductors provides enhanced signal transfer, the PVC insulation material and the high-density stranded copper double shield provide noise rejection for quiet operation
- [Ideal for Choice] New bee 1/4 straight and right angle metal connectors, ensures a secure connection in any instrument, pedal, or amp jack. L shape great fro on stage guitar stands
- [Wide Compatible] Suitable for mixer, power amplifier, microphone, effector, decoder, equalizer, electoronic organ, electric guitar, electric bass and other electronic equipments. Widely used in the installation of smart home, karaoke speaker, professional stage audio, etc
- [Easy Disassemble] Making incidental repairs quick and easy! Very nice, flexible cable
- [Dont Hesite to Order] 24 hours customer services and professional technology team are standing by
Microsoft’s documented requirements for the relevant Win32 behavior are:
- The
LongPathsEnabledregistry value must be set to1. - The application must declare
longPathAwarein its manifest.
Microsoft also notes that File Explorer does not use the long-path Group Policy setting. Therefore, enabling the policy may not change an extraction started through Explorer’s built-in ZIP commands. A third-party extractor must independently support long paths; the Windows setting cannot add that support to an application that has not opted in.
Microsoft’s technical summary states: “Starting in Windows 10, version 1607, MAX_PATH limitations have been removed from many common Win32 file and directory functions.” The immediately important qualification is: “However, your app must opt-in to the new behavior.” Both sentences matter when diagnosing an extraction failure.
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 & 11Crashes, No Sound, or Screen Glitches?
Random freezes, missing sound and display glitches usually trace back to one bad driver. Find and replace yours safely.Free scan · under a minuteMethod 1: Group Policy
Use this route on Windows installations that provide the Local Group Policy Editor.
- Sign in with an account that can change computer-wide policy.
- Press
Win+R, typegpedit.msc, and press Enter. - Open Computer Configuration > Administrative Templates > System > Filesystem.
- Open Enable Win32 long paths.
- Select Enabled, choose Apply, then OK.
- Close the policy editor. Restart the extraction application. If it still behaves as before, restart Windows so all processes reload the setting.
The policy changes the system value, but it does not retrofit the required longPathAware declaration into an extractor.
Method 2: Registry
If the policy editor is unavailable, set the same value directly. Editing the registry requires administrator rights; a mistake in another location can affect Windows, so change only the value shown here.
- Open Windows Terminal (Admin), PowerShell (Admin) or Command Prompt (Admin).
- Run:
reg add "HKLMSYSTEMCurrentControlSetControlFileSystem" /v LongPathsEnabled /t REG_DWORD /d 1 /f - Close and reopen the extractor. Restart Windows if the application still does not recognize the change.
To verify the value, run:
reg query "HKLMSYSTEMCurrentControlSetControlFileSystem" /v LongPathsEnabledA result of 0x1 indicates that the registry value is enabled. It still does not prove that a particular extraction program opts in.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
When not to change the setting
If extracting to C:Temp solves the problem, changing a computer-wide registry value or policy is unnecessary. Likewise, if the archive belongs to an organization with managed settings, check its change-control rules before modifying a system-wide value. A policy change can affect other applications, while a short destination is limited to the current extraction.
Choose the extraction method based on application support
Windows includes built-in ZIP extraction, but Microsoft’s long-path documentation does not establish that Explorer handles every long-path archive. Microsoft also mentions third-party archive tools for cases such as encrypted archives; that mention is not a certification that a particular utility supports long-path extraction.
If you try another extractor, check its current documentation for all of the following:
Rank #4
- Digital Family Calendar: BSIMB digital calendar wall touch screen puts an end to your chaotic life. Designed for busy families, the digital calendar keeps you organised and in step with your family. Assign different colours and tasks to each family member to make family scheduling easier and more intuitive.
- Easy Setup and Auto-Sync: Plug in, connect to WLAN and auto-syn your electric calendar in minutes. Digital wall calendar compatible with Google calendar, iCloud calendar, Outlook calendar, Cozi calendar and Yahoo calendar. Add events directly on the device or through the ecalendar app. Electronic calendar stays current whether you're at work or traveling—no manual updates needed.
- All-In-One Home Assistant: Smart calendar builds habits and encourage independence with personalised chores. Display daily meal plan to reduce the daily ‘What's for dinner?’ stress. To-do lists keep track of everything you want. Turning chores into valuable achievements with stars and rewards, making life easier and more enjoyable.
- Manage Anytime Anywhere: BSIMB electronic calendar for family stay connected with the powerful ecalendar app. Access and manage your digital wall calendar anytime, anywhere with free features like stars & rewards, photo screensaver, chore charts, meals plans, to-do lists etc. Electronic planner paid features like Magic Import tailor advanced tools for users with special needs.
- Stay in Touch with Loved Ones: Share photos or videos from your phone to electronic wall calendar with app, instantly update your life moment, and keep in touch with your family, especially those who are far away; you can also surprise your smart calendar digital wall by sending him a wish card; it's also great for keeping tech-illiterate elders in touch with the youngsters.
- The Windows versions it supports.
- Whether it supports long paths during extraction, not merely browsing or compression.
- Whether support requires a particular release, option or manifest setting.
- How it handles paths containing Unicode characters, spaces or very deep nesting.
Do not treat a program’s ability to open the ZIP as proof that it can write every contained path. Browsing reads archive metadata; extraction must create each directory and file on disk.
Recommended Free Tools
| Approach | Changes the archive? | Depends on application opt-in? | Best use |
|---|---|---|---|
Extract to C:Temp |
No | Uses the extractor’s normal behavior | First test and lowest-risk workaround |
| Shorten internal names | Yes, on a working copy | No special Windows setting, but the tool must still extract the renamed archive | When names are not required by scripts or documentation |
| Enable long paths | No | Yes: Windows setting plus longPathAware |
When preserving the original hierarchy is important |
| Use another extractor | No | Depends on that vendor’s documented implementation | When the current application is the limiting factor |
No option is universally superior. The short destination changes only where the files are written; renaming changes the archive’s internal paths; long-path support depends on both Windows and the application; and a different extractor must be evaluated from its own current documentation.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.A complete troubleshooting sequence
Follow these steps in order so that each change answers a specific question.
- Record the exact error. Note whether Windows reports “file name too long,” “path too long,” or
0x80010135. These messages point toward a path-length problem, but the exact wording can vary. - Measure the destination path. Copy the planned destination into a text editor and count its characters if necessary. Remember that the archive’s internal folders and file name must be added to it.
- Retry in
C:Temp. This is the safest first intervention because it leaves the archive unchanged. - Inspect the archive tree. Identify a deep branch or a component approaching the 255-character individual-name limit.
- Shorten internal names if acceptable. Work on a copy, rename only the necessary folders or files, and preserve the original archive.
- Enable long-path support. Use Group Policy or the registry, then restart the extraction program. Remember that the program must opt in.
- Test a documented long-path-capable extractor. Confirm support in the vendor’s current Windows documentation rather than relying on forum claims or a one-time success.
- Test one problematic entry. If the utility allows selective extraction, extract the deepest folder or longest file first. This helps identify whether the failure is caused by one entry or by the archive as a whole.
Use selective extraction as a diagnostic
If the utility supports selecting individual entries or folders, test the deepest branch first. A successful extraction of shallow folders followed by failure on one deep branch points to a specific path. If every entry fails from the same destination, the destination or application is more likely to be the common factor.
Selective extraction is a diagnostic, not a complete repair. It can leave an incomplete project tree and may omit files that other files reference. Keep a record of what was extracted, then repeat the final extraction after applying the chosen fix.
Quick wins for a faster PC:
Clear out junk files and repair common Windows errorsFree Scan →Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →Repair Windows errors before they cause bigger problemsFix Now →Why common attempted fixes fail
“I moved the ZIP, but the error remains”
Moving the archive changes the path to the ZIP, not necessarily the path of each extracted item. Select a shorter output directory and inspect the archive’s internal hierarchy.
“I enabled long paths, but Explorer still fails”
That result is expected in some cases. Microsoft states that File Explorer does not use the long-path Group Policy setting, and the extracting application must opt in separately. Use a shorter destination or an application whose documentation confirms support.
“The destination is short, so every file should fit”
Not if one internal folder or file name is itself too long. The 255-character component constraint is separate from the complete-path constraint.
“The archive opens, so extraction should work”
Opening or listing entries does not require creating the resulting directories and files. Extraction can encounter a path limit that browsing does not.
Do these 3 things before closing this tab:
1Clear out junk files and repair common Windows errors2Scan for outdated or missing drivers - takes under a minute3Repair Windows errors before they cause bigger problems“A different utility must fix it”
Not automatically. Utilities implement their own path handling. Verify the product’s current documentation for long-path extraction on your Windows version; no general guarantee applies to every third-party program.
“I will just delete a few folders from the ZIP”
Deleting entries may make the archive extract, but it can also remove dependencies or required documentation. First determine whether the long branch is optional. If it is not, preserve the original archive and use a shorter destination, a supported extractor, or carefully documented renaming instead.
How to prevent the error in future archives
- Keep working folders close to the drive root when projects contain many nested directories.
- Use concise, descriptive names for folders and files, especially in automated export jobs.
- Avoid combining a deeply nested destination with an archive that already contains a long hierarchy.
- Before distributing a ZIP, test extraction into a short path such as
C:Temp. - Document any intentional renaming so recipients know that archive paths differ from the source project.
- When deploying software or scripts that create files, verify that the application declares
longPathAwareif it must handle paths beyond the legacy limit. - When an automated job creates the ZIP, review its naming template for repeated date, customer, project and version segments that add unnecessary depth.
- Tell recipients the expected extraction root when distributing an archive with a deep hierarchy; a short root can prevent failures without changing the package.
Testing matters because a ZIP can appear normal in a file list while still failing at the final destination chosen by a recipient. A test in a short folder checks the archive’s internal paths independently of a user’s long Downloads or project path.
Frequently asked questions
Frequently Asked Questions
What is the quickest fix for a ZIP path-too-long error?
Create a short folder such as C:Temp and choose it as the extraction destination. This removes characters from every resulting path without changing the archive.
Recommended Free Tools
Is “file name too long” the same as “path too long”?
They often identify the same underlying problem: the complete path Windows is trying to create is too long. The path includes the destination, internal folders, separators, filename and extension.
Will enabling Win32 long paths make File Explorer extract any ZIP?
No. Microsoft says File Explorer does not use the long-path Group Policy setting. The extracting application must also opt in with a longPathAware manifest, so a short destination or another documented extractor may still be necessary.
What is the difference between 260 and 255 characters?
The commonly documented 260-character figure concerns the complete legacy path. The 255-character figure concerns one file or folder name. A path can exceed either limit, and shortening the destination cannot repair an individual component that is too long.
Should I rename files inside the ZIP?
Only if your workflow allows it. Renaming can break scripts, manifests, shortcuts, project files or documentation. Keep the original archive, work on a copy, and rename only the folders or files needed to reduce the path.
Why can an archive open but fail during extraction?
Listing or browsing reads the archive metadata. Extraction must create every directory and file on disk, where the destination length, component limit and extractor behavior are applied.
How do I know whether another extractor supports long paths?
Check the vendor’s current documentation for your Windows version and for long-path support during extraction specifically. Opening a ZIP or creating an archive does not prove that the utility can write every long path.
Do I need to enable long paths if extracting to C:Temp works?
Usually not for that extraction. The short destination already removes the path-length problem without changing system-wide settings. Enable the setting only when preserving the long hierarchy is necessary and the application supports the opt-in behavior.
The Bottom Line
Start with C:Temp: it is the safest fix because it shortens every resulting path without changing the ZIP. If extraction still fails, inspect the archive’s deepest folders and longest individual names, rename entries only on a working copy when safe, or use an extractor whose documentation confirms long-path extraction. Windows 10 version 1607 and later can support longer paths for many Win32 operations, but the system value and the application’s longPathAware opt-in are both required, and File Explorer is not universally changed by Group Policy.
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 & 11Crashes, No Sound, or Screen Glitches?
Random freezes, missing sound and display glitches usually trace back to one bad driver. Find and replace yours safely.Free scan · under a minuteQuick Recap
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.
