The file will not open
This is usually an open-password or file-encryption case. Preserve the original and identify the exact format before choosing a password search.
Open-password path

A password prompt, an edit restriction and a damaged file can look similar from the outside. This compatibility matrix connects each protection profile to the route, limits and evidence you should check first.
If the file will not open, investigate an open password or encryption profile. If it opens but cannot be edited, investigate the restriction or permission. If the application reports corruption, preserve the original and assess repair separately.
First decision
The same word “locked” can describe different technical states. Use the prompt and the file behaviour to avoid sending a corruption case into a password search or treating an edit restriction as encryption.
This is usually an open-password or file-encryption case. Preserve the original and identify the exact format before choosing a password search.
Open-password path
A worksheet, document or presentation editing restriction is different from encryption. Check the owner, permissions and the application’s protection controls first.
Edit-restriction path
Corruption and a forgotten password need different diagnostics. Keep the original, make a working copy and check whether another copy opens before attempting recovery.
Corruption assessment
Format matrix
Start with the prompt you see, then use the file profile and evidence state to choose a route. “Configured” means the path is defined; “locally verified” means the listed fixture passed a local check.
| Family / profile | Protection | Service path | Limits and notes | Evidence | Fixtures / sources |
|---|---|---|---|---|---|
Office Legacy Office RC4/MD5 (DOC/XLS/PPT) | Legacy file-opening encryption | Eligible older files may offer an unlocked copy after source verification. Assessment selects the path. Open matching guide | The original file is required. An unlocked copy and the original typed password are different results. | Configured | No fixture linked |
Office Legacy Office RC4/SHA-1, 40-bit | Legacy file-opening encryption | Submit the original document for assessment and password-search options. Open matching guide | This profile is not an unconditional file-unlock guarantee. | Configured | No fixture linked |
Office Legacy Office RC4/SHA-1, 128-bit | Legacy file-opening encryption | Submit the original document for assessment and password-search options. Open matching guide | Recovery depends on the password and available search. It is outside the 40-bit file-unlock profile. | Configured | No fixture linked |
Office OOXML Office 2007 Standard (DOCX/XLSX/PPTX) | File-opening encryption, AES-128 | Assess the original file; eligible hash-only submissions are password-only. Open matching guide | The three local examples use this encryption profile, not every modern Office variant. Hash-only processing cannot return an unlocked file. | Locally verified | docxxlsxpptx |
Office OOXML Office 2010 encryption (DOCX/XLSX/PPTX) | File-opening encryption | Assess the original file; eligible hash-only submissions are password-only. Open matching guide | A strong password may remain impractical to recover. This exact profile was not part of the controlled fixture set. | Configured | No fixture linked |
Office OOXML Office 2013+ encryption (DOCX/XLSX/PPTX) | File-opening encryption | Assess the original file; eligible hash-only submissions are password-only. Open matching guide | The extension alone does not identify the encryption profile. This exact profile was not part of the controlled fixture set. | Configured | No fixture linked |
Office Legacy Excel XOR protection | Legacy workbook obfuscation | Keep the XLS source for assessment and the applicable legacy recovery path. Open matching guide | This is a different protection scheme from modern workbook encryption. No encrypted XLS example was tested in this study. | Configured | No fixture linked |
Office Legacy Word XOR protection | Legacy document obfuscation | Keep the DOC source for assessment and the applicable legacy recovery path. Open matching guide | This is a different protection scheme from modern DOCX encryption. No encrypted DOC example was tested in this study. | Configured | No fixture linked |
PDF PDF revision 2, RC4-40 | File-opening / standard-security encryption | Eligible older PDFs may offer an unlocked copy after source verification. Open matching guide | An unlocked PDF is not necessarily recovery of the original typed password. Eligibility is determined from the actual file. | Configured | No fixture linked |
PDF PDF revision 3/4, RC4-128 | File-opening / standard-security encryption | Assess the PDF and separate the open password from editing permissions. Open matching guide | Hash-only processing is password-only. The controlled open-password example is revision 3, not every revision-4 combination. | Locally verified | pdf_open |
PDF PDF revision 5, AES-256 | File-opening / standard-security encryption | Assess the PDF; eligible hash-only submissions are password-only. Open matching guide | No revision-5 example was included in the controlled set. Support does not guarantee finding the password. | Configured | No fixture linked |
PDF PDF revision 6, AES-256 | File-opening / standard-security encryption | Assess the PDF; eligible hash-only submissions are password-only. Open matching guide | No revision-6 example was included in the controlled set. Strong passwords can remain impractical to recover. | Configured | No fixture linked |
ZIP ZIP ZipCrypto, stored member | Traditional ZIP file encryption | Submit the original archive for assessment and candidate verification. Open matching guide | The password must open the archive; a matching checksum alone is insufficient. Hash-only intake is not available for this profile. | Locally verified | zipcrypto |
ZIP ZIP ZipCrypto, deflated member | Traditional ZIP file encryption | Submit the original archive for assessment and candidate verification. Open matching guide | The controlled ZIP example is stored, not deflated. Keep the original archive available for final verification. | Configured | No fixture linked |
ZIP ZIP ZipCrypto, compressed multi-file | Traditional ZIP file encryption | Submit the complete original archive for assessment. Open matching guide | Different members can carry different protection. The configured profile was not locally fixture-tested here. | Configured | No fixture linked |
ZIP ZIP ZipCrypto, mixed multi-file | Traditional ZIP file encryption | Submit the complete original archive for assessment. Open matching guide | Member structure and compression matter. The configured profile was not locally fixture-tested here. | Configured | No fixture linked |
ZIP ZIP ZipCrypto, checksum-oriented multi-file | Traditional ZIP file encryption | Submit the original archive so a complete encrypted member can be checked. Open matching guide | A checksum result alone is not proof that the archive opens. No local example of this profile was tested. | Configured | No fixture linked |
ZIP ZIP WinZip AES | AES-encrypted ZIP contents | Submit the original archive for assessment and candidate verification. Open matching guide | The local example uses AES-256. Other strengths and ZIP variants require their own assessment; a recovered password still has to open the archive. | Locally verified | zip_aes256 |
RAR RAR3 with encrypted headers | Archive encryption including file names | Submit the original archive for assessment; eligible hash-only processing is password-only. Open matching guide | No RAR file was created in this study. An accepted hash-only job cannot return an unlocked archive. | Configured | No fixture linked |
RAR RAR3 stored encrypted member | Encrypted archive member with visible headers | Submit the original archive for assessment and source verification. Open matching guide | No RAR fixture was tested. Compression method and source availability determine the appropriate path. | Configured | No fixture linked |
RAR RAR3 compressed encrypted member | Encrypted archive member with visible headers | Submit the original archive for assessment and source verification. Open matching guide | No RAR fixture was tested. Larger member records can require a different processing path. | Configured | No fixture linked |
RAR RAR3 larger or alternate compressed member | Encrypted archive member; conditional compatibility | Submit the original archive for an individual compatibility assessment. Open matching guide | This is a conditional fallback, not blanket support for every RAR3 method. No local fixture was tested. | Configured | No fixture linked |
RAR RAR5 | Modern archive encryption | Submit the original archive for assessment; eligible hash-only processing is password-only. Open matching guide | No RAR5 fixture was tested. A header-only or hash-only submission cannot provide an unlocked archive. | Configured | No fixture linked |
7z 7z AES-256, visible file names | Encrypted archive contents | Submit the original 7z archive for assessment and source verification. Open matching guide | The local example has encrypted file names instead. Not every compression/coder combination is supported. | Configured | No fixture linked |
7z 7z AES-256, encrypted file names | Encrypted contents and archive header | Submit the original 7z archive for assessment and source verification. Open matching guide | Keep the complete original archive. This local example does not establish support for every coder combination or password. | Locally verified | sevenzip_aes |
PDF PDF permissions only, empty open password | Owner/permissions restriction; file already opens | Check authorised editing or export options in the PDF application before choosing a password search. Open matching guide | The controlled example opens with an empty user password. It does not represent a forgotten open password or guarantee a permissions-removal service. | Locally verified | pdf_owner_only |
Last verified: . A compatibility entry describes the available route; it does not promise that a password can be found.
Use the machine-readable exports when you need to compare a format profile with your own notes or reproduce the public research record.
Treat primary source links as format documentation and fixture results as local checks. A matching format guide can explain the protection, but only a check against your own authorised file can establish its actual state.
Next step
Start with an authorised copy and the exact prompt you see. The format profile determines which path is relevant.