Windows XP: check EFS files and existing recovery keys before migration

Before replacing XP, encrypted files must match available keys. This review grants no new access and does not replace key backup.

1. Define edition and data

Record XP edition, service pack, user and affected NTFS areas. XP Home does not provide EFS as XP Professional does. Distinguish EFS from ZIP passwords and disk encryption. Green Explorer text is only a clue; inspect properties.

2. Read a specific file’s certificates

Open encrypted file Properties, General, Advanced, Details. Read authorized users, certificate thumbprints and recovery entries. Do not add/remove users or change encryption. Check representative files: one key may not cover everything.

3. Match existing private keys

In the authorized account open certmgr.msc, Personal, Certificates. Compare the EFS certificate thumbprint with the file and verify its private key is available. A certificate alone is insufficient. Record protected PFX backups and mapping without copying keys or passwords into inventory.

4. Do not assume recovery authority

An administrator is not automatically every file’s recovery agent. Check the file’s actual recovery entries and corresponding private keys. A newly created role does not automatically unlock old files. Missing keys block migration; ownership takeover or password reset does not repair them.

5. Prove access on encrypted copies

Preserve originals and profile before migration. Plan a separate recovery test with an authorized test account and a copy verified still EFS-encrypted. Accidentally decrypted copies do not prove key recovery. Record readable and unresolved data separately; retain originals until acceptance.

Sources