Before buying a ZIP repair utility, work out what “compression is not working” means. A ZIP that will not open, a folder that stays large after zipping, and a missing disk-compression checkbox are three different problems. Treating them as one can turn a small file-transfer issue into an unnecessary system overhaul.
This guide uses Microsoft and 7-Zip documentation to separate those problems and identify the next useful check. The checks below are a proposed troubleshooting sequence, not a Windows experiment we performed.
First, choose the problem you actually have
| What you are trying to do | What to inspect first | What not to assume |
|---|---|---|
| Create a ZIP to send several files | Can you create a small ZIP from a harmless text file in your own local folder? | Failure with one large collection does not establish a broken Windows installation. |
| Extract a downloaded archive | Exact error, archive format, download completeness and destination | A file-list preview does not prove every member can be extracted. |
| Save space without making a ZIP | Drive file system and the folder’s NTFS compression setting | The disk-compression feature is separate from ZIP creation. |
| Make photos much smaller | Whether the original files are already compressed | Little size reduction is not necessarily an error. |
Microsoft’s ZIP instructions describe creating an archive through Send to → Compressed (zipped) folder on Windows 10, and using Extract All to unpack one. JPEGs are already compressed, so a ZIP may barely shrink them. Use ZIP to bundle files when that is the goal; do not pay for a repair tool just because the output is a similar size.
A small test that narrows the problem
Keep the original archive. Create a new folder you can write to under your own user account, with a short name. Try zipping a small text file there. Next, try extracting a small archive from a source you trust into another empty local folder. Record the exact message and which operation fails.
If these checks work, compare the failing case one variable at a time: another destination, a fresh download, or a shorter path. Success after a move suggests something about the original location or path, but it does not prove a permission fault. If even the small local checks fail, that is a stronger reason to investigate Explorer or Windows itself. These are diagnostic inferences, not guaranteed fixes.
When an archive opens but extraction fails
Seeing names inside an archive only confirms that enough metadata was readable to show a list. 7-Zip’s FAQ describes damaged 7z archives that display their contents yet report data or CRC errors during Test or Extract. It also notes that unsupported ZIP methods can cause trouble. A different reader is a useful compatibility check, not proof that damaged contents have been repaired.
For an archive you can obtain again, request a fresh copy or download from the original source before paying for recovery. Keep the failed copy separate. If the sender supplies a checksum, compare against that value; a checksum you calculate without a trusted reference cannot establish that the download matches the original.
Check the actual extension and the sender’s instructions. Microsoft’s broader RAR/7z/TAR support note is specifically for Windows 11 version 24H2; it should not be read as a Windows 10 feature list. Microsoft also documents limitations for encrypted archives. For a password-protected archive, use an appropriate archive application and obtain the password from the sender rather than changing disk-compression settings.
Two storage traps a repair utility will not solve
The destination is not the only drive involved. 7-Zip explains that dragging extracted files into Explorer stages them in its temporary folder before copying them to the destination. Its Extract command avoids that staging step. If the system drive is nearly full while the external drive has space, try Extract with an explicit destination. This is a workflow change to compare before buying more storage; it does not make the extracted files smaller.
Free space and maximum file size are different limits. Microsoft’s file-system comparison lists a roughly 4 GiB per-file ceiling for FAT32. A large ZIP being copied to that drive, or one large member being extracted, can exceed it even when the drive has plenty of room. Splitting an archive for transfer does not solve the problem of extracting a single oversized member onto FAT32. Prefer an existing suitable destination; formatting a drive is not a first troubleshooting step because it erases its contents.
Long paths: shorten first, change policy later
Microsoft documents a traditional MAX_PATH limit of 260 characters, including the terminating null character, for many Windows API paths. Windows 10 version 1607 and later allow many functions to use longer paths, but the application must opt in as well as the system setting. A registry switch alone does not update every application.
As a simple comparison, extract to a short folder you own and can write to, with enough free space. The full destination includes the nested names inside the archive, not just the ZIP filename. If shortening the path changes the result, preserve that observation when asking the sender or application vendor for help. Do not translate “Windows supports long paths” into “path length cannot be the problem.”
If you meant the “compress contents” checkbox
Microsoft’s compact command documentation concerns NTFS file compression, not ZIP archives. A directory’s compression attribute controls the treatment of newly added files; changing it does not necessarily change existing files. That inheritance can explain why new files look compressed again.
For a read-only check, open a normal Command Prompt in the folder concerned and enter compact with no parameters. Microsoft documents this as displaying the compression state of the current directory and its files. Do not copy a recursive drive-wide command merely to inspect one folder. The feature is NTFS-specific; ZIP files can still exist on a drive that does not support NTFS compression. An encryption-policy setting is not a substitute for this compression setting.
When to stop trying bigger fixes
Avoid turning off antivirus, excluding an entire download folder, deleting all temporary files recursively, or changing system policy just to open one archive. If a security product flags the file, investigate the source and warning rather than bypassing it. On a managed work computer, give IT the exact error, source, destination and small-test results.
If Explorer has broader problems with multiple known-good local files, Microsoft’s system-file repair guide gives DISM first and then SFC after DISM succeeds. These tools address Windows components; they do not reconstruct a damaged download. Use that route for a suspected system problem, not as a ritual for every failed ZIP.
7-Zip is free to use, including at work. Paid recovery is a separate decision: it may be worth investigating when the only copy is damaged, but neither a free tool nor a paid one should be treated as guaranteed recovery. The cheapest useful next step is usually the check that distinguishes the cause—not another generic repair subscription.
Scope and update
Reviewed 12 October 2026. We removed unrelated web-server timing checks, unverified firsthand-test claims and blanket system changes from the previous version. This is documentation-based analysis; no Windows PC was tested for this revision. ZIP and file-system behavior are best supported here by the relevant technical documentation, rather than an unrelated research citation.
Windows 10 version 22H2 reached its regular support end on 14 October 2025. Check Microsoft’s lifecycle and extended-security-update options for your edition and enrollment. This article is not a claim that every long-term-servicing edition shares the same lifecycle, or that an archive utility restores operating-system support.
Cover photograph: Arina Krasnikova / Pexels under the Pexels license. Illustrative storage photograph, not a screenshot of a tested Windows error.