Archive Corruption vs Encryption
Password prompts and extraction errors overlap with damaged files. Identify the branch first: a recovery search cannot restore missing bytes, and a repair tool cannot reveal a forgotten password.
Clues that point to encryption
A trusted utility recognises the container, shows protected entries or an encrypted header, and consistently rejects candidate passwords at authentication or extraction. That pattern supports a password branch, especially when a known-good copy behaves the same way.
Header visibility is format-specific: ZIP may show filenames while the data stays protected, while 7z or RAR5 may hide the listing entirely.
Clues that point to corruption
Invalid signatures, unexpected end-of-file, missing split parts, inconsistent hashes, and failures that move when you use a different copy all point to transfer or storage damage. A CRC or data error after a correct password can also be localised corruption.
Check the original source, file size, volume count and cryptographic hash before attempting repair. Keep an untouched copy for evidence.
Invalid signature
Container problem
Missing part
Volume problem
Protected listing
Encryption possible
Data error
Password or damage
Use separate work queues
If the container is healthy and protected, build a password candidate plan. If it is damaged, make a forensic copy and investigate repair or a replacement download. Mixing both queues wastes time and can overwrite useful evidence.
A successful password is not a repaired archive
Verify the password and the extracted data independently. A correct password may expose a file that still contains damaged blocks.
Frequently asked questions
Does a password prompt prove encryption?
Can archive repair recover a password?
What should I send a specialist?
Need a second opinion on this file?
Run the free local check first. If the file is healthy and you are authorized to recover it, you can compare the evidence with a specialist's supported workflow.
Related guides
For authorized owner use only. Recovery depends on the exact file and password; no outcome is guaranteed. FilesUnlock is a separate product from the recovery service that processes submissions.