EFS encrypts individual files using a user’s certificate and private key. BitLocker protects a volume. If files still exist but cannot be decrypted after a reinstall or migration, identify EFS and locate the original authorized key material; copying the files or becoming an administrator does not supply it.
Confirm that the problem is EFS
Inspect a file’s Properties > Advanced for the encryption setting. An advanced read-only check in Command Prompt is:
cipher /c "D:\Archive\report.docx"
Use the actual file path. Microsoft’s cipher reference documents this information display and certificate/key operations. Record the certificate identity locally. Do not include private keys, PFX files or their passwords in support messages. A filename, color, or generic access-denied message alone is not enough to diagnose EFS.
If the whole volume is BitLocker-locked, unlock that layer using its valid credential first. An unlocked volume can still contain EFS files requiring a separate key.
Search your existing credential sources
Check a password-protected PFX/P12 export made by the original user, a secure certificate backup, or the original still-working profile. A .cer file alone normally contains the public certificate, not the private key required for decryption. If an organization configured a recovery agent for those files, contact its administrator; do not assume every installation has one.
If the original account still opens the files, copy needed content through that account to a separate destination protected for its sensitivity, such as encrypted storage with access limited to authorized users. Back up its existing EFS certificate and keys using the supported export process. Creating a new EFS key is not a way to decrypt files encrypted under an old key.
Import only matching material you are authorized to use
For an existing protected PFX that contains the relevant certificate and private key, use Windows’ certificate import workflow for the intended user’s Personal store. Enter its export password locally, retain the protected original, and verify that the imported certificate has an associated private key. Microsoft’s certutil documentation describes PFX import and distinguishes certificate/private-key material.
Test access to a retained file under that user’s account. Open its actual content; a successful certificate import is not by itself a decryption result. Keep encrypted originals and any readable exports securely separated until the result is checked. Do not share PFX files, private keys, or their passwords in support tickets, screenshots or public posts.
If the key cannot be found
Preserve the encrypted files and relevant original profile/backup material. Ask the organization’s certificate administrator about any pre-existing recovery provision. Taking ownership, renaming extensions, recreating the username, or copying ciphertext cannot recreate the lost private key.
To open an EFS-encrypted file, restore the matching certificate and private key to an authorized Windows account, following the credential-recovery routes above. Recovering the encrypted file and restoring the ability to decrypt it are separate tasks. A readable recovered copy still needs the correct key material; a BitLocker recovery key unlocks a different encryption layer.